Trunk subport's port status and binding:host_id don't updated after live-migration
Bug #1914747 reported by
Slawek Kaplonski
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Slawek Kaplonski |
Bug Description
It happens for me in ml2/ovs env for sure.
How to reproduce the issue:
1. Create trunk with some subport,
2. Spawn vm with plugged to the trunk's parent port,
3. Check status of trunk's parent port and subport's port - both are ACTIVE and have correct host_id,
4. Live-migrate vm
5. Check status of trunk's parent port and subport's port - subport is DOWN and has old host_id.
Due to that, if e.g. dvr and l2pop are used, connectivity to such subport is broken.
To fix it I needed to restart neutron-ovs-agent on the host to which vm was migrated to.
Changed in neutron: | |
status: | Confirmed → Fix Released |
tags: | added: neutron-proactive-backport-potential |
To post a comment you must log in.
Proposed fix: https:/ /review. opendev. org/c/openstack /neutron/ +/774245