Thursday, 2026-09-17

gibi_ashigupt: I will try to get to it but at the moment it is somewhere in the middle of my todo lit07:03
gibi_lis07:03
gibi_list07:03
*** bauzas7 is now known as bauzas07:54
bauzashey folks, back08:09
bauzasgibi_: I mentioned https://review.opendev.org/c/openstack/nova/+/1005727 but this requires a bit of cleanup on my side per the last comments, fwiw08:16
gibi_ack08:25
gibi_I push what I have and then start looking at yours08:26
opendevreviewBalazs Gibizer proposed openstack/nova master: Fix PCI allocation leak on failed cold migration  https://review.opendev.org/c/openstack/nova/+/100600309:00
gibi_bauzas: that is mine ^^ it reuses an existing RPC call originally used for live migration during cold migration to clean up the leaked MoveClaim09:01
bauzasack09:01
gibi_bauzas: left questions in the fix09:13
bauzasty, still trying to untangle all the potential issues09:13
gibi_ack09:14
*** gibi_ is now known as gibi09:14
bauzasas a reminder, the best solution is something persisted09:14
bauzasbut still trying to find a short-term fix for being backportable shortly09:14
gibiahh and I realized that I asked the same question as Dan 09:15
gibiabout how the two parallel request can overlap09:15
bauzasnp09:15
gibiOK moved my comment to the proper place09:26
opendevreviewBalazs Gibizer proposed openstack/nova master: Reproduce bug 2166786  https://review.opendev.org/c/openstack/nova/+/100465809:27
opendevreviewBalazs Gibizer proposed openstack/nova master: Fix PCI allocation leak on failed cold migration  https://review.opendev.org/c/openstack/nova/+/100600309:27
opendevreviewSylvain Bauza proposed openstack/nova master: Guard against deleting a concurrent request's BDM on timeout  https://review.opendev.org/c/openstack/nova/+/100572710:38
opendevreviewSylvain Bauza proposed openstack/nova master: Reject stale reserve_block_device_name RPC on compute  https://review.opendev.org/c/openstack/nova/+/100601110:38
opendevreviewMerged openstack/placement master: pre-commit: Add codespell  https://review.opendev.org/c/openstack/placement/+/93180611:36
gibigmaan: does this clear_events_for_instance needs to run for failed resizes as well https://github.com/openstack/nova/blob/94de0576ca02e0668233bedfbe7e18b87316c708/nova/compute/manager.py#L6418 ? E.g. if driver.migrate_disk_and_power_off raises do we leak a pending resize task?13:11
bauzasgibi: gmaan: I barely paid attention to the gate issues with threading, but I just saw that one https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_c5e/openstack/c5e5e75ba3ba4ea1bbc056c4f9299476/testr_results.html13:52
bauzascontext : https://review.opendev.org/c/openstack/nova/+/100572713:53
gibihttps://bugs.launchpad.net/nova/+bug/216514913:55
gibihttps://review.opendev.org/c/openstack/nova/+/100358613:56
opendevreviewribaudr proposed openstack/nova master: Fix swap disk creation skipped on NFS during cold migration  https://review.opendev.org/c/openstack/nova/+/100603613:56
gibibauzas: that is also one of the todos I have13:56
bauzasack ok13:56
bauzasI didn't wanted to blindly recheck13:56
gibiwe have open bug and a local fix that does not work on the gate :)13:56
bauzasgibi: great questions by the way on my second patch for preveting BDM creation after RPC timeout14:00
bauzasI wasn't having that level of expertise, you're pushing me into looking at all the oslo.service details :)14:00
gibiyeah my feeling is that we are getting deeper and deeper into a rabbithole14:00
gibibut I haven't had the brain power to offer a real backportable alternative14:01
bauzasfwiw, I care about the first patch in the series, I just offered help for the other patch14:02
bauzasif we don't find a short-term solution for the BDMs being created without calling Cinder, I'm all good14:03
bauzasI just want nova to not delete the wrong BDM (the other case) :-)14:03
gibiOK. we can refocus on the first14:03
gibiI understand your priorities ;)14:03
gibibtw mine is also more complicated than what I pushed. we might want to fixes on that prevent the problem to reapper(that I pushed) and a fix in the periodic to clear the old leaks14:04
gibi*two fixes one that14:04
gibiso I'm poking at the periodic14:05
gibiwhile fighiting a race condition in the original reproduce as we revert stuff in an untestable order14:05
gibiaaand I will drop for a wile in 25mins so running out of time too14:06
bauzasyeah I need some brain cycles now to look at your patch14:06
gibiif you look just focus on the RPC implications, the rest might change14:09
bauzasI need to load a bit of context, that's it14:09
eduardomorais[m]Could someone review this PR and give me some tips? I'm new to contributing, thanks in advance! https://review.opendev.org/c/openstack/nova/+/100588115:48
dansmitheduardomorais[m]: reviewing other people's submissions is a good way to get familiar with the codebase _and_ get yourself karma you can use for other purposes. i.e. find some (legitimate) thing to -1 :)17:18
gmaangibi: yes, resize has the sane issue of task leak in source resize_instance error in between. dest call resize_instance  on source as 'RPC cast' so dest does not get to know if source failed as source does not call dest. As this is prep_resize time the new VM is not yet created on dest so we are good on dest host but task end is not done.17:21
gmaanrevert_resize has the same which not jsut leak task but make VM.host in unrecoverable state. i reported that bug https://bugs.launchpad.net/nova/+bug/2162090 17:21
gmaanI am going to handle these error cases between source and dest as a genric way in part-3.17:23
gmaangibi: if you want I can make previously listed bug as more generic for all migration tasks instead of just live migration task leak at dest. this one https://review.opendev.org/c/openstack/nova/+/1003386/5/releasenotes/notes/nova-graceful-shutdown-task-tracking-13485c8346512ae4.yaml#2317:24
dansmithgmaan: do you have an easy way to disable waiting for graceful shutdown in functional workers? the thing I'm working on seems like it's getting stuck a *lot* and I suspect maybe it's because of graceful shutdown17:27
dansmithmaybe set the wait conf knob to zero by default as a test?17:27
gmaandansmith: we have config knob already set to 0 in configfixture so it should not stuck https://github.com/openstack/nova/blob/master/nova/tests/fixtures/conf.py#L6517:29
dansmithokay but I see lots of messages about it waiting17:29
dansmithlike he thread pool nova.tests.functional.test_servers.ServerMovingTestsWithNestedResourceRequests.test_resize_revert.default is shutting down17:30
dansmithis that just it noting that it's shutting down but not waiting? (I haven't looked to verify)17:30
dansmithit always seems to come after a long pause so I figured those were the ones that eventually did shut down after waiting17:30
gmaanoh, are you seeing hang or just logs. because we have noisy logs of thread pool and I am fixing those for tests  https://review.opendev.org/c/openstack/nova/+/100416017:32
gmaanactual shutdown should not take time as we do not wait for in-progress tasks except in some graceful shutdown tests17:33
dansmithI'm seeing hangs, trying to determine why they're hanging and suspecting graceful shutdown (not my glorious code of course!)17:34
dansmithokay17:34
gmaanhumm, can you check what is manager_shutdown_time value there (by printing ro so). note: graceful_shutdown_timeout is kept default which is 180 sec i hope nothing stuck after manager return immidiatly 17:36
gmaandansmith: one thing can take time is thead pool logs taking time, if anything still running in executors the it will wait17:37
dansmithyeah I'm waiting well past 180s to determine they're stuck, but I was thinking maybe there was some deadlock we're hitting that made the timeout not relevant.. I haven't figured out which test is the problem yet because all the candidates seem to run fine when run alone17:38
dansmithhence me suspecting some interaction17:38
gmaani see. i remember oslo.service does not timeout the shutdown based on graceful_shutdown_timeout as there is no releah SIGTERM handler called on test process between tests17:40
gmaanso we basically retun from manager quickly with 0 sec wait but if something still running in exevcutor and hang then it will hang the shutdown also17:41
gmaanwe does not stop without wait as we want to cathc the bad tests (not your  glorious code of course :)) who leak the things - https://github.com/openstack/nova/blob/master/nova/tests/fixtures/nova.py#L135317:42
gmaanwe fixed a few tests which were hanging and not always but when they face some race so there might be some more but not seen yet in CI17:44
dansmithreset_all_executors() will kill and continue not hang?17:53
gmaanno, it stop executor with wait=True so anything in executro queue will be finished17:53
dansmithbut with timeout or no?17:54
dansmith(heh I see the comment right above, sorry)17:54
gmaanno timeout, because oslo.service SIGTERM handler does not timeout 17:54
gmaanI try to kill them during cleanup and not wait but then liked the gibi idea to wait and let test hang to see why test leaving the things in-progress17:55
gmaanwhich exact tests hang or is it many tests take times17:57
opendevreviewGhanshyam Maan proposed openstack/nova master: Update graceful shutdown known issue to list resize case also  https://review.opendev.org/c/openstack/nova/+/100609518:28
gmaangibi: I updated the existing bug description to cover the resize case - https://bugs.launchpad.net/nova/+bug/216600918:37
gmaangibi: dansmith ^^ and updating the 'known issue' in releae notes18:37
opendevreviewEduardo Henrique Lima de Morais proposed openstack/nova master: Enforce nullable=False on instance_uuid  https://review.opendev.org/c/openstack/nova/+/100588122:01
eduardomorais[m]dansmithSorry for the late reply. I'll take a look at some other PRs to get a better understanding of how things work. Thanks for the help and the tips!22:11
JayFeduardomorais[m]: it's worth noting the PTG (Project Teams Gathering) planning session is happening soon (ptg.opendev.org) -- and that would  be a good place in many projects (I assume this is true for Nova as well) to find something to volunteer to work on22:13
JayFeduardomorais[m]: IDK if you are just looking to drive by contribute or what, but if you want a longer engagement, attending PTG sessions of those projects is a GREAT way to get attention22:13
eduardomorais[m]JayFI'd like to start contributing a bit more to OpenStack services. I currently work as an OpenStack operator, and I'd love to learn more about the codebase and help improve it. I'll definitely keep an eye out for the PTG, thanks for the tip!22:18

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