| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2026-03-20 | |||
| 14:29:49 | sean-k-mooney | os_distro="debian" | |
| 14:29:51 | sean-k-mooney | os_version="13" | |
| 14:30:07 | sean-k-mooney | but the spec defied that os_distro="debian13" woudl be required | |
| 14:30:14 | sean-k-mooney | i.e that only os_distro woudl be used | |
| 14:30:23 | sean-k-mooney | even though os_version exsited | |
| 14:30:32 | sean-k-mooney | so that is a breakign api change in my view | |
| 14:30:45 | sean-k-mooney | as it will chenat the behvior for exsitng images | |
| 14:31:18 | sean-k-mooney | so i woudl close it as invalid but im biased again that feature as i personlly want to remove the libosinfo functionality entrily | |
| 14:31:26 | sean-k-mooney | i belive it was a mistake to ever include it | |
| 14:31:53 | sean-k-mooney | becuase it does nto provdie stable bevhor across version as they assuem the domian will not be deleted and recreated and rely on that for stablity | |
| 14:32:24 | sean-k-mooney | nova deletes and recreates the domain all the time so if you sue the libosinfo fucntionaltiy you can get unexpected bhavior in nova when you do a package update | |
| 14:33:28 | sean-k-mooney | i partly mitigated that in the past i think but it still makes me uneasey so i woudl mark this opion and whishlist | |
| 14:33:56 | sean-k-mooney | i dont think it woudl be safe to turn this on by defautl (looking at both disto and version) without a flag to opt in | |
| 14:34:34 | sean-k-mooney | they are totally right to expect it to look at both its just not how it was implmeented unfortunetly | |
| 14:35:01 | sean-k-mooney | https://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/libvirt-hardware-policy-from-libosinfo.html | |
| 14:35:39 | sean-k-mooney | the spec actully say it use –property os_name=fedora21 but i woudl have to double check that | |
| 14:37:17 | sean-k-mooney | ya its usign os_name today https://github.com/openstack/nova/blob/master/nova/virt/osinfo.py#L93 | |
| 14:37:31 | sean-k-mooney | oh no os_disto https://github.com/openstack/nova/blob/master/nova/virt/osinfo.py#L136 | |
| 14:37:54 | Uggla | sean-k-mooney, that's fine I answered with "invalid" because based on what you have said above, clearly it is a behavior change so more a BP than a bug. | |
| 14:37:54 | sean-k-mooney | os_name is the vairable name | |
| 14:38:11 | sean-k-mooney | yep that fair | |
| 14:38:28 | sean-k-mooney | i think fi we ant to do the se need a new image proeprty to enabel using this functionlty | |
| 14:38:35 | sean-k-mooney | we coudl perhaps eventually change the defualt of that | |
| 14:39:00 | sean-k-mooney | but as a new feature it woudl have to be opt in i think for a release or two before we consider if it can be the default | |
| 14:39:48 | sean-k-mooney | by the way currently when you use this feature we only use it for 2 things | |
| 14:40:05 | sean-k-mooney | the hw_vif_model and hw_disk_bus defaults | |
| 14:40:42 | sean-k-mooney | if we were to use libosinfo there are many other thing it could express an opion on but we have moved toward usign libvirts defaults instead | |
| 14:40:49 | sean-k-mooney | our our own in code | |
| 14:41:24 | sean-k-mooney | we are not tellign libosinfo about the machine type we are suign for example or the architecure | |
| 14:41:44 | sean-k-mooney | so today it can provide sub optimal or invalide recomendation in some cases | |
| 14:42:20 | sean-k-mooney | the feature was never really updated after it was initally created so its somethign i discuage peopel from using | |
| 14:43:54 | sean-k-mooney | the last change was https://github.com/openstack/nova/commit/6be668e51992df53a4d871bea70bc738a9beacb8 to workaround a breakign change in libosinfo so i just see this as tech debt today | |
| 15:01:15 | bauzas | sean-k-mooney: do you have time for a question about https://review.opendev.org/c/openstack/nova/+/979999 ? | |
| 15:03:22 | bauzas | sean-k-mooney: tl;dr wasn't able to find any difference between the code and the fixtures, so I can't see any leak | |
| 15:14:58 | sean-k-mooney | bauzas: ack im not sure where the change in behvior is either. but i kown we were not ablt to propperly repoduce it in https://review.opendev.org/c/openstack/nova/+/914712 when we tried. we coudl only repoduce it in devstack | |
| 15:15:38 | bauzas | sean-k-mooney: I looked that we were providing the limits in the Selection object | |
| 15:15:47 | bauzas | that's why it works | |
| 15:16:08 | sean-k-mooney | right but i dont thnk we have that on the compute node right | |
| 15:16:34 | sean-k-mooney | only in the schduler so i asuem it was drop in the rpc? | |
| 15:18:01 | sean-k-mooney | bauzas: https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2505 | |
| 15:18:20 | sean-k-mooney | build_and_run_instance accpate the limits object but im not sure if we pass it | |
| 15:18:25 | sean-k-mooney | and what it contains | |
| 15:18:26 | bauzas | we pass the limits | |
| 15:18:30 | bauzas | by it | |
| 15:19:02 | bauzas | of course, if we no longer have alternates, then we call back to the conductor and then we miss the limits | |
| 15:19:22 | bauzas | also, limits are not persisted so when you resize, you don't look at the network metadata | |
| 15:19:39 | sean-k-mooney | well yes because they can change on resize | |
| 15:20:00 | bauzas | so yeah, we should get the network metadata by the claim, but as I said, I can't reproduce the issue | |
| 15:20:01 | sean-k-mooney | they shoudl not be persited they shoudl be calcuatled on each create/resize/rebuild | |
| 15:20:05 | bauzas | correct | |
| 15:22:49 | sean-k-mooney | i can see if i can make some time to try and look into it next week im currently tryitn to wrap up some cybrog stuff for rc2 so i proably cant dig into it indetail today | |
| 15:23:13 | sean-k-mooney | bauzas: are you currently blocked or do you have enfor info to try workign on the fix? | |
| 15:23:39 | bauzas | I'll work on the fix | |
| 15:25:48 | sean-k-mooney | ack my best advice right now is try adding some LOG.debug statement like artom did https://review.opendev.org/c/openstack/nova/+/914712 | |
| 15:25:58 | sean-k-mooney | or even take over that patch | |
| 15:26:29 | sean-k-mooney | and see if you can repoduce in devstack | |
| 15:26:48 | sean-k-mooney | we can hopefully use that info to fix the funtional tests or repoduce in a unit test later | |
| 17:33:13 | opendevreview | ribaudr proposed openstack/nova master: Reproduce bug #2108974: keypairs lost during cross-cell resize https://review.opendev.org/c/openstack/nova/+/981557 | |
| 17:33:13 | opendevreview | ribaudr proposed openstack/nova master: Fix keypairs lost during cross-cell resize https://review.opendev.org/c/openstack/nova/+/981558 | |
| 20:42:22 | opendevreview | Merged openstack/nova master: Reproduce bug #2144660: NUMA cell sorting bug for non-PCI VMs https://review.opendev.org/c/openstack/nova/+/978885 | |
| 20:57:39 | opendevreview | Merged openstack/nova master: Fix NUMA cell sorting for non-PCI VMs with pack strategy https://review.opendev.org/c/openstack/nova/+/978954 | |
| 21:52:24 | opendevreview | Merged openstack/nova master: FUP Add HW_PCI_LIVE_MIGRATABLE trait to PCI resource providers https://review.opendev.org/c/openstack/nova/+/977310 | |
| 21:52:37 | opendevreview | Merged openstack/nova master: Tidy up pci self.flags() calls in SR-IOV functional tests https://review.opendev.org/c/openstack/nova/+/978479 | |
| #openstack-nova - 2026-03-22 | |||
| 00:54:44 | opendevreview | Merged openstack/nova master: Update master for stable/2026.1 https://review.opendev.org/c/openstack/nova/+/980406 | |
| 13:26:10 | opendevreview | sean mooney proposed openstack/nova master: [WIP] POC: NUMA-aware vSwitch enforcement on compute claim https://review.opendev.org/c/openstack/nova/+/981684 | |
| 13:26:16 | sean-k-mooney | bauzas: i filed https://bugs.launchpad.net/nova/+bug/2145135 you were right about the current dependce on the limits https://review.opendev.org/c/openstack/nova/+/979999 is a valid repoducer but only becuase part of the orginal spec was not properly impmented. | |
| #openstack-nova - 2026-03-23 | |||
| 12:51:24 | opendevreview | Balazs Gibizer proposed openstack/nova master: Move py312-threading to py313 https://review.opendev.org/c/openstack/nova/+/980458 | |
| 14:22:20 | nicolairuckel | Do I understand it correctly, that this is done? https://blueprints.launchpad.net/nova/+spec/vtpm-live-migration | |
| 14:22:52 | nicolairuckel | And all patches from here that are merged should belong to the implementation? https://review.opendev.org/q/topic:%22bp/vtpm-live-migration%22 | |
| 14:26:01 | dansmith | yes, and "should" | |
| 14:36:00 | nicolairuckel | thanks :) | |
| 14:55:21 | Uggla | melwitt, gmaan, please can you review again https://review.opendev.org/c/openstack/nova/+/981085 it should not take long. | |
| 15:06:28 | Uggla | Upstream meeting in ~1h. | |
| 15:21:12 | opendevreview | Merged openstack/nova stable/2026.1: Fix Flamingo version in qemu matrix. https://review.opendev.org/c/openstack/nova/+/981085 | |
| 16:00:31 | Uggla | #startmeeting nova | |
| 16:00:31 | opendevmeet | Meeting started Mon Mar 23 16:00:31 2026 UTC and is due to finish in 60 minutes. The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 16:00:31 | opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 16:00:31 | opendevmeet | The meeting name has been set to 'nova' | |
| 16:00:35 | gibi | o/ | |
| 16:00:40 | Uggla | Hello everyone | |
| 16:01:47 | nicolairuckel | o/ | |
| 16:01:47 | fwiesel | o/ | |
| 16:02:30 | lajoskatona | o/ | |
| 16:03:35 | Uggla | Let's start | |
| 16:03:45 | Uggla | #topic Bugs (stuck/critical) | |
| 16:03:51 | Uggla | #info No Critical bug | |
| 16:04:19 | bauzas | o/ | |
| 16:04:24 | Uggla | #topic Gate status | |
| 16:04:25 | elodilles | o/ | |
| 16:04:43 | Uggla | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | |
| 16:04:54 | Uggla | #link https://etherpad.opendev.org/p/nova-ci-failures-minimal | |
| 16:05:01 | Uggla | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status | |
| 16:05:06 | Uggla | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:05:12 | Uggla | #info Please try to provide a meaningful comment when you recheck | |
| 16:05:37 | Uggla | TBH I have not looked at the status pages. Anything wrong with the gate ? | |
| 16:06:46 | sean-k-mooney | o/ | |
| 16:07:27 | Uggla | seems not so moving on | |
| 16:07:46 | Uggla | #topic Release Planning | |
| 16:07:54 | Uggla | #link https://releases.openstack.org/gazpacho/schedule.html | |
| 16:08:05 | Uggla | #info Nova deadlines are set in the above schedule | |