15:02:36 #startmeeting cinder_bs 15:02:36 Meeting started Wed Jul 21 15:02:36 2021 UTC and is due to finish in 60 minutes. The chair is enriquetaso. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:36 The meeting name has been set to 'cinder_bs' 15:02:46 #topic agenda 15:02:50 #link https://etherpad.opendev.org/p/cinder-bug-squad-meeting 15:02:59 Cinder has 3 bugs reported this week. 15:03:08 #topic bug_1: "instance is using the wrong scsi disk after a stop/start" 15:03:13 #link https://bugs.launchpad.net/cinder/+bug/1936854 15:03:20 jbernard is facing this issue when using very old volumes as far as I understand. I left some question regarding the cinder version and the backend his using. 15:03:44 this is a bug originally reported internally and jbernard thinks is still relevant 15:04:36 make sense, so it's a master bug + rbd ? 15:05:39 OK, i'll ask after the meeting. Moving on.. 15:06:01 #topic bug_2: "c-bak appears to crash during tempest.api.volume.test_volumes_backup.VolumesBackupsTest.test_backup_create_attached_volume in CentOS 8 stream job" 15:06:14 #link https://bugs.launchpad.net/cinder/+bug/1936909 15:07:14 Some tempest test are failling with CentOS 8 Stream. I'll take a look later but if someone has more info regarding this let me know. Maybe tosky knows something about it. I'll ask him later. 15:07:34 :P 15:08:42 I don't know :/ 15:09:09 don't worry 15:09:10 #action (enriquetaso): take a look 15:09:17 #topic bug_3:" Failure on restoring imported Ceph backup" 15:09:25 #link https://bugs.launchpad.net/cinder/+bug/1936431 15:09:29 Ussuri - 15:09:37 Looks like a legit scenario. The reported deletes the backup in cinder but after that tries to importing the backup again and restore it to a volume but It fails. I'm not sure about the support of importing metadata in ussuri but I think I should work. Need to check it later. 15:11:03 and I suspect we don't have scenario tests for that scenario 15:12:01 we don't 15:12:19 #action (enriquetaso): see if this happens in master and check the root couse and add test scenario for this case. 15:13:32 Last topic of today's meeting: 15:13:37 #topic LVM CI failure 15:13:45 #link https://review.opendev.org/c/openstack/os-brick/+/798743 15:13:46 I'll update this patch today. I think we may want it before the new os-brick release wallaby... 15:13:51 whoami-rajat ^ 15:14:33 does the os-brick patch fix failures that are currently happening? 15:15:09 enriquetaso, since it's related to gate, it's not release dependent, but good to have 15:15:14 i thought the CI failures were tied to the cinder fix and this change was just needed to move from the cinder to os-brick code 15:15:23 i'm not sure it is related to gate 15:15:47 oh, it's true 15:16:51 yes, the failures were tied to the cinder fix 15:17:00 so, bad title 15:17:39 then it's good to have in the release 15:17:58 ++ 15:18:00 OK, that's all I have for today's meeting. 15:18:05 #topic open discussion 15:18:12 any bug to discuss here? 15:19:35 Can I ask about this bug from last meeting: https://bugs.launchpad.net/cinder/+bug/1934905 ? Unfortunately I wasn't able to join, but there was suggestion that it can be configuration issue. As it was working before(with Rocky release) I'm just wondering what kind of configuration can help here? I was following release documentation and I strongly 15:19:36 believe I didn't miss anything, so it's a bit tricky for me it's not working 15:24:24 * enriquetaso checking 15:29:27 OK, I can't figure out what's going on now, but could be a problem from the upgrade from Rocky. 15:31:24 sure, all other functionalities of cinder works perfectly fine, just cinder-backup is having this issue, retype cinder volume to ceph and then make a backup works...so it looks like an issue maybe with a driver to iscsi or something else. Especially that cinder backup volume is hitting error status, just after execution(miliseconds) 15:32:53 OK, I ran out of time.. Let me double check the bug and let's see what the cinder team could say about it from the bug report 15:33:06 sure, thanks! 15:33:16 #endmeeting