[Yahoo-eng-team] [Bug 2049121] [NEW] Boot one VM with two GPU(in same numa)by pci passthrough cannot have GPUDirect P2P capability

Public bug reported: Hi, I have two GPU cards, all of them was connect with one same numa CPU socket as below link info: https://paste.opendev.org/show/b7Qi8qCnbLVxO2W0JdQw/ I can boot one nova instance successfully with the two GPU cards by PCI Passthrough way. but in the booted instances,

[Yahoo-eng-team] [Bug 2049120] [NEW] Unable to upgrade nova-compute to 2023.1 due to existing hostname

Public bug reported: Our hypervisors were all originally registered with their short names. After upgrading to 2023.1, it looks like nova-compute now relies on libvirt, which provides an FQDN, for the hosts' names and the service fails to start with this error: Error starting thread.:

[Yahoo-eng-team] [Bug 2049067] [NEW] Information about interfaces of shared network are missing in network topology

Public bug reported: In network topology page, interfaces table in RouterDetailView includes both interfaces in the current project's networks and also interfaces in the shared networks in other projects. But all information except the id_or_name of the interfaces in the shared networks are

[Yahoo-eng-team] [Bug 2049064] [NEW] Unit/functional test failures with oslo.limit 2.3.0

Public bug reported: Description === The new oslo.limit 2.3.0 release introduced the validation to ensure the [oslo_limit] endpoint_id option is set. However this change broke some unit/functional test cases which enable unified quota implementation without setting this option. Steps

[Yahoo-eng-team] [Bug 2049030] [NEW] request_spec out of sync with instance details

Public bug reported: Description === We have an OpenStack Zed running based on the Ubuntu cloud archive packages. We regularly live-migrate instances between hypervisors for host maintenance, but suddenly had issues with many instances. Nova correctly refused to migrate an instance from