Thursday, 2025-03-20

opendevreviewAdam Kijak proposed openstack/nova stable/2024.1: Fix race condition when attaching a volume and deleting the instance  https://review.opendev.org/c/openstack/nova/+/94506707:48
bauzasdansmith: sean-k-mooney: yeah the reservation id is some older field related to ec2 API, nothing related to blazar09:17
bauzasit was existing *before* climate :) (ie. blazar older name)09:17
bauzasgmann: dansmith: when you're up, as a reminder, there is some work to be done on grenade as we can't merge https://review.opendev.org/c/openstack/nova/+/944018 yet for our non-SLURP support enveloppe10:09
sean-k-mooneybauzas: ack, i use horizon im just rarely logged in as admin so i was like what is this feild i never see10:27
bauzasmore than a decade ago when we incepted climate, we were wondering the interest of that field and whether it could be useful10:29
bauzaseventually, we said meh10:29
bauzasbut afaik, you get the same reservation id for multicreate, that's one way for you to match the relationship (particularly given the request_id isn't public)10:30
bauzasthat has to be confirmed, I'm a bit unsure of that10:31
sean-k-mooneyya apprently its just a way to corralate instance create by multi create (and happens to be set on all instnaces probly because of common code path) im not really sure why that useful10:37
sean-k-mooneyit would be more useful if we recored the orginal request id but ti probably predates that?10:37
sean-k-mooneyat least with the resquest id we could easilly corralate the request to logs if they still existed and it would work across all services10:38
sean-k-mooneybauzas: the resuqest id is set in the header of the request by the user so it is public10:39
sean-k-mooneybauzas: we generate one if its not present using middelware10:39
sean-k-mooneybut you as a normal user are free to set it, you just dont have access to the logs to make use of it. the only api that takes it as an input it the instance action log10:39
sean-k-mooneydansmith: by the way my ci run with the invokeation fo kill took the sys.exit path... so either the mod_wsgi docs are wrong about the constant i need to check or it does not work for some other reason10:44
sean-k-mooneydansmith: on the pluse side the raise_forever version worked as expected and cause the k8s pods to fail the ready check and that got reported back up into the CRs10:44
sean-k-mooneyso im going to rework https://review.opendev.org/c/openstack/nova/+/945028 with a workaorund config flag to opt into that behavior if you have external monitoring that will detect the error10:45
sean-k-mooneybauzas: by the way i think we have our own variant of teh grenade multi node job10:47
sean-k-mooneybauzas: so if we wanted we could overried the base branch temporally until it get changed for everything else10:48
sean-k-mooneywe jsut need to export the wirte varible in the job def10:48
sean-k-mooneyor wait like 2 weeks until it gets fixed in greneade either is fine10:49
opendevreviewMina Shahsavan pour proposed openstack/nova master: Volume Affinity Filter  https://review.opendev.org/c/openstack/nova/+/94503112:17
opendevreviewBalazs Gibizer proposed openstack/nova stable/2025.1: Reproduce bug/2098496  https://review.opendev.org/c/openstack/nova/+/94509512:57
opendevreviewBalazs Gibizer proposed openstack/nova stable/2025.1: Ignore metadata tags in pci/stats _find_pool logic  https://review.opendev.org/c/openstack/nova/+/94509612:57
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.2: Reproduce bug/2098496  https://review.opendev.org/c/openstack/nova/+/94509812:59
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.2: Ignore metadata tags in pci/stats _find_pool logic  https://review.opendev.org/c/openstack/nova/+/94509912:59
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.1: Reproduce bug/2098496  https://review.opendev.org/c/openstack/nova/+/94510012:59
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.1: Ignore metadata tags in pci/stats _find_pool logic  https://review.opendev.org/c/openstack/nova/+/94510112:59
opendevreviewBalazs Gibizer proposed openstack/nova stable/2023.2: Reproduce bug/2098496  https://review.opendev.org/c/openstack/nova/+/94510213:01
opendevreviewBalazs Gibizer proposed openstack/nova stable/2023.2: Ignore metadata tags in pci/stats _find_pool logic  https://review.opendev.org/c/openstack/nova/+/94510313:01
sean-k-mooneyfeck it anyway, of cores i cant use a workaround config flag to decied how to handel invalid config errors13:32
sean-k-mooneys/cores/course/13:32
sean-k-mooneyi wrote some nice help text and everything, oh well i guess i can use some of that for the release note13:33
dansmithsean-k-mooney: cool13:38
opendevreviewsean mooney proposed openstack/nova master: raise_forever on wsgi app init  https://review.opendev.org/c/openstack/nova/+/94502814:03
sean-k-mooneydansmith: ^ i think is in a pretty good state ill kick off one more recheck via the operator repo to to get fresh result with mod_wsgi but it should be good to review14:10
dansmithI've got it open14:10
*** priteau2 is now known as priteau15:01
gmannbauzas: yes, today I got go ahead from release team about all repo are branched now and I will start the QA tooling (including grenade) setup for old/new releases17:21
bauzasgmann: cool excellent17:33
zigosean-k-mooney: Hey there! Do you happen to know how far we've been from having the virtiofs driver in Manila? Is it in Epoxy, or should we wait another release ?!?17:57
opendevreviewsean mooney proposed openstack/nova master: wrap wsgi_app.init_application with latch_error_on_raise  https://review.opendev.org/c/openstack/nova/+/94502817:59
sean-k-mooneyzigo: its in17:59
zigoOh !!! :)17:59
sean-k-mooneyzigo: the osc patches for it missed however17:59
zigosean-k-mooney: Is there anything I should do to support it at the packaging level ?17:59
zigoOr "it just works" (tm) ?17:59
sean-k-mooneyso the osc command to attach/detach the share were not merged on time as they are waiting for the sdk patch for the new nova api to land17:59
sean-k-mooneyzigo: i dont think it changes any deps or requries packaging work beyond making sure you have the right version of openstacksdk ectra18:00
zigosean-k-mooney: At this point, I probably will try to get Epoxy in Debian 13, so if there's a (small) series of patches to add, it's probably worth it !18:00
zigoMaybe I should ask in the -discuss list about this topic?18:01
sean-k-mooneythey are proposed we proablly will see if we can do a release early in 2025.2 to get the client out there18:01
zigoI'd love it if they were backported to Epoxy officially.18:02
sean-k-mooneyhttps://review.opendev.org/c/openstack/python-openstackclient/+/881540 and https://review.opendev.org/c/openstack/openstacksdk/+/880056 are the pending patches18:02
sean-k-mooneythey need a little more work to get over the line hopefully Uggla will have time to work on them again soon18:03
sean-k-mooneyzigo: but sure start a mail thread if you want we know completing hte client side fo the various api we added this cycle is a priority18:04
sean-k-mooneywe have a couple of gaps for spice-direct, manilla-shared, image properties in server show and server groups in server show18:05
sean-k-mooneyall i think have pathces up but we need to work with the clinet fould to get them in shape and landed18:05
mikalzigo: yeah, it would be good to know if Debian 13 had any discussions around dropping SPICE support too. Debian is currently the recommended host OS for hypervisors with spice-direct.19:06

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