yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #89631
[Bug 1988549] [NEW] Trunk status is down after a live-migration
Public bug reported:
After live-migrating a trunk VM the network trunk status remains in a
DOWN state even if the subports and parent port status is ACTIVE and
there is connectivity between subports and to the trunk port.
stepts to reproduce:
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, subport's port and trunk itself- all ACTIVE
4. Live-migrate vm
5. Check status of trunk's parent port and subport's port and trunk itself - subport and parent port status is UP but trunk itself has DOWN status.
Info:
(overcloud) [stack@undercloud-0 ~]$ openstack server event list ovn-migration-server-trunk-ext-pinger-1
+------------------------------------------+--------------------------------------+--------+----------------------------+
| Request ID | Server ID | Action | Start Time |
+------------------------------------------+--------------------------------------+--------+----------------------------+
| req-93485625-4e4f-40f0-89a6-104853eceee5 | 8ded64a4-6675-462c-8276-663a46f8efa9 | create | 2022-09-01T20:51:14.000000 |
+------------------------------------------+--------------------------------------+--------+----------------------------+
(overcloud) [stack@undercloud-0 ~]$ openstack port list | grep -ext-pinger-1
| de281f6b-afab-424f-a05e-058cabc42b53 | ovn-migration-port-trunk-ext-pinger-1-subport | fa:16:3e:bc:b6:96 | ip_address='192.168.200.178', subnet_id='e54a235d-1337-4f78-ba64-1c3d1f21c97e' | ACTIVE |
| fca6bb27-a0a1-47fb-bb37-b6aa53121248 | ovn-migration-port-trunk-ext-pinger-1 | fa:16:3e:bc:b6:96 | ip_address='10.0.0.218', subnet_id='f0ef20d3-5769-478c-bbfd-7384d5ffb284' | ACTIVE |
(overcloud) [stack@undercloud-0 ~]$ openstack network trunk show ovn-migration-trunk-pinger-1 -f value -c status
ACTIVE
(overcloud) [stack@undercloud-0 ~]$ openstack server migrate --live-migration --host compute-0.redhat.local --block-migration --wait ovn-migration-server-trunk-ext-pinger-1
Complete
(overcloud) [stack@undercloud-0 ~]$ openstack port list | grep -ext-pinger-1
| de281f6b-afab-424f-a05e-058cabc42b53 | ovn-migration-port-trunk-ext-pinger-1-subport | fa:16:3e:bc:b6:96 | ip_address='192.168.200.178', subnet_id='e54a235d-1337-4f78-ba64-1c3d1f21c97e' | ACTIVE |
| fca6bb27-a0a1-47fb-bb37-b6aa53121248 | ovn-migration-port-trunk-ext-pinger-1 | fa:16:3e:bc:b6:96 | ip_address='10.0.0.218', subnet_id='f0ef20d3-5769-478c-bbfd-7384d5ffb284' | ACTIVE |
(overcloud) [stack@undercloud-0 ~]$ openstack network trunk show ovn-migration-trunk-pinger-1 -f value -c status
DOWN
** Affects: neutron
Importance: Undecided
Assignee: Arnau Verdaguer (averdagu)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => Arnau Verdaguer (averdagu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1988549
Title:
Trunk status is down after a live-migration
Status in neutron:
In Progress
Bug description:
After live-migrating a trunk VM the network trunk status remains in a
DOWN state even if the subports and parent port status is ACTIVE and
there is connectivity between subports and to the trunk port.
stepts to reproduce:
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, subport's port and trunk itself- all ACTIVE
4. Live-migrate vm
5. Check status of trunk's parent port and subport's port and trunk itself - subport and parent port status is UP but trunk itself has DOWN status.
Info:
(overcloud) [stack@undercloud-0 ~]$ openstack server event list ovn-migration-server-trunk-ext-pinger-1
+------------------------------------------+--------------------------------------+--------+----------------------------+
| Request ID | Server ID | Action | Start Time |
+------------------------------------------+--------------------------------------+--------+----------------------------+
| req-93485625-4e4f-40f0-89a6-104853eceee5 | 8ded64a4-6675-462c-8276-663a46f8efa9 | create | 2022-09-01T20:51:14.000000 |
+------------------------------------------+--------------------------------------+--------+----------------------------+
(overcloud) [stack@undercloud-0 ~]$ openstack port list | grep -ext-pinger-1
| de281f6b-afab-424f-a05e-058cabc42b53 | ovn-migration-port-trunk-ext-pinger-1-subport | fa:16:3e:bc:b6:96 | ip_address='192.168.200.178', subnet_id='e54a235d-1337-4f78-ba64-1c3d1f21c97e' | ACTIVE |
| fca6bb27-a0a1-47fb-bb37-b6aa53121248 | ovn-migration-port-trunk-ext-pinger-1 | fa:16:3e:bc:b6:96 | ip_address='10.0.0.218', subnet_id='f0ef20d3-5769-478c-bbfd-7384d5ffb284' | ACTIVE |
(overcloud) [stack@undercloud-0 ~]$ openstack network trunk show ovn-migration-trunk-pinger-1 -f value -c status
ACTIVE
(overcloud) [stack@undercloud-0 ~]$ openstack server migrate --live-migration --host compute-0.redhat.local --block-migration --wait ovn-migration-server-trunk-ext-pinger-1
Complete
(overcloud) [stack@undercloud-0 ~]$ openstack port list | grep -ext-pinger-1
| de281f6b-afab-424f-a05e-058cabc42b53 | ovn-migration-port-trunk-ext-pinger-1-subport | fa:16:3e:bc:b6:96 | ip_address='192.168.200.178', subnet_id='e54a235d-1337-4f78-ba64-1c3d1f21c97e' | ACTIVE |
| fca6bb27-a0a1-47fb-bb37-b6aa53121248 | ovn-migration-port-trunk-ext-pinger-1 | fa:16:3e:bc:b6:96 | ip_address='10.0.0.218', subnet_id='f0ef20d3-5769-478c-bbfd-7384d5ffb284' | ACTIVE |
(overcloud) [stack@undercloud-0 ~]$ openstack network trunk show ovn-migration-trunk-pinger-1 -f value -c status
DOWN
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1988549/+subscriptions
Follow ups