It was an invalid user configuration.
The "dvr"node was not configured with the right agent mode, and so this
issue was seen.
Please ignore this bug.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1541714
Title:
DVR routers are not created on a compute node that runs agent in 'dvr'
mode
Status in neutron:
Invalid
Bug description:
DVR routers are not created on a compute node that is running L3 agent
in "dvr" mode.
This might have been introduced by the latest patch that changed the
scheduling behavior.
https://review.openstack.org/#/c/254837/
Steps to reproduce:
1. Stack up two nodes. ( dvr_snat node) and (dvr node)
2. Create a Network
3. Create a Subnet
4. Create a Router
5. Add Subnet to the Router
6. Create a VM on the "dvr_snat" node.
Everything works fine here. We can see the router-namespace, snat-namespace
and the dhcp-namespace.
7. Now Create a VM and force the VM to be created on the second node ( dvr
node).
- nova boot --flavor xyz --image abc --net net-id yyy-id
--availability-zone nova:dvr-node myinstance2
Now see the image is created in the second node.
But the router namespace is missing in the second node.
The router is scheduled to the dvr-snat node, but not to the compute
node.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1541714/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
