Friday, 2026-08-14

opendevreviewRico Lin proposed openstack/nova master: compute: add skip_inventory_in_use_errors opt  https://review.opendev.org/c/openstack/nova/+/98575008:29
opendevreviewBhavana proposed openstack/nova-specs master: Add spec for MIG-aware PCI Host Weigher  https://review.opendev.org/c/openstack/nova-specs/+/99875309:12
opendevreviewKamil Sambor proposed openstack/nova master: Fix pickling error that forces oslo.service to fall back to fork  https://review.opendev.org/c/openstack/nova/+/100095610:08
opendevreviewPierre Libeau proposed openstack/nova master: libvirt: Add reproducer for unstable vNIC PCI addresses on hard reboot  https://review.opendev.org/c/openstack/nova/+/100096112:09
opendevreviewPierre Libeau proposed openstack/nova master: libvirt: Render guest interface PCI address in config  https://review.opendev.org/c/openstack/nova/+/100096212:09
opendevreviewPierre Libeau proposed openstack/nova master: libvirt: Preserve vNIC guest PCI address on domain XML regeneration  https://review.opendev.org/c/openstack/nova/+/100096312:09
plibeauhi — opinions wanted on https://bugs.launchpad.net/nova/+bug/2163417 : vNIC guest PCI slots get reshuffled on hard reboot (multi-NIC appliances see port1/port2 swapped). nova never pins the VIF guest PCI address, libvirt renumbers from XML order; MAC is the only invariant. reproduced on clean master12:43
plibeauI have a WIP opt-in (3 commits above) [libvirt] preserve_vif_pci_addresses re-pinning by MAC from old_guest (hard reboot/power_on/resume only). is that the right direction, or should the slot be persisted per-VIF? or is "use device role tagging" the intended answer?12:45
gibiplibeau: I think we never promised the guest that the pci slot ordering is stable. Tagging devices are the way to map ports to devices afaik12:47
plibeauyes and linux by default manage that correctly because it use mac address and not pci slot to manage NIC but it's not the case of some and specially appliance. What do you think to try to improve that for this type of use case?12:53
gibiplibeau: I mean you can tag the nic and block devices in the nova api when add it to your server, then the VM can read the tagging from the metadata12:56
gibithat should be OS independent12:56
amorinyes, but some OS are not able to do that, the proposition from plibeau is to try to keep the order as much as possible to avoid order change when it's possible12:57
gibiamorin: you mean there are OSes that are not able to read the metadata API?13:01
gibior read the metadat from the config drive?13:01
amorinyup13:02
amorinsome of our customers complain about this13:02
gibiis it possible that they could read but don't want to? Sorry I'm suspicious here as it is a very basic fuctionality to read a file from an attached disk or do http request13:02
amorinI totally agree with you :) They usually rely on providers to give them images and they seems not able to do so in an easy way13:03
amorinplibeau will have more info, I dont remember the name of the image?13:03
gibiamorin: you can propose a feature (or ask this on the IRC meeting) to start providing a stable order of PCI devices to guests to get the oppinion of others but this was rejected before with the above argument13:05
plibeauFortinet is the name :) but not only and the customer can't fix also because it's appliance, he don't have root access on it13:05
gibican this be brougth up to Frotinet then? to integrate with cloud VMs by reading the metadata? :) 13:07
gibiI feel like either Fortinet supports to run in OpenStack or isn't :)13:09
plibeauyes, fix on Fortinet side is a solution but we need to fix also probably other case. I think yes Fortinet is supported on openstack I see some documentation how to deploy it above openstack13:15
opendevreviewGhanshyam Maan proposed openstack/nova master: Unify the thread pool executors into a central factory  https://review.opendev.org/c/openstack/nova/+/99857113:38
gmaangibi: ^^ added the test coverage13:58
gibigmaan: thanks. I will check it soon13:59
gmaanthanks14:01
gibi+214:01
gibithanks14:01
opendevreviewGhanshyam Maan proposed openstack/nova master: Shutdown thread pool executors during graceful shutdown  https://review.opendev.org/c/openstack/nova/+/100021114:01
opendevreviewGhanshyam Maan proposed openstack/nova master: Add doc and release notes for the graceful shutdown task tracking  https://review.opendev.org/c/openstack/nova/+/99714114:01
opendevreviewTobias Urdin proposed openstack/nova master: Catch ValueError from from_image_ref in rescue  https://review.opendev.org/c/openstack/nova/+/100096914:15
gmaangibi: and this is graceful shutdown part to shutdown executors which i separated from the original change https://review.opendev.org/c/openstack/nova/+/100021114:48
opendevreviewBalazs Gibizer proposed openstack/nova master: Stabilize functional test for slow instance.save  https://review.opendev.org/c/openstack/nova/+/99912114:59
opendevreviewBalazs Gibizer proposed openstack/nova master: Make functional-py313-threading voting  https://review.opendev.org/c/openstack/nova/+/99721614:59
opendevreviewBalazs Gibizer proposed openstack/nova master: Fix test_fill_vifs_migration under native threading  https://review.opendev.org/c/openstack/nova/+/100078014:59
opendevreviewBalazs Gibizer proposed openstack/nova master: Stabilize func test waiting for VM ERROR state  https://review.opendev.org/c/openstack/nova/+/100097114:59
opendevreviewBalazs Gibizer proposed openstack/nova master: Stabilize func test waiting for VM ERROR state  https://review.opendev.org/c/openstack/nova/+/99882215:00
opendevreviewBalazs Gibizer proposed openstack/nova master: Stabilize functional test for slow instance.save  https://review.opendev.org/c/openstack/nova/+/99912115:00
opendevreviewBalazs Gibizer proposed openstack/nova master: Make functional-py313-threading voting  https://review.opendev.org/c/openstack/nova/+/99721615:00
opendevreviewBalazs Gibizer proposed openstack/nova master: Fix test_fill_vifs_migration under native threading  https://review.opendev.org/c/openstack/nova/+/100078015:00
gibigmaan: thank for the suggestion in the stabilization series ^^ I applied it15:05
gmaangibi: ack will check today15:05
opendevreviewPierre Libeau proposed openstack/nova master: libvirt: Add reproducer for unstable vNIC PCI addresses on hard reboot  https://review.opendev.org/c/openstack/nova/+/100096115:49
opendevreviewPierre Libeau proposed openstack/nova master: libvirt: Render guest interface PCI address in config  https://review.opendev.org/c/openstack/nova/+/100096215:49
opendevreviewPierre Libeau proposed openstack/nova master: libvirt: Preserve vNIC guest PCI address on domain XML regeneration  https://review.opendev.org/c/openstack/nova/+/100096315:49
opendevreviewMerged openstack/os-traits master: Add HW_NVME capability traits  https://review.opendev.org/c/openstack/os-traits/+/99992116:31
opendevreviewMerged openstack/nova master: Task tracking mechanism for graceful shutdown  https://review.opendev.org/c/openstack/nova/+/99629917:48
opendevreviewGhanshyam Maan proposed openstack/nova master: Shutdown thread pool executors during graceful shutdown  https://review.opendev.org/c/openstack/nova/+/100021117:58
opendevreviewGhanshyam Maan proposed openstack/nova master: Unify the thread pool executors into a central factory  https://review.opendev.org/c/openstack/nova/+/99857118:29
opendevreviewGhanshyam Maan proposed openstack/nova master: Shutdown thread pool executors during graceful shutdown  https://review.opendev.org/c/openstack/nova/+/100021118:30

Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!