Migration scenarios are not supported
Bug #1630631 reported by
radu puscas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tap-as-a-service |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
When migrating a VM tapped in both directions from one compute to another:
1. The outbound ovs flow(in_port=x) is automatically deleted because the ovs in_port disappears.
2. The inbound ovs flow(dl_src=mac) is not removed.
If I try to delete the tap flow after the migration happens, the delete call will go to the compute node where the migrated VM is now located.
The ovs inbound flow on the old compute is never deleted. The only way to get rid of it is to reboot the compute.
| tags: | added: ovs |
| Changed in tap-as-a-service: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
To post a comment you must log in.
