15:04:09 #startmeeting cinder_bs 15:04:09 Meeting started Wed Nov 10 15:04:09 2021 UTC and is due to finish in 60 minutes. The chair is enriquetaso. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:04:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:04:09 The meeting name has been set to 'cinder_bs' 15:04:22 Welcome back to the cinder bug meeting. We have a quiet meeting today. Only 4 new bugs reported this period. 15:04:28 \o/ 15:04:33 Etherpad: 15:04:33 #link https://etherpad.opendev.org/p/cinder-bug-squad-meeting 15:04:33 Full list of bugs: 15:04:33 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025734.html 15:04:49 (i need to go to the tc/rback meeting, so will only partially be paying attention here) 15:04:55 I sent the email earlier and forgot lance bug 15:05:06 don't worry rosmaita 15:05:18 #link https://bugs.launchpad.net/cinder/+bug/1950474 15:05:36 #topic bug_1 tempest-integrated-compute-centos-8-stream fails with version conflict in boto3 15:05:48 #link https://bugs.launchpad.net/cinder/+bug/1950291 15:05:48 Summary: Cannot install cinder because boto3 package versions have conflicting dependencies. It seems it is blocking the nova master gate since 2021.11.09. 15:06:07 (i should attend the rbac meeting tough) 15:06:18 I don't think this is critical to Cinder because all the centos jobs were removed because of constant failure. 15:06:19 The only constraint I see from cinder is boto3>=1.16.51 # Apache-2.0 15:06:19 https://opendev.org/openstack/cinder/src/branch/master/requirements.txt#L67 15:06:19 I don't know what to do with this bug, it doesn't seem like a cinder problem... What do you think? 15:07:45 it looks like it was already resolved as an issue with openstack python mirrors 15:07:47 is marked Invalid currently 15:08:54 * enriquetaso facepalms 15:09:06 thanks eharney 15:09:16 #topic bug_2 [incomplete] InstanceLocality filter use results in AttributeError: 'Client' object has no attribute 'list_extensions'. 15:09:16 #link https://bugs.launchpad.net/cinder/+bug/1950134 15:09:27 Summary: Using InstanceLocality filter result in an exception when cinder tries to figure out the supported nova extensions: 2021-11-08 08:48:01.514 3120 ERROR oslo_messaging.rpc.server AttributeError: 'Client' object has no attribute 'list_extensions' 15:09:27 I did a quick search and there were no changes on our code regarding InstanceLocality recently. The last modifications were from queens. 15:09:27 I left a comment on the launchpad bug "I think the quickest way to find out is for you to contact the nova team on IRC" 15:09:55 just to let you know in case you're facing something similar ^ 15:10:02 moving on.. 15:10:10 #topic bug_3 [Invalid] NFS backend initialisation fails because an immutable directory exists 15:10:10 #link https://bugs.launchpad.net/cinder/+bug/1950128 15:10:21 Summary: Using a DELL Data Domain storage as NFS backend for cinder-backup, is causing problems for cinder-volume when starting cinder-volume. The storage is creating a `.snapshot` directory in every share. This directory is immutable. cinder-volume is trying to set ownership on the immutable directory. 15:10:21 Looks like this a credentials problem from kolla or DELL Data Domain setup. 15:11:04 Simon Dodsley proposed openstack/cinder master: [Pure Storage] Remove all REST version checks https://review.opendev.org/c/openstack/cinder/+/817085 15:11:05 that looks like a kolla script failing, not cinder code, right? 15:11:27 yes, that's why I marked it invalid, but just to double check 15:11:50 that's all I have for today's meeting 15:12:47 #topic Xena accept transfer policy breaks volume transfer workflow 15:12:53 #link https://bugs.launchpad.net/cinder/+bug/1950474 15:13:15 just for the record, I'm going to copy paste the options that lbragstad proposed 15:13:35 lbragstad> but you could 1.) update the volume project_id in the policy target to be the accepting user's project id 2.) add a new key to the volume policy target called destination_project and update the policy check string 15:13:36 3.) or update the policy to remove the project_id check 15:13:36 maybe a topic for the meeting which is ongoing now? 15:13:36 i guess 3 might be easiest (and backportable), it's pretty much like having "" as the policy checkstring 15:14:17 #topic open discussion 15:19:13 guess no other topics for today's, sorry for the super quick meeting. 15:20:29 Thanks eharney 15:20:33 thanks everyone 15:20:34 #endmeeting