15:07:27 #startmeeting bug-report-cinder 15:07:27 Meeting started Wed Mar 10 15:07:27 2021 UTC and is due to finish in 60 minutes. The chair is enriquetaso. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:07:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:07:30 The meeting name has been set to 'bug_report_cinder' 15:07:33 I need to think of a more original and cool name for the next meeting. 15:07:40 :) 15:07:44 I couldn't fully prepare the etherpard for today's but I have some bugs to discuss: 15:07:51 #topic #bug_1:"Cinder ignores reader role conventions in default policies" 15:08:00 eharney, I'll work on a draft spec 15:08:03 #link https://bugs.launchpad.net/cinder/+bug/1917795 15:08:05 Launchpad bug 1917795 in Cinder "Cinder ignores reader role conventions in default policies" [Undecided,New] 15:08:15 In keystone, if I grant someone the reader role on a project [0], they're able to make writable changes in cinder. 15:08:15 Opening this bug to track work for cinder to consume keystone's default read-only `reader` role. 15:08:36 I am worried about doing this as we approach RC time but I think we want this for W, right? 15:08:49 well, we'll have to see 15:09:12 this is a bug, so not subject to FF 15:09:19 and it is a real bug, i think 15:09:55 ah OK, so I'll set medium importance 15:10:07 #topic bug_2: "Cinder request to glance does not support TLS" 15:10:18 #link https://bugs.launchpad.net/cinder/+bug/1917797 15:10:19 Launchpad bug 1917797 in Cinder "Cinder request to glance does not support TLS" [Undecided,In progress] 15:10:30 in https://github.com/openstack/cinder/blob/39e6008543cd72bbb0daebda676d69ec80bc7be4/cinder/image/glance.py#L107 15:10:30 the code does not send cert/key certificates to keystoneauth so if the glance API require TLS the request will fail 15:10:35 that doesn't sound right 15:10:41 or at least, needs a lot more detail 15:10:55 There's a patch for this so far: 15:10:59 #link https://review.opendev.org/c/openstack/cinder/+/778768 15:11:17 so, the bug it's not completed 15:11:25 so is this really about mTLS again? 15:12:09 yep 15:12:19 i don't think we can go adding support for security related features without the bugs/patches at least having a clear description of what's going on 15:12:22 as you mention last time this bug assumes that we support strict mTLS from cinderclient which i don't know is a reasonable assumption but worth fix it. 15:12:57 well, i find it concerning that someone who wants to work on this is not being precise about what they are talking about 15:13:02 me too 15:13:17 because it's not clear if we or they understand what the requirements actually are 15:14:12 i am going to request a spec 15:14:15 so this could be more a topic for the next PTG if the reported would like to prepare it? 15:14:23 oh spec sounds cool 15:14:26 yep 15:14:35 ok, next one 15:14:43 #topic bug_3: "Volume backup timeout for large volumes" 15:14:46 #link https://bugs.launchpad.net/cinder/+bug/1918119 15:14:47 Launchpad bug 1918119 in Cinder "Volume backup timeout for large volumes" [Undecided,In progress] - Assigned to kiran pawar (kiranpawar89) 15:14:52 There's a patch for this 15:14:53 #link https://review.opendev.org/c/openstack/cinder/+/779233 15:14:53 Update from today's meeting earlier: we are going to push it to Xena 15:15:07 just to double check ^ 15:15:09 i don't think this patch is even going in the right direction the longer i think about it 15:15:21 both Gorka and i left some feedback 15:15:35 cool, thanks! 15:15:56 Last one 15:16:03 #topic bug_4: "Cinder-backup progress notification has incorrect percentage." 15:16:10 #link https://bugs.launchpad.net/cinder/+bug/1918102 15:16:11 Launchpad bug 1918102 in Cinder "Cinder-backup progress notification has incorrect percentage." [Undecided,New] - Assigned to Jon Cui (czl389) 15:16:16 In the process of volume backup, Jon Cui found the percentage number was wrong for progress notification. 15:16:16 I wonder if this should be treat as medium o high importance bug. 15:16:34 do we give a real percentage or just make one up? 15:16:44 probably not high 15:17:25 good question 15:17:42 TIL: ctrl-L in my IRC client completely wipes out the buffer 15:17:42 ++++ backup_percent is 1.5832483768463135e-05 15:17:44 heh 15:17:46 the calculation looks wrong 15:18:01 dividing number of blocks by volume size, those aren't even the same units 15:18:01 hemna: sounds like one of your 2TB backups 15:18:24 rosmaita yah I think it's related to our backup setup. 15:18:44 we are suffering pretty bad for backups taking ages right now 15:18:55 we should just mark that as confirmed but it's medium prio at best 15:19:11 (probably low prio given that presumably it's been like that for ages with nobody noticing) 15:19:46 sounds good to me 15:20:05 #topic open discussion 15:20:20 ram usage peaked around 3G for the parallel backup w/ that patch 15:20:21 Not sure if we need a open discussion 15:20:43 one thing i've wondered about re: bug meetings 15:20:54 we also have an issue with expiring tokens for the backups taking that long 15:21:00 which kills the backup 15:21:04 we have a process for looking at incoming new bugs, do we need to periodically look at ones that have been stuck in in-progress for a long time? 15:21:35 hemna, do you have a link? 15:21:40 Simon Dodsley proposed openstack/cinder stable/victoria: Pure Storage: check volumename length does not exceed maximum https://review.opendev.org/c/openstack/cinder/+/779596 15:21:42 i think that expiration problem no longer happens if you configure things to use the correct style of keystone tokens etc 15:21:45 enriquetaso no, it's internal 15:22:05 eharney correct style ? 15:22:11 eharney, i think it's a good concern, I should probably start looking to older and stuck bugs too 15:22:21 hemna: https://docs.openstack.org/cinder/latest/configuration/block-storage/service-token.html 15:23:09 the problem is: how to do the report of 'stuck in in-progress' bugs, send an email? 15:23:44 probably 15:24:13 rosmaita I just checked out cinder.conf and we have teh send_service_user_token = true 15:24:54 do you have the username, project, etc for the service user? 15:25:32 #action enriquetaso: think a good way to report the 'stuck in in-progress for a long time' bugs 15:26:31 enriquetaso: short term, we could look them over at this meeting and see if they're still relevant 15:26:49 yah 15:26:55 ++ 15:27:02 OK 15:27:11 that's all I have for today's meeting 15:27:33 thanks, enriquetaso 15:28:08 #endmeeting