[Bug 2072154] Re: Port status goes BUILD when migrating non-sriov instance in sriov setting.
Seyeong Kim
2072154 at bugs.launchpad.net
Sat Dec 14 03:37:19 UTC 2024
I verified zed
root at node-05:/home/ubuntu# dpkg -l | grep neutron
ii neutron-common 2:21.2.0-0ubuntu1~cloud1 all Neutron is a virtual network service for Openstack - common
ii neutron-ovn-metadata-agent 2:21.2.0-0ubuntu1~cloud1 all Neutron is a virtual network service for Openstack - OVN metadata agent
ii neutron-sriov-agent 2:21.2.0-0ubuntu1~cloud1 all Neutron is a virtual network service for Openstack - SR-IOV agent
ii python3-neutron 2:21.2.0-0ubuntu1~cloud1 all Neutron is a virtual network service for Openstack - Python library
** Tags removed: verification-zed-needed
** Tags added: verification-zed-done
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/2072154
Title:
Port status goes BUILD when migrating non-sriov instance in sriov
setting.
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive antelope series:
Fix Committed
Status in Ubuntu Cloud Archive bobcat series:
Fix Committed
Status in Ubuntu Cloud Archive caracal series:
Fix Committed
Status in Ubuntu Cloud Archive dalmation series:
Fix Released
Status in Ubuntu Cloud Archive epoxy series:
Fix Released
Status in Ubuntu Cloud Archive yoga series:
Fix Committed
Status in Ubuntu Cloud Archive zed series:
Fix Committed
Status in neutron:
Fix Released
Status in neutron package in Ubuntu:
Fix Released
Status in neutron source package in Jammy:
Fix Released
Status in neutron source package in Noble:
Fix Released
Status in neutron source package in Oracular:
Fix Released
Bug description:
[ Impact ]
Port status goes BUILD when migrating non-sriov instance in sriov
setting.
[ Test Plan ]
1. Deploy OpenStack using Juju & Charms ( upstream also has the same code )
2. Enable SRIOV
3. create a vm without sriov nic. (test)
4. migrate it to another host
- openstack server migrate --live-migration --os-compute-api-version 2.30 --host node-04.maas test
5. check port status
- https://paste.ubuntu.com/p/RKGnP76MvB/
[ Where problems could occur ]
this patch is related to sriov agent. it adds checking if port is
sriov or not. so it could be possible that sriov port can be handled
inproperly.
[ Other Info ]
nova-compute has neutron-sriov-nic-agent and neutron-ovn-metadata-
agent
So far, I've checked that
ovn_monitor change it to ACTIVE but sriov-nic-agent change it back to
BUILD by calling _get_new_status
./plugins/ml2/drivers/mech_sriov/agent/sriov_nic_agent.py
binding_activate
- get_device_details_from_port_id
- get_device_details
- _get_new_status < this makes status BUILD.
so as running order is not fixed, sometimes it goes ACTIVE, sometimes
BUILD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/2072154/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list