Wednesday, 2026-08-05

opendevreviewGoutham Pacha Ravi proposed openstack/nova master: DNM: Add virtiofs share attachment CI jobs  https://review.opendev.org/c/openstack/nova/+/99977203:12
opendevreviewGoutham Pacha Ravi proposed openstack/nova master: DNM: Add virtiofs share attachment CI jobs  https://review.opendev.org/c/openstack/nova/+/99977203:12
opendevreviewTakashi Kajinami proposed openstack/nova master: Stub kernel support check of AMD-SEV in tests  https://review.opendev.org/c/openstack/nova/+/99978004:15
opendevreviewDr. Jens Harbott proposed openstack/nova master: DNM: Test unit tests on kvm  https://review.opendev.org/c/openstack/nova/+/99972904:16
opendevreviewTakashi Kajinami proposed openstack/nova master: DNM: Test unit tests on kvm  https://review.opendev.org/c/openstack/nova/+/99972904:26
opendevreviewGoutham Pacha Ravi proposed openstack/nova master: DNM: Add virtiofs share attachment CI jobs  https://review.opendev.org/c/openstack/nova/+/99977204:55
opendevreviewGoutham Pacha Ravi proposed openstack/nova master: DNM: Add virtiofs share attachment CI jobs  https://review.opendev.org/c/openstack/nova/+/99977204:56
opendevreviewTakashi Kajinami proposed openstack/nova master: Stub kernel support check of AMD-SEV in tests  https://review.opendev.org/c/openstack/nova/+/99978006:18
opendevreviewTakashi Kajinami proposed openstack/nova master: DNM: Test unit tests on kvm  https://review.opendev.org/c/openstack/nova/+/99972906:18
opendevreviewTakashi Kajinami proposed openstack/nova master: Stub kernel support check of AMD-SEV in tests  https://review.opendev.org/c/openstack/nova/+/99978007:26
opendevreviewTakashi Kajinami proposed openstack/nova master: DNM: Test unit tests on kvm  https://review.opendev.org/c/openstack/nova/+/99972907:26
gibigmaan: re threadpool, not yet, I will try to get to it today but there are higher prio things in front of it at the moment07:32
opendevreviewBalazs Gibizer proposed openstack/nova master: DNM: check tempest for instability  https://review.opendev.org/c/openstack/nova/+/99937807:40
bauzasgibi: may I gently ask you for a short +W ? https://review.opendev.org/c/openstack/nova/+/99960707:43
gibibauzas: done. Have you checked if a failing post copy live migration in this case leaves the instance on the source node in ACTIVE state and we leak nothing on the dest node?07:44
bauzasgibi: at least I saw that by the tempest whitebox test, the instance is back to the source07:45
bauzashttps://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/93949807:45
gibiOK, thanks07:46
bauzasbut I'll verify whether the instance is back ACTIVE for sure07:46
opendevreviewKamil Sambor proposed openstack/nova master: libvirt: retry get_guest() on InstanceNotFound during post-copy VIF reattach  https://review.opendev.org/c/openstack/nova/+/99738007:51
mattcreesGood morning! Would anyone be free to give me another review of my bugfix? https://review.opendev.org/c/openstack/nova/+/98266008:07
opendevreviewTakashi Kajinami proposed openstack/nova master: Stub kernel support check of AMD-SEV in tests  https://review.opendev.org/c/openstack/nova/+/99978009:07
opendevreviewTakashi Kajinami proposed openstack/nova master: DNM: Test unit tests on kvm  https://review.opendev.org/c/openstack/nova/+/99972909:07
opendevreviewTakashi Kajinami proposed openstack/nova master: Stub kernel support check of AMD-SEV in tests  https://review.opendev.org/c/openstack/nova/+/99978009:33
opendevreviewTakashi Kajinami proposed openstack/nova master: DNM: Test unit tests on kvm  https://review.opendev.org/c/openstack/nova/+/99972909:33
tkajinamhmm I was able to fix unit tests but am struggling to fix functional tests. I don't know why that patching of update_provider_tree is ignored ...09:34
opendevreviewMerged openstack/nova master: doc: Document postcopy incompatibility with vGPU live migration  https://review.opendev.org/c/openstack/nova/+/99960709:40
opendevreviewMerged openstack/osc-placement master: tox: Fix outdated functional test environments  https://review.opendev.org/c/openstack/osc-placement/+/99882511:06
opendevreviewElod Illes proposed openstack/nova stable/2025.1: [stable-only] Set skip-level grenade as voting  https://review.opendev.org/c/openstack/nova/+/99974211:08
opendevreviewMerged openstack/osc-placement master: [tox] Use constraints for requirements in docs job  https://review.opendev.org/c/openstack/osc-placement/+/99881611:14
opendevreviewMerged openstack/osc-placement master: reno: Update master for unmaintained/2024.1  https://review.opendev.org/c/openstack/osc-placement/+/96549511:16
opendevreviewMerged openstack/osc-placement master: Exclude tests directory from coverage calculation  https://review.opendev.org/c/openstack/osc-placement/+/90666511:17
opendevreviewElod Illes proposed openstack/osc-placement stable/2026.1: [tox] Use constraints for requirements in docs job  https://review.opendev.org/c/openstack/osc-placement/+/99981312:19
opendevreviewElod Illes proposed openstack/osc-placement stable/2025.2: [tox] Use constraints for requirements in docs job  https://review.opendev.org/c/openstack/osc-placement/+/99981412:21
opendevreviewElod Illes proposed openstack/osc-placement stable/2025.1: [tox] Use constraints for requirements in docs job  https://review.opendev.org/c/openstack/osc-placement/+/99981512:23
jangutter[m]Hi folks, we ran into an issue in one of our OpenStack clusters where the autoincrement ID in the nova.instance_system_metadata table ran into the max for the column size https://opendev.org/openstack/nova/src/branch/master/nova/db/main/models.py#L99312:42
jangutter[m]For now, we’re promoting that column to BigInteger, but I was wondering if there’s a process for reclaiming old ID’s and resetting the autoincrement? Our combination of massive amounts of instance properties plus churn in instance launches triggered this, but I was wondering if there’s a periodic maintenance step we’re missing.12:42
sean-k-mooneyjangutter[m]: your not the first12:42
sean-k-mooneyso we didnt do that to avoid the upgrade impact but we have considered doing that in the past12:43
sean-k-mooneyeverntully we will need to do the same upstream12:43
sean-k-mooneywhat we did for our old internal cloud12:43
jangutter[m][sean-k-mooney](https://matrix.to/#/@sean-k-mooney:matrix.org) I was literally calculating how soon folks like CERN or telcos would run into this!12:43
sean-k-mooneywas manually reindex the records in teh table12:43
sean-k-mooneyya so our internal cloud hit this about 2-3 years ago12:44
jangutter[m]We took down our DB and re-imported (since we could take the downtime)12:44
sean-k-mooneymelwitt had the pleasure of helping them fix it12:44
sean-k-mooneyi think we did somethign simialr we shuffled the row ids back to the start of the reange fillign the gaps and then reset the increment point12:45
jangutter[m]But yeah, migrating the primary index is not to be taken lightly.12:45
sean-k-mooneythe way we woudl do that upstream woudl be to add a new column and index then later hava a contract migration to drop the old integer column12:45
sean-k-mooneyso you woudl do the expand schema migration ot add the new colume then upgrade nova then we woudl drop the old primary index column12:46
sean-k-mooneyjangutter[m]: i dont know how shareable or robust the scripting we did internaly was but i could see adding a nova-manage command to do this if it was safe to do so12:47
jangutter[m]You’d still run out of indexes, but hopefully other things would bother you first (like the rise of the Zombie people in 2045)12:48
sean-k-mooneybut ya the instance system metadata table is the first to hit it because there are many entreis per vm12:48
jangutter[m]Thanks for confirming!12:49
sean-k-mooneyim just checking if i have any refence ot the downstream issue its been a while12:50
jangutter[m]Yeah, strangely I didn’t find any launchpad issues12:50
sean-k-mooneywe discused it in the ptg a few years ago but i dont know if we created a bug12:51
sean-k-mooneyhttps://redhat.atlassian.net/browse/OSPRH-421612:52
sean-k-mooneyok so that was orgially imported form bugzill 2 jira instances ago12:53
sean-k-mooneyhttps://bugzilla.redhat.com/show_bug.cgi?id=216424712:54
sean-k-mooneyhttps://etherpad.opendev.org/p/nova-bobcat-ptg#L43112:56
sean-k-mooneyjangutter[m]: so it looks like we agreed new PK will be big ints and to ask operators what there prefence woudl be for upgrades and if they woudl prefer reindexing12:57
sean-k-mooneyjangutter[m]: so if you have a prefence let us know :)12:57
jangutter[m]We’re planning our Epoxy migrations now (and looks like most of them will be offline), so we might not be a good example.12:58
sean-k-mooneyi think most operator would just like sometihng that works :)13:00
sean-k-mooneywhere they dont have to think to hard about it 13:00
sean-k-mooneyultimatly we need to change all our primary keys to bigints eventually13:01
jangutter[m]Yeah, and the fixes are different whether you’re having an outage or not, of course.13:01
jangutter[m]At least this isn’t as bad as the Y2038 problem. If you’ve been running a cluster long enough for this to affect you, chances are you know a bit about the internals of OpenStack.13:04
sean-k-mooneyya the internal culsterwas running since like osp7 and upgraded along the way so 6-8 years of primarlly a dev/ci workload with many many short lived vms13:08
sean-k-mooneyanyeay if melwitt rememebr andy more or still has the script somewhere perhaps she can comment on how feasible it woudl be to have a nova-manage command to "heal" it when needed but that a workaround not a real fix13:09
sean-k-mooneyjangutter[m]: have ye fixed this for your current cloud13:10
sean-k-mooneyyou mentioned you just promoted the column right13:10
sean-k-mooneyi dont know that we ever join on that primary key so for that specici table droping that column might also be an option13:11
sean-k-mooneythe unique constraitn is the instance id or uuid and the metadata key i think and we alwasy join on the instance id13:12
sean-k-mooneyya its on the instanfce uuid we actuly do not have a proper uniwue constrating on that table...13:14
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/db/main/models.py#L987-L100413:14
sean-k-mooneyi wonder if that would be the better fix in this case add a uniqeconstrat on instnace_uuid + key colum and drop id entirly13:15
sean-k-mooneythe instance uuid is effectivly the real "primary key" based on our actul usage which is why its already got its own index13:16
sean-k-mooneyah this has the soft delete mixin13:21
sean-k-mooneyso ya we cant actully change the colume name like that or delete the id colume and use a compistie primay key13:22
sean-k-mooneyso the only options are reindex or promot to BigInt13:22
sean-k-mooneyjangutter[m]: you will need to promote the deleted colume to the same type because of softdelete fyi13:25
sean-k-mooneyotherwase you wont be abel to delete if the value exceeds int max13:25
jangutter[m]oh yes, we saw you need to do it in pairs.13:38
jangutter[m]We managed to speedrun it in 2-3 years with a combination of ~50 properties per instance and a tight create/delete loop.13:40
sean-k-mooneyyep that will do it13:41
sean-k-mooneywe did the reindex by sufflleing all the rows down to avoid needing to mess with the schema13:41
sean-k-mooneyas noted we dont actully use the id values 13:43
sean-k-mooneyso the hack is basiclly13:43
sean-k-mooneySET @num := 0;13:43
sean-k-mooneyUPDATE instance_system_metadata SET id = @num := (@num+1);13:43
sean-k-mooneyALTER TABLE instance_system_metadata AUTO_INCREMENT =1;13:43
sean-k-mooneyi say basiclly becase if the deleted colum is non 0 you have to set delete=id as well13:44
sean-k-mooneyto keep the soft delete state correct13:44
sean-k-mooneyim sure you can express that as a single query but i think we didi it in python13:45
jangutter[m]That would be a handy hack to have in nova-manage.13:45
jangutter[m]but you have to be sure the id isn’t referenced elsewhere.13:46
sean-k-mooneyya and there are other tabels that we can or coudl do the same for13:51
sean-k-mooneybasiclly a `nova-manage db compact`  command13:52
sean-k-mooneyi think to do that properly you need to do it with a full table lock and batch it to now block operations13:52
sean-k-mooneyor do it offline but but if you do it 1000 rows at a time ectra you could do it online13:53
MaxLamprecht[m]Hey folks, I wanted to ask regarding some attachment fixes I proposed a while ago(we merged 1 out of 3 fixes a while ago). https://review.opendev.org/c/openstack/nova/+/974832 and https://review.opendev.org/c/openstack/nova/+/972045 are still open with valid reproducers/regression tests. Is there something I can do to get more attention on this topic?14:13
opendevreviewminwoo seo proposed openstack/nova master: libvirt: Add volume migration bandwidth option to nova.conf  https://review.opendev.org/c/openstack/nova/+/99984114:24
tkajinamclif, hj could you try https://review.opendev.org/c/openstack/nova/+/999780 when you have time ?14:39
tkajinamthere are a few functional tests still failing but CI shows at least unit tests are passing14:39
cliftkajinam: passes for me:   py3: OK (113.29=setup[2.17]+cmd[99.77,7.69,3.66] seconds)14:42
tkajinamclif, that's good. could you also run functional tests there, too ?14:42
clifsure14:43
tkajinamI expect two reshape tests may fail14:43
cliftkajinam: I get two failures in functional: nova.tests.functional.libvirt.test_reshape.SevResphapeTests.test_create_servers_with_amd_sev and nova.tests.functional.libvirt.test_reshape.SevResphapeTests.test_create_servers_with_amd_sev_mixed14:49
tkajinamyeah14:49
tkajinamit's wired that update_available_resource is called there though it's mocked out14:49
opendevreviewClif Houck proposed openstack/nova master: perf(ironic): eliminate O(N²) ProviderTree deepcopy at startup (B6)  https://review.opendev.org/c/openstack/nova/+/98067615:03
melwittMaxLamprecht[m]: channel ping is good, both have green CI, i will try to look soon15:06
UgglaReminder upstream bug triage in ~20mn.15:08
lajoskatonasean-k-mooney: Hi, there is a patch ( https://review.opendev.org/c/openstack/nova/+/982085) for  https://bugs.launchpad.net/nova/+bug/2051685 (After repeat of incomplete migration nova applies wrong (status=error) migration context in update_available_resource periodic job)15:12
lajoskatonasean-k-mooney: and a reproducer functional test under the commit. As I remember we had a short chat about it, if you have time can you please check it? Bence / rubasov started to work on it but He was moved to another project so I am kind of responsible for it now :)15:12
opendevreviewClif Houck proposed openstack/nova master: Parallelize per-node resource updates  https://review.opendev.org/c/openstack/nova/+/98067915:15
opendevreviewminwoo seo proposed openstack/nova master: libvirt: Add volume migration bandwidth option to nova.conf  https://review.opendev.org/c/openstack/nova/+/99984115:28
UgglaLink reminder: meet.google.com/zjr-rxus-hzj  (upstream triage)15:33
opendevreviewTakashi Kajinami proposed openstack/nova master: Stub kernel support check of AMD-SEV in tests  https://review.opendev.org/c/openstack/nova/+/99978015:40
opendevreviewTakashi Kajinami proposed openstack/nova master: DNM: Test unit tests on kvm  https://review.opendev.org/c/openstack/nova/+/99972915:40
*** Unknown123 is now known as Mike--16:28
opendevreviewBalazs Gibizer proposed openstack/nova master: Add reproducer for bug/2162912  https://review.opendev.org/c/openstack/nova/+/99987716:37
tkajinamsean-k-mooney dansmith https://review.opendev.org/c/openstack/nova/+/999780 fixes the unit/func tests in amd machine17:06
tkajinamverified in ci by https://review.opendev.org/c/openstack/nova/+/99972917:07
tkajinamjust fyi17:07
tkajinam(but appreciate your reviews, if you have time17:07
sean-k-mooneyi looked breifly this morningin the only thing i was debtin is if you shoudl pass in the var when constucting the fixture as you are doign or just have the class var defiend in the fixture and use it direcly 17:08
sean-k-mooneythat would just avoid proxing it here https://review.opendev.org/c/openstack/nova/+/999780/6/nova/tests/functional/libvirt/base.py17:09
sean-k-mooneybut i see why you did it this way17:19
sean-k-mooney+2 form me17:22
sean-k-mooneygmaan: https://review.opendev.org/c/openstack/nova/+/980679 this is the patch that i mentioned today related to usign an executor to Parallelize per-node resource updates17:46
sean-k-mooneyits workign the exact same as the _sync_power_executor https://review.opendev.org/c/openstack/nova/+/980679/5/nova/compute/manager.py#66917:46
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline momentarily at 20:00 UTC (an hour from now) while we restart for a patch upgrade, but should return within a few minutes.19:03
gmaansean-k-mooney: ack19:06
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org will not be restarted at 20:00 UTC after all, due to unanticipated image build regressions, and will be rescheduled to a later time/date.19:14
opendevreviewBryan Fraschetti proposed openstack/nova master: Feat: Add Command for Forceful BDM Deletion  https://review.opendev.org/c/openstack/nova/+/98571719:20
opendevreviewBryan Fraschetti proposed openstack/nova master: add task state for attach volume and detach volume  https://review.opendev.org/c/openstack/nova/+/98571819:20
opendevreviewBryan Fraschetti proposed openstack/nova master: Reject to attach and detach volume while task_state is not None  https://review.opendev.org/c/openstack/nova/+/75891819:20
opendevreviewBryan Fraschetti proposed openstack/nova master: Reject Volume Attachment if task_state not Attaching  https://review.opendev.org/c/openstack/nova/+/98571919:20
opendevreviewMerged openstack/placement stable/2026.1: Reproduce bug 2160721  https://review.opendev.org/c/openstack/placement/+/99887320:07
opendevreviewMerged openstack/placement stable/2026.1: Check overall capacity before generating candidates  https://review.opendev.org/c/openstack/placement/+/99887420:07

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