15:00:33 #startmeeting manila 15:00:33 Meeting started Thu Mar 2 15:00:33 2023 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:33 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:33 The meeting name has been set to 'manila' 15:00:38 o/ 15:00:49 o/ 15:01:03 hi 15:01:04 o/ 15:01:09 o/ 15:01:36 courtesy ping: dviroel vhari gouthamr 15:01:54 hi 15:02:32 o/ 15:02:56 hi 15:04:04 o/ 15:04:11 o/ hello everyone 15:04:19 good quorum, glad to see you here today 15:04:22 let's get started! 15:04:30 today's meeting agenda: 15:04:32 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:05:03 first topic for today is 15:05:06 #topic Announcements 15:05:22 Release Schedule: 15:05:23 #link https://releases.openstack.org/antelope/schedule.html 15:05:42 This is RC1 target week! 15:06:35 time flies 15:07:09 we are trying to target the bugs of our bugsquash for RC1 15:07:19 but so far, the features we have merged seem to be stable 15:08:01 I would like to thank you for all of the the reviews in the changes we had for feature freeze and also the other fixes we have been merging 15:08:56 it was tough to get things merged but we managed to merge a couple of features over this cycle 15:10:02 * dviroel o/ 15:10:04 that's all I had for announcements 15:10:09 * carloss waves at dviroel o/ 15:10:18 do you have an announcement to share with us today? 15:13:29 oh, actually I do have one more thing 15:13:41 do you plan on attending to the OpenInfra Summit in Vancouver? 15:14:06 there willl be a virtual PTG in the same time, so I would like to know if there are more people interested on participating 15:16:04 NetApp will be there with two members 15:17:38 oh, okay - thanks for the feedback felipe_rodrigues 15:18:43 I'll be possibly pinging later as well, but it is good to know how many parties are interested in attending 15:20:34 next topic 15:20:44 #topic Manila Bugsquash 15:20:56 so we have opened our bugsquash on Monday 15:21:07 and the theme of this bugsqush is: getting things done 15:21:38 we had the number of bugs increasing but one of the issues was that the bugs were stuck with fixes proposed 15:21:53 so we can tackle that with events like this bugsquash 15:22:23 #link https://ethercalc.net/8ru5hurhelyl 15:23:28 this is the ethercalc we are using to track the bugsquash bugs. 15:23:46 thank you for those reviewing the changes and submitting new patch sets 15:24:03 I believe we will be able to get a couple of bugs solved out of this 15:24:35 the target date for merging those bugs is today. In the EOD for me, I need to update the RC1 patch in the releases repo 15:24:46 so we will have the updated list of things landing for antelope 15:26:07 so please, keep updating this ethercalc and following up on reviews 15:27:33 the focus for reviews should be on the bugs of this list 15:27:42 feel free to review changes you are not assigned to as well 15:28:02 that's all I had for Bug Squash 15:28:11 is there something you would like to bring up in this meeting? 15:31:11 taking silence as no 15:31:19 vhari: thank you very much for helping to organize this! 15:31:27 and thank you everyone for participating 15:31:31 next topic 15:31:35 #Bug Triage 15:31:38 #link https://etherpad.opendev.org/p/manila-bug-triage-pad-new 15:31:38 carloss yw, glad to help 15:31:46 vhari: floor is yours 15:31:47 :D 15:31:51 :) 15:32:04 we have a bit of a new bug backlog today 15:32:09 lets jump it 15:32:12 #link https://bugs.launchpad.net/manila/+bug/2007560 15:32:59 so we are looking for minor triage on this an other bugs today, time permitting :) 15:35:36 gouthamr: can you remember `Was there any reason for not going with this approach?` ? 15:37:03 I think gouthamr may be afk now 15:37:12 but we can follow up on the comments 15:37:23 it seems like a question and something that could become a bugfix, yes 15:40:18 It seems that the discussion was to name one way, but the code names differently 15:40:35 yed 15:40:37 yes* 15:42:06 okay, let's follow up on the bug then 15:42:09 thanks for the report carthaca 15:42:17 you can add the bug to me 15:42:26 sure felipe_rodrigues 15:42:31 felipe_rodrigues++ carthaca++ 15:42:32 medium prio? 15:43:21 I don't know why I didn't notice this 5 years ago - better late than never 15:43:40 yep :D 15:44:00 uhh.. it doesn't break.. it causes some confusion.. wdyt carthaca "medium" or "low" ? 15:44:14 k, set to low 15:44:21 low ++ 15:44:25 nice 15:44:27 low 15:44:32 ++ 15:44:36 next up #link https://bugs.launchpad.net/manila/+bug/2008813 15:45:18 oh, this is an issue popping up on CI after we merged this change: https://review.opendev.org/c/openstack/manila/+/856144/4/manila/db/sqlalchemy/models.py 15:47:45 it's a problem with giving a unique name to azs, and apparently we are trying to create azs concurrently sometimes 15:49:40 what bugs us currently is that https://opendev.org/openstack/manila/src/commit/f075b1bd7d01516818693c930f9974227de50363/manila/db/sqlalchemy/api.py#L5696 should grant that the creation of the az is idempotent 15:49:51 so it requires further investigation 15:50:03 is there someone willing to take a look at this? 15:52:11 you can add me.. I will investigate and then maybe give it to another netapper, depending how the things go 15:52:16 thanks felipe_rodrigues 15:52:25 this is a good debugging exercise 15:52:35 and will be very helpful for the CI 15:52:51 ++ 15:53:14 ty felipe_rodrigues 15:53:27 carloss, do we have time for one more bug? 15:53:28 ty felipe_rodrigues :) 15:53:36 I think we do vhari 15:53:37 :) 15:53:42 #link https://bugs.launchpad.net/manila/+bug/2007719 15:53:58 if not we can continue in manila channel :) 15:55:17 oh, one that we realized after we merged share transfers 15:55:28 the thing is: we are doing migrations for sqlalchemy 2.0 15:56:52 is it a blocker for the migration ? 15:57:46 it would be, yes 15:57:50 so the idea is to change this 15:57:55 haixin: could you please take a look? 15:58:09 it's not supposed to be a huge change to apply the new way of using context 15:58:13 ok 15:58:50 thanks haixin 15:59:12 so it doesn't break anything (except when we migrate to sqlalchemy 2.0) 15:59:19 i'd say low/medium 16:00:50 that's a wrap for bugs .. thanks all for contributing to today's session 16:00:55 thanks vhari! 16:01:03 thank you all for attending to today's meeting 16:01:06 yw carloss 16:01:09 :) 16:01:12 let's continue the bugsquash activities 16:01:16 #endmeeting