14:01:00 #startmeeting cinder 14:01:00 Meeting started Wed Mar 9 14:01:00 2022 UTC and is due to finish in 60 minutes. The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:00 The meeting name has been set to 'cinder' 14:01:07 #topic roll call 14:01:15 o/ 14:01:21 Hi 14:01:21 howdy 14:01:21 hi 14:01:30 hi 14:01:40 o/ 14:01:45 o/ 14:01:58 hi 14:02:07 hi! o/ 14:02:08 hi 14:02:29 hello 14:02:43 hello everyone 14:02:59 #link https://etherpad.opendev.org/p/cinder-yoga-meetings 14:03:11 let's get started! 14:03:17 hey 14:03:38 daylight savings time in USA starts 13 March, so this meeting may be 1 hour later for you next week depending on where you are 14:03:52 so, if you show up and no one is here, come back in an hour 14:04:00 you will not have missed anything 14:04:06 :-) 14:04:19 the first Yoga Release Candidate (RC-1) must be made this week 14:04:31 at that time, the stable/yoga branch will be cut 14:04:38 master becomes the Zed development branch 14:04:58 any changes must be made in master and then backported to stable/yoga to be in the release 14:06:23 so, let's prioritize 14:06:32 https://etherpad.opendev.org/p/cinder-yoga-release-critical-changes 14:07:06 first, for new drivers coming out in Yoga, if you have a bugfix you discovered, it would be good to get those into the Yoga release 14:07:35 btw, these don't require a release note because the driver doesn't exist yet 14:08:09 the "transition-to-alembic" patches continue to be important 14:09:14 and there aren't too many left 14:09:37 are the merged alembic changes stable enough that we can move the rest for Zed? or they need to be in yoga only 14:10:20 i need to talk to stephenfin about that 14:11:11 the other things we should take a look at are the "known issues" in the xena release 14:11:24 https://docs.openstack.org/releasenotes/cinder/xena.html#known-issues 14:13:45 rosmaita: there are a couple of issues on the nvmet target 14:14:07 known by me, I mean 14:14:08 you mean left over from xena, or new ones for yoga 14:14:25 I'm not currently working on the encryption problem but it's on my TODO list. If anyone would like to work with me on that to speed things up, let me know.. :P 14:15:06 rosmaita: as far as I know we've had them since the begining of the nvmet target 14:15:10 enriquetaso: that's Bug #1888680 ? https://bugs.launchpad.net/cinder/+bug/1888680 14:15:12 we just didn't know 14:15:52 yep, the ones mentioned on Known Issues 14:16:34 geguileo: ok, let's talk later and work out the text about nvmet known issues 14:17:06 i believe jon bernard is workign on the cgroups v1 issue 14:18:13 Bug #1937084 (race condition between delete attachment and delete volume) ... pretty sure geguileo fixed that and it's been backported 14:18:18 \o/ 14:18:26 yup 14:19:15 https://bugs.launchpad.net/cinder/+bug/1895035 ("Ceph backup driver could not restore a volume other than ceph") doesn't have a patch associated with it in launchpad 14:19:22 anyone know the status of that one? 14:20:57 it's ready for upstream reviews 14:21:13 cool, do you have a review link? 14:21:21 #link https://review.opendev.org/c/openstack/cinder/+/750782/ 14:22:22 ty 14:22:26 \o/ 14:23:26 ok, last thing was a warning to operators not to manage really old qcow2 images into cinder from an nfs backend 14:23:50 bug 1937084 is mentioned as something we are working on in the release notes -- but it's been fixed 14:24:25 yes, thanks to geguileo i think 14:25:40 as far as the operator warning goes (about managing v2 qcow2s into cinder from nfs backend), we can repeat in Y and think about blocking this in code in Z 14:27:05 sounds good, operators need to make this transition eventually 14:28:06 any questions or observations before we move on? 14:29:20 ok, only one agenda item, so maybe this will be a quick meeting 14:29:34 #topic question about translation pattern 14:30:04 well, you can look here to see what I'm talking about: 14:30:13 #link https://review.opendev.org/c/openstack/cinder/+/819778/8/cinder/volume/drivers/huawei/huawei_conf.py#436 14:30:16 rosmaita: You are going to jinx it. :-) 14:30:44 yeah, somehow a discussion of logging is always contentious 14:31:50 i feel like i'm missing something about how this is supposed to work 14:32:10 :-) 14:32:12 if you want the log messages to be in english, would you not just have the service running with an en_US locale or so? 14:32:37 i think if you do that, the exception messages that show up to the user are english too 14:32:55 are they? really not sure 14:33:03 Yuval is still here 14:33:11 the idea was that operators want the logs in english to maximize the chance they'll get a hit when googling the message 14:33:20 well, tbh, i am not sure either 14:33:34 I think everything uses the same language 14:33:38 (but could be wrong) 14:34:03 i guess i was hoping that API requests were requesting a language via http headers 14:34:50 at any rate, it would seem like a good idea to understand the requirements before we ask everyone to duplicate all of their error messages in the code, because that's just... uhy :/ 14:35:04 i figured that since they made a big deal about it in the oslo.log docs, this must be what you have to do 14:35:12 maybe so 14:35:19 but also maybe not 14:35:32 which, as was pointed out in the review, surely means that most of them in cinder aren't done right 14:36:05 yep 14:36:53 ok, seems like the thing to do short-term is continue our current practice 14:36:58 don't translate log messages 14:37:08 do translate messages for exceptions 14:37:12 https://docs.openstack.org/oslo.i18n/latest/user/guidelines.html 14:37:15 says "_() is preferred for any user facing message, even if it is also going to a log file." 14:37:21 rosmaita: That was my latest understanding. 14:37:41 But then we have the line that eharney highlights. :-) 14:38:10 keep reading, though: "However, now that log messages are no longer translated, it is unfortunately necessary to use two separate strings: a plain one for the log message, and a translatable one for the exception." 14:38:32 dramatic twist! yeah... 14:38:58 *duh duh ... dah!* 14:39:11 So, that would appear to be the answer then. 14:39:24 i wonder if anyone at all is actually doing this (where 'this'==duplicate strings) 14:39:41 i bet everyone stops reading at the line eharney pointed out 14:39:47 Honestly, I don't think I have seen that in the code. 14:39:55 Yep. 14:40:02 i don't think i've seen it anywhere in cinder 14:40:04 well, most people look for info, and find it, and don't assume that the next paragraph is going to tell you the opposite thing :) 14:40:06 but is someone translating exceptions? 14:40:18 if nobody is translating anything, what's the point? 14:40:24 also true 14:40:34 well, we do get occasional .po file updates 14:41:57 ok, let's take eharney's sentence "_() is preferred for any user facing message, even if it is also going to a log file. This ensures that the translated version of the message will be available to the user." as the current cinder approach 14:42:38 we can ask the TC about this at the PTG 14:43:00 ok 14:43:04 it looks like we maybe just fully removed a few languages this year from cinder's translations. wonder why 14:43:38 https://review.opendev.org/c/openstack/cinder/+/809944 14:44:53 Interesting. 14:44:54 Spanish survived!!! 14:45:09 :-) 14:45:10 \o/ 14:45:14 ha 14:45:21 Survivors. 14:45:33 French and Italian ... gone. 14:45:40 Hola 14:45:47 lol 14:45:53 :-) 14:46:02 _('Hello') 14:46:12 * fabiooliveira hahaha 14:46:21 i have no idea, the instructions to PTLs are to merge those patches right away as long as they don't break any tests 14:46:31 Exception: Hola 14:46:44 Hola Mundo! 14:46:49 :P 14:47:12 * jungleboyj stops before he embarrasses himself 14:47:32 ups 14:47:49 maybe a threshold issue? 14:48:20 I guess I will have to take a look 14:48:58 tosky: how do you mean? they didn't translast at least x% of the messages, and thus were dropped? somehting like that? 14:49:31 Or lack of translation volunteers. 14:50:21 ok, so we have discussed this and reached a conclusion ... namely, continue to do what we have been doing 14:50:23 thanks! 14:50:29 #topic open discussion 14:50:47 ++ 14:53:22 https://review.opendev.org/c/openstack/cinder/+/800704 is a patch that just removes a bunch of dead code if someone wants an easy review 14:53:29 it was approved a while ago but got stuck in a merge conflict or something 14:53:44 where is Sean? He loves dead code. 14:55:05 ok 14:55:31 do we have a mypy patch for this week? 14:56:05 well https://review.opendev.org/c/openstack/cinder/+/774288 was the mypy patch from a few weeks ago, it was approved but didn't merge because nobody has reviewed its parent patch yet 14:56:49 oops 14:57:03 just realized my comment on the parent is still in draft 14:57:15 (it was a positive comment) 14:57:18 #link https://review.opendev.org/c/openstack/cinder/+/818830 14:57:18 there are more of them out there under the "mypy" topic 14:57:25 I'll review the parent 15:00:49 ok, that's all we have time for ... 15:00:52 #endmeeting