Public bug reported:
Description =========== When shelving an instance, the instance is removed from the compute and the image is uploaded to glance. But, after completion, the port binding on neutron side is staying. This is not a big issue in most of the case, but some operators (like OVHcloud) rely on strong consistency between nova and neutron and expect the binding to be updated to avoid orphans. As stated on IRC with sean-k-mooney, this behavior was already spotted while working on another subject (see [1]). Steps to reproduce ================== # Boot an instance openstack server create ... # Wait for it to be fully booted, then shelve: openstack server shelve 57b3cbf6-9aa4-4da2-90ab-20cf518ea38e # Wait for shelve to be completed (offloaded) openstack server show 57b3cbf6-9aa4-4da2-90ab-20cf518ea38e ... | OS-EXT-STS:vm_state | shelved_offloaded ... # List ports associated to the instance: openstack port list --server 57b3cbf6-9aa4-4da2-90ab-20cf518ea38e # Show the port: openstack port show f9144ff9-4261-476f-98f9-de0750f3db1a ... | binding_host_id | compute-5 | binding_vif_type | ovs ... Expected result =============== ... | binding_host_id | | binding_vif_type | unbound ... Environment =========== OpenStack victoria, but master is also affected [1] https://review.opendev.org/c/openstack/nova/+/832330/7/nova/tests/functional/libvirt/test_pci_sriov_servers.py#1286 ** Affects: nova Importance: Undecided Status: New ** Summary changed: - Shelved (offloaded) instance still have port binded to host + Shelved (offloaded) instance still have port bound to host -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1983471 Title: Shelved (offloaded) instance still have port bound to host Status in OpenStack Compute (nova): New Bug description: Description =========== When shelving an instance, the instance is removed from the compute and the image is uploaded to glance. But, after completion, the port binding on neutron side is staying. This is not a big issue in most of the case, but some operators (like OVHcloud) rely on strong consistency between nova and neutron and expect the binding to be updated to avoid orphans. As stated on IRC with sean-k-mooney, this behavior was already spotted while working on another subject (see [1]). Steps to reproduce ================== # Boot an instance openstack server create ... # Wait for it to be fully booted, then shelve: openstack server shelve 57b3cbf6-9aa4-4da2-90ab-20cf518ea38e # Wait for shelve to be completed (offloaded) openstack server show 57b3cbf6-9aa4-4da2-90ab-20cf518ea38e ... | OS-EXT-STS:vm_state | shelved_offloaded ... # List ports associated to the instance: openstack port list --server 57b3cbf6-9aa4-4da2-90ab-20cf518ea38e # Show the port: openstack port show f9144ff9-4261-476f-98f9-de0750f3db1a ... | binding_host_id | compute-5 | binding_vif_type | ovs ... Expected result =============== ... | binding_host_id | | binding_vif_type | unbound ... Environment =========== OpenStack victoria, but master is also affected [1] https://review.opendev.org/c/openstack/nova/+/832330/7/nova/tests/functional/libvirt/test_pci_sriov_servers.py#1286 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1983471/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp