that worked! Additional queries to do:
use neutron
update ml2_port_bindings set host = 'new-host' where host = 'old-host';
update ml2_port_binding_levels set host = 'new-host' where host = 'old-host';
Setting Neutron to won't fix and adding bug against docs + providing a fix.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1282956
Title:
ML2 : hard reboot a VM after a compute crash
Status in neutron:
Won't Fix
Status in openstack-manuals:
New
Bug description:
I run in multi node setup with ML2, L2-population and Linuxbridge MD,
and vxlan TypeDriver.
I start two compute-nodes, I launch a VM, and I shutdown the compute-
node which host the VM.
I use this process to relaunch the VM on the other compute-node :
http://docs.openstack.org/trunk/openstack-
ops/content/maintenance.html#totle_compute_node_failure
Once the VM is launched on the other compute node, fdb entries and
neighbouring entries are no more populated on the network-node nor on
the compute node
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1282956/+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
