Earlier  
Posted Nick Remark
#openstack-nova - 2026-10-20
17:23:28 gmaan oh, you are doing that in next change, nevermind +w the base one https://review.opendev.org/c/openstack/nova/+/1011513
17:23:54 sean-k-mooney we have duplicates now https://review.opendev.org/c/openstack/nova/+/1011450
17:24:08 sean-k-mooney and https://review.opendev.org/c/openstack/nova/+/1011513
17:25:08 sean-k-mooney to me changing the default bahvior and deprection the config option are unrelated
17:25:19 sean-k-mooney we are chaing the meaing of auto
17:25:26 sean-k-mooney not the default of the config option
17:25:46 sean-k-mooney but as long as we abandon one fo the deprecation patches its fine
17:28:46 gmaan 1011513 is more than just deprecating the config but also changing default for CLI
17:28:59 gmaan anyways i commented there in gerrit
17:29:24 gmaan title of 1011513 and 1011450 are same but they are not duplicate
18:16:01 abhishek_ sean-k-mooney, dansmith: Circling back to rbd ec snapshot topic from PTG, I have tested locally with changes made to devstack-plugin-ceph https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/1011533
18:16:48 abhishek_ the snapshot now gets stored in data (EC) pool and metadata stored in metadata pool, so we don't need any changes explicitly done in nova to expose data pool
18:25:42 sean-k-mooney abhishek_: i think that woudl also be true for maniala by the way
18:26:08 sean-k-mooney i saw there was a dicsion about addign some extra spec for the data pool
18:26:24 abhishek_ right
18:28:06 sean-k-mooney i have never actuly use manilla with ceph but as i noted on the ptg i used to deploy kolla ansibel with all my storage on ec pools in ceph a decade ago
18:28:14 sean-k-mooney so im glad that didnt break along the way
18:29:09 gouthamr nope, not going to break if you don't set an optional flag.. this is an opt-in feature..
18:29:14 abhishek_ yeah, thanks for the pointers
18:29:36 sean-k-mooney gouthamr: what i was sayign is you probely dont need to add the feature at all
18:30:16 gouthamr sean-k-mooney: yes, you don't - today you can do it transparently to manila.. but, its not operator-friendly.. i.e., they may want to direct provisioning to an EC pool
18:30:58 sean-k-mooney gouthamr: well for a stroage project have ing more advanced policy over this might make sense
18:31:28 sean-k-mooney gouthamr: just noting that the ceph native cofnigution has been supproted in galnce, nova and cidner for a very long time
18:32:00 sean-k-mooney but as i also noted in the etherpad i dont knwo that the service projects have ever docudmented how to do it
18:32:16 sean-k-mooney but the installer and ceph comunity have in the past
18:32:30 sean-k-mooney so its one of those thing that if you dont knwo to ask you wont find out about
18:55:15 opendevreview Abhishek Kekane proposed openstack/nova master: Add Glance preferred stores support https://review.opendev.org/c/openstack/nova/+/1011470
18:56:58 sean-k-mooney abhishek_: for ^ it would be nice if you enabeld that in the multi store job we have if it does not conflict with what that is already testing
18:57:10 sean-k-mooney or if we coudl enabel it in one of the other jobs if it does
18:58:21 abhishek_ ack, I will check and act accordingly (might need to add specific tempest test as well for this in that case)
19:00:12 sean-k-mooney if the current multi store config would configlict i woudl proably enabel this in the nova-alt-config job instead
19:00:23 sean-k-mooney i dont think that is currently testing any special storage config
19:00:29 sean-k-mooney so its less likely to conflict
19:01:43 sean-k-mooney that job existis to test non default configuration of nova withou any suggestion that it will become the new default unlike nova-next.
19:06:32 abhishek_ ack
19:50:15 opendevreview Abhishek Kekane proposed openstack/nova master: Add Glance preferred stores support https://review.opendev.org/c/openstack/nova/+/1011470
19:53:57 opendevreview Merged openstack/nova master: Default native threading for console proxies https://review.opendev.org/c/openstack/nova/+/1009027
23:23:02 opendevreview Dan Smith proposed openstack/nova master: Add old_cell_id to InstanceMapping DB model https://review.opendev.org/c/openstack/nova/+/1008834
23:23:03 opendevreview Dan Smith proposed openstack/nova master: InstanceMapping object changes for old_cell_id https://review.opendev.org/c/openstack/nova/+/1008835
23:23:03 opendevreview Dan Smith proposed openstack/nova master: Make external_events send to source and destination https://review.opendev.org/c/openstack/nova/+/1008836
23:23:04 opendevreview Dan Smith proposed openstack/nova master: Instance lookup support for mid-cell-migration https://review.opendev.org/c/openstack/nova/+/1008837
23:23:04 opendevreview Dan Smith proposed openstack/nova master: Initial conductor plumbing for conductor-orchestrated live migration https://review.opendev.org/c/openstack/nova/+/1008838
23:23:05 opendevreview Dan Smith proposed openstack/nova master: REST API changes for conductor-orchestrated live migration https://review.opendev.org/c/openstack/nova/+/1008839
23:23:05 opendevreview Dan Smith proposed openstack/nova master: Compute RPC refactors for re-use later https://review.opendev.org/c/openstack/nova/+/1008840
23:23:06 opendevreview Dan Smith proposed openstack/nova master: Compute RPC methods for live migration v2 https://review.opendev.org/c/openstack/nova/+/1008841
23:23:06 opendevreview Dan Smith proposed openstack/nova master: Add conductor-orchestrated live migration https://review.opendev.org/c/openstack/nova/+/1008842
23:23:08 opendevreview Dan Smith proposed openstack/nova master: Functional tests for cross-cell live migrate https://review.opendev.org/c/openstack/nova/+/1008843
23:23:08 opendevreview Dan Smith proposed openstack/nova master: Doc changes for cross-cell live migrate https://review.opendev.org/c/openstack/nova/+/1008844
23:23:10 opendevreview Dan Smith proposed openstack/nova master: WIP: Extra instance check for migration_context https://review.opendev.org/c/openstack/nova/+/1008845
#openstack-nova - 2026-10-21
02:54:15 opendevreview YushoYamaguchi proposed openstack/nova-specs master: Allow disabling host checksum offload for vhost-user https://review.opendev.org/c/openstack/nova-specs/+/1011067
03:37:12 opendevreview Abhishek Kekane proposed openstack/nova master: Add Glance preferred stores support https://review.opendev.org/c/openstack/nova/+/1011470
04:50:04 tkajinam hmm 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:32 tkajinam it 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:56 tkajinam context: https://zuul.opendev.org/t/openstack/build/7557579c282b406e95138b928e8e91e7
07:16:43 opendevreview Kamil Sambor proposed openstack/nova master: deprecate: concurrency_backend config option https://review.opendev.org/c/openstack/nova/+/1011450
07:16:44 opendevreview Kamil Sambor proposed openstack/nova master: Default native threading for CLI entry points https://review.opendev.org/c/openstack/nova/+/1011606
07:44:46 opendevreview Juan Larriba proposed openstack/nova master: Add OpenTelemetry tracing middleware for Nova https://review.opendev.org/c/openstack/nova/+/982871
11:25:33 opendevreview dalekseev proposed openstack/nova master: Restrict machine type check to QEMU instances https://review.opendev.org/c/openstack/nova/+/991137
12:19:20 gibi tkajinam: good catch. could you please file a bug. I agree, based on the logs, that the test is not waiting for the attachment to finish
12:46:41 tkajinam gibi, will do
12:51:18 gibi thanks
13:23:09 opendevreview Kamil Sambor proposed openstack/nova master: Fix pickling error that forces oslo.service to fall back to fork https://review.opendev.org/c/openstack/nova/+/1000956
13:26:06 tkajinam reported https://bugs.launchpad.net/nova/+bug/2171624
13:27:16 sean-k-mooney attching multiple volume sconcurently should be porhibitied as we can only have one task in flight at once
13:27:24 tkajinam bauzas0 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 thought
13:27:29 sean-k-mooney previsoulsy it woucl have been serialised at the compute
13:27:46 tkajinam yeah that's what I thought
13:28:22 sean-k-mooney we have a chice i guess we can do it at the compute serially using the instnace lock
13:28:37 sean-k-mooney or we can block it at the api based on task_Sate!=none
13:28:42 sean-k-mooney although that can race
13:29:01 sean-k-mooney if your talking to 2 apis at the same time so we always need the instnace lock on teh compute regardless
13:30:31 sean-k-mooney the 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 migrate
13:30:58 tkajinam I personally prefer api level lock and reject concurrent actions explicitly so that revert action can be simplified
13:31:01 sean-k-mooney the task state shoudl also help but its the final backstop to prevent 2 operations form trying to muteate the domain at the same time
13:31:12 tkajinam yeah
13:31:40 sean-k-mooney tkajinam: same but that does rely on use updating the task state before doing the rpc to the compute or ealy in the conductor flow
13:33:30 tkajinam 1006786 added task state update in conductor layer so that implements what you said iiuc
13:33:33 sean-k-mooney basicly 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 actions
13:33:45 tkajinam it's not lock at api layer(which I said) but conductor layer
13:33:53 sean-k-mooney tkajinam: the conductor is kind fo too late but its better then the compute
13:34:08 tkajinam yeah I understand
13:34:48 sean-k-mooney the action are async and diffent conductors could start processing it howpever wehn we do save we pass the expefcteed state
13:35:03 sean-k-mooney so one of the 2 conductor shoudl get a db error and fail teh second attach
13:35:55 sean-k-mooney i think that is fine. we do not provide any ordering guarentey for concurnet api calls anyway
13:37:02 sean-k-mooney im bit surpprosed that no functional regression test was created for this bug however
13:37:33 sean-k-mooney this is they type of bug where we normally required those before proceeding with the fix
13:38:59 sean-k-mooney bauzas0: was there a reason you didnt create a functional regression test first to demonstrate the race?
13:45:55 tkajinam I've made the job non-voting in the mean time but also proposed 1011657 to stop testing concurrent attachments. just fyi...
13:51:55 sean-k-mooney ack
13:52:12 sean-k-mooney tkajinam: what job was failing?
13:52:36 sean-k-mooney and is that test in core tempest or a plugin?
13:52:38 tkajinam sean-k-mooney, cinder-tempest-plugin-lvm-concurrency-tests job
13:52:43 sean-k-mooney ah ok
13:52:51 tkajinam the failing test case is in cinder-tempest-plugin
13:52:58 sean-k-mooney i was just wonderign why id was not failing on our gate
13:53:32 tkajinam yeah
13:54:04 tkajinam the plugin has a few test cases testing concurrent operations (such as concurrent volume creations, concurrent volume backups) and concurrent volume attachments is one of these
13:54:30 tkajinam though I feel like these tests can reside in core tempest
13:55:17 tkajinam hm interestingly that job only runs in cinder-tempest-plugin. idk why
15:54:28 opendevreview Michael Sherman proposed openstack/nova master: ironic: Restore retries on 409 and 503 from Ironic https://review.opendev.org/c/openstack/nova/+/1011683

Earlier   Later