Reviewed: https://review.openstack.org/289458 Committed: https://git.openstack.org/cgit/openstack/operations-guide/commit/?id=610019c45496e17a8094d535c856d9de9a16f123 Submitter: Jenkins Branch: master
commit 610019c45496e17a8094d535c856d9de9a16f123 Author: Andreas Scheuring <[email protected]> Date: Mon Mar 7 18:13:18 2016 +0100 Ops: Update Compute Node Failure section with Neutron content Adding content describing how to fix the Neutron ML2 database in the case of a total compute node failure. Change-Id: I4712f604f798c6c9ebb6f9d8d82b63d8ac2ed599 Closes-Bug: #1282956 ** Changed in: openstack-manuals Status: In Progress => Fix Released -- 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: Fix Released 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 : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
