ML2 : hard reboot a VM after a compute crash
Bug #1282956 reported by
Mathieu Rohon
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Medium
|
Unassigned | ||
openstack-manuals |
Fix Released
|
Undecided
|
Andreas Scheuring |
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://
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
summary: |
- l2-population : hard reboot a VM after a compute crash + ML2 : hard reboot a VM after a compute crash |
Changed in neutron: | |
status: | Incomplete → New |
tags: | added: network |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in neutron: | |
assignee: | nobody → Sandhya Dasu (sadasu) |
tags: | added: neutron |
no longer affects: | nova |
tags: | removed: havana-backport-potential |
Changed in neutron: | |
assignee: | Sandhya Dasu (sadasu) → nobody |
To post a comment you must log in.
Can you check the log files if there are any errors or provide them? What's 'fdb' entries and neighbouring entries?