[Bug 2072154] Re: Port status goes BUILD when migrating non-sriov instance in sriov setting.

[Seyeong Kim]

** Changed in: neutron (Ubuntu Oracular)
       Status: New => In Progress

** Changed in: neutron (Ubuntu Oracular)
     Assignee: (unassigned) => Seyeong Kim (seyeongkim)

** Changed in: neutron (Ubuntu Focal)
     Assignee: (unassigned) => Seyeong Kim (seyeongkim)

** Changed in: neutron (Ubuntu Jammy)
     Assignee: (unassigned) => Seyeong Kim (seyeongkim)

** Changed in: neutron (Ubuntu Noble)
     Assignee: (unassigned) => Seyeong Kim (seyeongkim)

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/2072154

Title:
  Port status goes BUILD when migrating non-sriov instance in sriov
  setting.

Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  In Progress
Status in neutron source package in Focal:
  New
Status in neutron source package in Jammy:
  New
Status in neutron source package in Noble:
  New
Status in neutron source package in Oracular:
  In Progress

Bug description:
  [ Impact ]

  Port status goes BUILD when migrating non-sriov instance in sriov
  setting.

  [ Test Plan ]

  1. Deploy Antelope with juju ( 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/neutron/+bug/2072154/+subscriptions