15:03:59 <enriquetaso> #startmeeting cinder_bs
15:03:59 <opendevmeet> Meeting started Wed Feb 15 15:03:59 2023 UTC and is due to finish in 60 minutes.  The chair is enriquetaso. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:59 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:59 <opendevmeet> The meeting name has been set to 'cinder_bs'
15:04:35 <enriquetaso> hello, welcome to the bug meeting
15:04:51 <enriquetaso> #topic Failure to mount volumes with LUN ID > 255
15:04:55 <enriquetaso> #link https://bugs.launchpad.net/os-brick/+bug/2006960
15:05:09 <enriquetaso> Pure Storage by default uses peripheral addressing for LUN ID < 256 while it uses flat addressing for LUN >= 256 .
15:05:53 <enriquetaso> At some point, we stop discovering new volumes. It looks like /sys/class/scsi_host/host13/device/session7/target13:0:0/ targets goes from 13:0:0:1 to 13:0:0:255 and after that, no new luns can be mapped to the compute server.
15:06:13 <enriquetaso> The reason of this is explain in https://bugzilla.redhat.com/show_bug.cgi?id=1975368#c5
15:06:36 <enriquetaso> i think there's people working on this but not fix proposed to master yet
15:07:15 <whoami-rajat> isn't this a OS limitation that only allows LUN IDs from 0-255 ?
15:09:02 <enriquetaso> oh, sorry, i lost track of it
15:09:18 <enriquetaso> yes.. okay, then i'm not sure what is the state of the bug
15:09:37 <enriquetaso> i think it's out of cinder scope
15:09:39 <whoami-rajat> I'm going through it, the bug also says RHEL is able to detect those LUNs but not os-brick
15:09:49 <hemna-> https://access.redhat.com/solutions/5120951
15:09:52 <whoami-rajat> needs further investigation
15:10:43 <enriquetaso> hemna-++
15:12:32 <enriquetaso> okay, i'll point the articule and let's see what the reporter says
15:12:46 <opendevreview> Lukas Piwowarski proposed openstack/cinder-tempest-plugin master: Enable enforce_scope in -protection-functional job  https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/873939
15:13:37 <whoami-rajat> geguileor,  has a proposed solution which will require changes in the pure driver and os-brick code
15:13:39 <whoami-rajat> The solution would be to add a parameter to the connection information that tells the addressing mode when a conversion is needed (defaults to no conversion), and add the code to handle different values in os-brick.
15:14:30 <whoami-rajat> we can surely discuss it during PTG
15:14:47 <geguileor> whoami-rajat: I think we first need to know if someone would be working on this...
15:15:14 <geguileor> It's easy work, but special hardware may be required
15:15:38 <whoami-rajat> ok, would be good to bring it up during PTG and see it there are any takers
15:15:48 <enriquetaso> maybe the reporter would be interested in working on it, i'll leave a question asking happystacker
15:15:50 <rosmaita> seems like Pure would be interested in this
15:16:12 <enriquetaso> okay
15:16:46 <enriquetaso> sounds good to me
15:16:55 <opendevreview> Brian Rosmaita proposed openstack/cinder-tempest-plugin master: Get ready for tox 4  https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/868319
15:17:37 <enriquetaso> moving on
15:17:40 <happystacker> enriquetaso: I'm not the reporter or did I miss anything?
15:17:53 <enriquetaso> oh, sorry about it happystacker
15:18:00 <enriquetaso> lol
15:18:02 <happystacker> enriquetaso: np
15:18:21 <enriquetaso> #topic Error created new rsc_name in linstor driver
15:18:26 <enriquetaso> #link https://bugs.launchpad.net/cinder/+bug/2007275
15:18:30 <enriquetaso> Linstor driver ran into a problem with creating new volumes using the linstor driver. In the linstor logs, we see that cinder is trying to create a resource with an empty name.
15:19:06 <enriquetaso> too much `linstor` wording in that sentence
15:19:22 <enriquetaso> No fix proposed to master yet
15:19:47 <happystacker> name should be different from id
15:20:08 <happystacker> like volume-<id>
15:20:17 <happystacker> or something similar
15:21:05 <opendevreview> Vladislav Belogrudov proposed openstack/cinder master: Fix temp volume project id for Tatlin storage  https://review.opendev.org/c/openstack/cinder/+/858293
15:21:13 <opendevreview> Vladislav Belogrudov proposed openstack/cinder master: Tatlin Unified driver - simplify code  https://review.opendev.org/c/openstack/cinder/+/862491
15:21:18 <opendevreview> Vladislav Belogrudov proposed openstack/cinder master: Tatlin Unified driver - remove unused code  https://review.opendev.org/c/openstack/cinder/+/862489
15:21:28 <enriquetaso> i've left a comment happystacker, thanks
15:21:31 <opendevreview> Vladislav Belogrudov proposed openstack/cinder master: Tatlin unified driver - rename tatlin_api object  https://review.opendev.org/c/openstack/cinder/+/862490
15:21:33 <whoami-rajat> they're passing volume['id'] to the _is_clean_volume_name function
15:21:43 <whoami-rajat> i guess they should pass volume.name
15:21:54 <opendevreview> Vladislav Belogrudov proposed openstack/cinder master: Tatlin unified driver - rename tatlin_api object  https://review.opendev.org/c/openstack/cinder/+/862490
15:24:04 <enriquetaso> excellent
15:24:12 <enriquetaso> i've update with this comments
15:24:21 <enriquetaso> thanks
15:24:23 <enriquetaso> moving on
15:24:33 <enriquetaso> #topic  NFS Encryption Clone operation is broken
15:24:40 <enriquetaso> #link https://bugs.launchpad.net/cinder/+bug/2007139
15:24:49 <enriquetaso> This bug report aims to track the NFS encryption work. Is the last bug as far as I can tell and it has a fix proposed to master already.
15:24:54 <enriquetaso> The work for the NFS can be track using
15:24:58 <enriquetaso> #link https://review.opendev.org/q/topic:bp%252Fnfs-volume-encryption
15:25:08 <enriquetaso> Initial work is ready for reviews, please review after the priorities for this week:
15:25:12 <enriquetaso> #link https://review.opendev.org/c/openstack/cinder/+/749155
15:25:55 <enriquetaso> OK, moving on ( I have 5 minutes left)
15:26:00 <enriquetaso> #topic Service token does not work if user auth is token based
15:26:03 <enriquetaso> #link https://bugs.launchpad.net/keystone/+bug/2006631
15:26:07 <enriquetaso> Looks like a Keystone bug so I've removed Cinder from it.
15:26:11 <enriquetaso> rosmaita, ^
15:26:26 <rosmaita> i think that's correct
15:26:38 <rosmaita> we can always get added back if keystone disagrees
15:26:44 <happystacker> it's keystone right?
15:26:46 <rosmaita> but it looks like maybe a configuration problems
15:26:59 <happystacker> don't know what we can do about this one
15:27:00 <rosmaita> happystacker: well, keystoneauth1 specifically
15:27:06 <happystacker> correct
15:27:29 <rosmaita> i'm not sure what the constraints are on how you configure the service users in the various config files
15:27:41 <rosmaita> so hopefully keystone has some docs or something
15:28:35 <enriquetaso> I'll keep an eye on it then
15:28:42 <enriquetaso> last bug:
15:28:50 <enriquetaso> #topic Inaccurate docstring test_boot_cloned_encrypted_volume
15:28:54 <enriquetaso> #link https://bugs.launchpad.net/cinder-tempest-plugin/+bug/2006594
15:29:26 <enriquetaso> It's an error on a docstring. It's a good low-hanging-fruit for Outreachy potential intern
15:29:57 <enriquetaso> Thank you for being so active today and joining the bug meeting!
15:30:10 <happystacker> than you
15:30:13 <enriquetaso> #endmeeting