You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Nicolas Vazquez <Ni...@shapeblue.com> on 2018/03/05 11:16:44 UTC
Re: Refusing to design this network, the physical isolation
type is not BCF_SEGMENT
Solved, thanks for testing and raising the issue! This will be included on 4.11.1
________________________________
From: Nux! <nu...@li.nux.ro>
Sent: Thursday, February 8, 2018 1:03:29 PM
To: dev
Subject: Re: Refusing to design this network, the physical isolation type is not BCF_SEGMENT
Tested, now I can add L2 network on the back of vxlan phsyical network, but I have found a problem.
It doesn't seem to like VNI ids higher than those for VLANs which is 4096, however VXLAN's max id is about 16 millions, so this is a problem that needs a fix.
Here are some logs:
2018-02-08 15:50:00,738 WARN [resource.wrapper.LibvirtStartCommandWrapper] (agentRequest-Handler-4:null) (logid:bd9fbea5) InternalErrorException
com.cloud.exception.InternalErrorException: Failed to create vnet 33333: RTNETLINK answers: Numerical result out of rangeCannot find device "bond0.33333"Failed to create vlan 33333 on pif: bond0.
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Nicolas.Vazquez@shapeblue.com
www.shapeblue.com
,
@shapeblue
----- Original Message -----
> From: "Nux!" <nu...@li.nux.ro>
> To: "dev" <de...@cloudstack.apache.org>
> Sent: Thursday, 8 February, 2018 14:29:36
> Subject: Re: Refusing to design this network, the physical isolation type is not BCF_SEGMENT
> Thanks! Any idea where blueorangutan keeps the rpms?
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
> ----- Original Message -----
>> From: "Nicolas Vazquez" <Ni...@shapeblue.com>
>> To: "dev" <de...@cloudstack.apache.org>
>> Sent: Wednesday, 7 February, 2018 12:12:00
>> Subject: Re: Refusing to design this network, the physical isolation type is not
>> BCF_SEGMENT
>
>> I have pushed a fix for this on PR 2448. Can you please test it?
>>
>> ________________________________
>> From: Nux! <nu...@li.nux.ro>
>> Sent: Tuesday, February 6, 2018 10:25:07 AM
>> To: dev
>> Subject: Re: Refusing to design this network, the physical isolation type is not
>> BCF_SEGMENT
>>
>> Thanks Nicolas, much appreciated.
>> Once you have a patch, feel free to ping me so I can test.
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>>
>> Nicolas.Vazquez@shapeblue.com
>> www.shapeblue.com<http://www.shapeblue.com>
>> ,
>> @shapeblue
>>
>>
>>
>> ----- Original Message -----
>>> From: "Nicolas Vazquez" <Ni...@shapeblue.com>
>>> To: "dev" <de...@cloudstack.apache.org>
>>> Sent: Tuesday, 6 February, 2018 13:23:54
>>> Subject: Re: Refusing to design this network, the physical isolation type is not
>>> BCF_SEGMENT
>>
>>> Hi Lucian,
>>>
>>>
>>> Thanks for posting this issue. I have checked the canHandle() method on
>>> VxlanGuestNetworkGuru and it is not considering L2 network offerings, only
>>> Isolated, so it refuses to design the network. I'll make sure to include a fix
>>> for it on 4.11.1.
>>>
>>>
>>> Thanks,
>>>
>>> Nicolas
>>>
>>> ________________________________
>>> From: Nux! <nu...@li.nux.ro>
>>> Sent: Tuesday, February 6, 2018 8:30:03 AM
>>> To: dev
>>> Subject: [L2 network] [VXLAN] Refusing to design this network, the physical
>>> isolation type is not BCF_SEGMENT
>>>
>>> Hi,
>>>
>>> I'm trying to add an L2 network based on a VXLAN physical network and I am
>>> getting the error in the subject.
>>>
>>> If I use a VLAN based physical network all completes successfully and I end up
>>> with an L2 network in green "Setup" state.
>>>
>>> Here are some more logs:
>>>
>>> 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical
>>> network id=201 based on requested tags mellanoxvxlan
>>> 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical
>>> network id=201 based on requested tags mellanoxvxlan
>>> 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network, the physical isolation type is not BCF_SEGMENT
>>> 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,767 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,769 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) SSP not
>>> configured to be active
>>> 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design this network
>>> 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>> design network using network offering 19 on physical network 201
>>> 2018-02-06 11:20:27,770 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Releasing lock
>>> for Acct[6af2875b-04fc-11e8-923e-002590474525-admin]
>>> 2018-02-06 11:20:27,789 DEBUG [c.c.u.d.T.Transaction]
>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Rolling back the
>>> transaction: Time = 38 Name = qtp788117692-390; called by
>>> -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-TransactionLegacy.close:656-Transaction.execute:43-Transaction.execute:47-NetworkOrchestrator.createGuestNetwork:2315-NetworkServiceImpl$4.doInTransaction:1383-NetworkServiceImpl$4.doInTransaction:1331-Transaction.execute:40-NetworkServiceImpl.commitNetwork:1331-NetworkServiceImpl.createGuestNetwork:1294-NativeMethodAccessorImpl.invoke0:-2
>>> 2018-02-06 11:20:27,798 ERROR [c.c.a.ApiServer] (qtp788117692-390:ctx-f1a980be
>>> ctx-61be30e8) (logid:0ca0c866) unhandled exception executing api command:
>>> [Ljava.lang.String;@43b9df02
>>> com.cloud.utils.exception.CloudRuntimeException: Unable to convert network
>>> offering with specified id to network profile
>>> at
>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:726)
>>> at
>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2364)
>>> at
>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2315)
>>> at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:50)
>>> at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
>>> at com.cloud.utils.db.Transaction.execute(Transaction.java:47)
>>>
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>> Nicolas.Vazquez@shapeblue.com
>>> www.shapeblue.com<http://www.shapeblue.com>
>>> ,
> > > @shapeblue
Re: Refusing to design this network, the physical isolation type is
not BCF_SEGMENT
Posted by Nux! <nu...@li.nux.ro>.
And thank you for fixing it!
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Nicolas Vazquez" <Ni...@shapeblue.com>
> To: "dev" <de...@cloudstack.apache.org>
> Sent: Monday, 5 March, 2018 11:16:44
> Subject: Re: Refusing to design this network, the physical isolation type is not BCF_SEGMENT
> Solved, thanks for testing and raising the issue! This will be included on
> 4.11.1
>
> ________________________________
> From: Nux! <nu...@li.nux.ro>
> Sent: Thursday, February 8, 2018 1:03:29 PM
> To: dev
> Subject: Re: Refusing to design this network, the physical isolation type is not
> BCF_SEGMENT
>
> Tested, now I can add L2 network on the back of vxlan phsyical network, but I
> have found a problem.
>
> It doesn't seem to like VNI ids higher than those for VLANs which is 4096,
> however VXLAN's max id is about 16 millions, so this is a problem that needs a
> fix.
>
> Here are some logs:
>
> 2018-02-08 15:50:00,738 WARN [resource.wrapper.LibvirtStartCommandWrapper]
> (agentRequest-Handler-4:null) (logid:bd9fbea5) InternalErrorException
> com.cloud.exception.InternalErrorException: Failed to create vnet 33333:
> RTNETLINK answers: Numerical result out of rangeCannot find device
> "bond0.33333"Failed to create vlan 33333 on pif: bond0.
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
>
> Nicolas.Vazquez@shapeblue.com
> www.shapeblue.com
> ,
> @shapeblue
>
>
>
> ----- Original Message -----
>> From: "Nux!" <nu...@li.nux.ro>
>> To: "dev" <de...@cloudstack.apache.org>
>> Sent: Thursday, 8 February, 2018 14:29:36
>> Subject: Re: Refusing to design this network, the physical isolation type is not
>> BCF_SEGMENT
>
>> Thanks! Any idea where blueorangutan keeps the rpms?
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> ----- Original Message -----
>>> From: "Nicolas Vazquez" <Ni...@shapeblue.com>
>>> To: "dev" <de...@cloudstack.apache.org>
>>> Sent: Wednesday, 7 February, 2018 12:12:00
>>> Subject: Re: Refusing to design this network, the physical isolation type is not
>>> BCF_SEGMENT
>>
>>> I have pushed a fix for this on PR 2448. Can you please test it?
>>>
>>> ________________________________
>>> From: Nux! <nu...@li.nux.ro>
>>> Sent: Tuesday, February 6, 2018 10:25:07 AM
>>> To: dev
>>> Subject: Re: Refusing to design this network, the physical isolation type is not
>>> BCF_SEGMENT
>>>
>>> Thanks Nicolas, much appreciated.
>>> Once you have a patch, feel free to ping me so I can test.
>>>
>>> --
>>> Sent from the Delta quadrant using Borg technology!
>>>
>>> Nux!
>>> www.nux.ro
>>>
>>>
>>> Nicolas.Vazquez@shapeblue.com
>>> www.shapeblue.com<http://www.shapeblue.com>
>>> ,
>>> @shapeblue
>>>
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Nicolas Vazquez" <Ni...@shapeblue.com>
>>>> To: "dev" <de...@cloudstack.apache.org>
>>>> Sent: Tuesday, 6 February, 2018 13:23:54
>>>> Subject: Re: Refusing to design this network, the physical isolation type is not
>>>> BCF_SEGMENT
>>>
>>>> Hi Lucian,
>>>>
>>>>
>>>> Thanks for posting this issue. I have checked the canHandle() method on
>>>> VxlanGuestNetworkGuru and it is not considering L2 network offerings, only
>>>> Isolated, so it refuses to design the network. I'll make sure to include a fix
>>>> for it on 4.11.1.
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Nicolas
>>>>
>>>> ________________________________
>>>> From: Nux! <nu...@li.nux.ro>
>>>> Sent: Tuesday, February 6, 2018 8:30:03 AM
>>>> To: dev
>>>> Subject: [L2 network] [VXLAN] Refusing to design this network, the physical
>>>> isolation type is not BCF_SEGMENT
>>>>
>>>> Hi,
>>>>
>>>> I'm trying to add an L2 network based on a VXLAN physical network and I am
>>>> getting the error in the subject.
>>>>
>>>> If I use a VLAN based physical network all completes successfully and I end up
>>>> with an L2 network in green "Setup" state.
>>>>
>>>> Here are some more logs:
>>>>
>>>> 2018-02-06 11:20:27,748 DEBUG [c.c.n.NetworkServiceImpl]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical
>>>> network id=201 based on requested tags mellanoxvxlan
>>>> 2018-02-06 11:20:27,749 DEBUG [c.c.n.NetworkServiceImpl]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Found physical
>>>> network id=201 based on requested tags mellanoxvxlan
>>>> 2018-02-06 11:20:27,766 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>>> design this network, the physical isolation type is not BCF_SEGMENT
>>>> 2018-02-06 11:20:27,766 DEBUG [o.a.c.n.c.m.ContrailGuru]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>>> design this network
>>>> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>>> design this network
>>>> 2018-02-06 11:20:27,767 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>>> design this network
>>>> 2018-02-06 11:20:27,767 DEBUG [c.c.n.g.OvsGuestNetworkGuru]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>>> design this network
>>>> 2018-02-06 11:20:27,769 DEBUG [o.a.c.n.g.SspGuestNetworkGuru]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) SSP not
>>>> configured to be active
>>>> 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>>> design this network
>>>> 2018-02-06 11:20:27,769 DEBUG [c.c.n.g.NuageVspGuestNetworkGuru]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Refusing to
>>>> design network using network offering 19 on physical network 201
>>>> 2018-02-06 11:20:27,770 DEBUG [o.a.c.e.o.NetworkOrchestrator]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Releasing lock
>>>> for Acct[6af2875b-04fc-11e8-923e-002590474525-admin]
>>>> 2018-02-06 11:20:27,789 DEBUG [c.c.u.d.T.Transaction]
>>>> (qtp788117692-390:ctx-f1a980be ctx-61be30e8) (logid:0ca0c866) Rolling back the
>>>> transaction: Time = 38 Name = qtp788117692-390; called by
>>>> -TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-TransactionLegacy.close:656-Transaction.execute:43-Transaction.execute:47-NetworkOrchestrator.createGuestNetwork:2315-NetworkServiceImpl$4.doInTransaction:1383-NetworkServiceImpl$4.doInTransaction:1331-Transaction.execute:40-NetworkServiceImpl.commitNetwork:1331-NetworkServiceImpl.createGuestNetwork:1294-NativeMethodAccessorImpl.invoke0:-2
>>>> 2018-02-06 11:20:27,798 ERROR [c.c.a.ApiServer] (qtp788117692-390:ctx-f1a980be
>>>> ctx-61be30e8) (logid:0ca0c866) unhandled exception executing api command:
>>>> [Ljava.lang.String;@43b9df02
>>>> com.cloud.utils.exception.CloudRuntimeException: Unable to convert network
>>>> offering with specified id to network profile
>>>> at
>>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:726)
>>>> at
>>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2364)
>>>> at
>>>> org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2315)
>>>> at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:50)
>>>> at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
>>>> at com.cloud.utils.db.Transaction.execute(Transaction.java:47)
>>>>
>>>>
>>>> --
>>>> Sent from the Delta quadrant using Borg technology!
>>>>
>>>> Nux!
>>>> www.nux.ro
>>>>
>>>> Nicolas.Vazquez@shapeblue.com
>>>> www.shapeblue.com<http://www.shapeblue.com>
>>>> ,
> > > > @shapeblue