Wednesday, 2026-10-21

opendevreviewYushoYamaguchi proposed openstack/nova-specs master: Allow disabling host checksum offload for vhost-user  https://review.opendev.org/c/openstack/nova-specs/+/101106702:54
opendevreviewAbhishek Kekane proposed openstack/nova master: Add Glance preferred stores support  https://review.opendev.org/c/openstack/nova/+/101147003:37
tkajinamhmm it seems https://review.opendev.org/c/openstack/nova/+/1006786 broke some tests (at least a few founds in cinder-tempest-plugin) repeating volume attachments ...04:50
tkajinamit actually breaks it correctly but I guess we have to update some test scenarios to make sure that they wait until attachment actually completes...04:50
tkajinamcontext: https://zuul.opendev.org/t/openstack/build/7557579c282b406e95138b928e8e91e704:50
opendevreviewKamil Sambor proposed openstack/nova master: deprecate: concurrency_backend config option  https://review.opendev.org/c/openstack/nova/+/101145007:16
opendevreviewKamil Sambor proposed openstack/nova master: Default native threading for CLI entry points  https://review.opendev.org/c/openstack/nova/+/101160607:16
opendevreviewJuan Larriba proposed openstack/nova master: Add OpenTelemetry tracing middleware for Nova  https://review.opendev.org/c/openstack/nova/+/98287107:44
opendevreviewdalekseev proposed openstack/nova master: Restrict machine type check to QEMU instances  https://review.opendev.org/c/openstack/nova/+/99113711:25
gibitkajinam: good catch. could you please file a bug. I agree, based on the logs, that the test is not waiting for the attachment to finish12:19
tkajinamgibi, will do12:46
gibithanks12:51
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/+/100095613:23
tkajinamreported https://bugs.launchpad.net/nova/+bug/217162413:26
sean-k-mooneyattching multiple volume sconcurently should be porhibitied as we can only have one task in flight at once13:27
tkajinambauzas0 gibi , I guess ^^^ is the expected behavior after we merged 1006786 and we should drop that test case because such concurrent volume attachments to a single server should be avoided, but it'd be nice if you could double check my thought13:27
sean-k-mooneyprevisoulsy it woucl have been serialised at the compute13:27
tkajinamyeah that's what I thought13:27
sean-k-mooneywe have a chice i guess we can do it at the compute serially using the instnace lock13:28
sean-k-mooneyor we can block it at the api based on task_Sate!=none13:28
sean-k-mooneyalthough that can race13:28
sean-k-mooneyif your talking to 2 apis at the same time so we always need the instnace lock on teh compute regardless13:29
sean-k-mooneythe instance lock on the compute agent is also one of the things that guards agaisn starting a cinder volume migrate or retype durign say an instance live migrate13:30
tkajinamI personally prefer api level lock and reject concurrent actions explicitly so that revert action can be simplified13:30
sean-k-mooneythe task state shoudl also help but its the final backstop to prevent 2 operations form trying to muteate the domain at the same time13:31
tkajinamyeah13:31
sean-k-mooneytkajinam: same but that does rely on use updating the task state before doing the rpc to the compute or ealy in the conductor flow13:31
tkajinam1006786 added task state update in conductor layer so that implements what you said iiuc13:33
sean-k-mooneybasicly if task state is the primary guard then the api has to update it before doing an rpc to the conducotr or comptue for all instnace actions13:33
tkajinamit's not lock at api layer(which I said) but conductor layer13:33
sean-k-mooneytkajinam: the conductor is kind fo too late but its better then the compute13:33
tkajinamyeah I understand13:34
sean-k-mooneythe action are async and diffent conductors could start processing it howpever wehn we do save we pass the expefcteed state13:34
sean-k-mooneyso one of the 2 conductor shoudl get a db error and fail teh second attach13:35
sean-k-mooneyi think that is fine. we do not provide any ordering guarentey for concurnet api calls anyway13:35
sean-k-mooneyim bit surpprosed that no functional regression test was created for this bug however13:37
sean-k-mooneythis is they type of bug where we normally required those before proceeding with the fix13:37
sean-k-mooneybauzas0: was there a reason you didnt create a functional regression test  first to demonstrate the race?13:38
tkajinamI've made the job non-voting in the mean time but also proposed 1011657 to stop testing concurrent attachments. just fyi...13:45
sean-k-mooneyack13:51
sean-k-mooneytkajinam: what job was failing?13:52
sean-k-mooneyand is that test in core tempest or a plugin?13:52
tkajinamsean-k-mooney,  cinder-tempest-plugin-lvm-concurrency-tests job13:52
sean-k-mooneyah ok13:52
tkajinamthe failing test case is in cinder-tempest-plugin13:52
sean-k-mooneyi was just wonderign why id was not failing on our gate13:52
tkajinamyeah13:53
tkajinamthe plugin has a few test cases testing concurrent operations (such as concurrent volume creations, concurrent volume backups) and concurrent volume attachments is one of these13:54
tkajinamthough I feel like these tests can reside in core tempest13:54
tkajinamhm interestingly that job only runs in cinder-tempest-plugin. idk why13:55
opendevreviewMichael Sherman proposed openstack/nova master: ironic: Restore retries on 409 and 503 from Ironic  https://review.opendev.org/c/openstack/nova/+/101168315:54
*** raineszm0 is now known as raineszm16:55
opendevreviewMerged openstack/nova master: Enable G (flake8-logging-format) rules  https://review.opendev.org/c/openstack/nova/+/99855718:34

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