Public bug reported:
I have a setup with 2 Network nodes, with bridge_mappings of l2 agents as
follows.
Network Node 1 : bridge_mappings: provider:10:1000
Network Node 2 : bridge_mappings: physnet1:1000:1500
Now, I create a provider network.
neutron net-create net1 --provider:network_type vlan
--provider:physical_network physnet1
Now, when I add a port to that network, the network gets scheduled to
NN1, in which physical_network "physnet1" has no meaning.
Solution:
A pre-check to be added while scheduling a provider network, whether physical
network specified exists in the bridge_mappings config of the respective NN
node.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: neutron ovs vlan
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1521071
Title:
Network connectivity fails when a provider network is scheduled to a
Node which has invalid physical network mappings
Status in neutron:
New
Bug description:
I have a setup with 2 Network nodes, with bridge_mappings of l2 agents as
follows.
Network Node 1 : bridge_mappings: provider:10:1000
Network Node 2 : bridge_mappings: physnet1:1000:1500
Now, I create a provider network.
neutron net-create net1 --provider:network_type vlan
--provider:physical_network physnet1
Now, when I add a port to that network, the network gets scheduled to
NN1, in which physical_network "physnet1" has no meaning.
Solution:
A pre-check to be added while scheduling a provider network, whether physical
network specified exists in the bridge_mappings config of the respective NN
node.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1521071/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
