15:00:43 #startmeeting manila 15:00:45 Meeting started Thu May 20 15:00:43 2021 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:48 The meeting name has been set to 'manila' 15:01:00 courtesy ping: ganso vkmc dviroel carloss tbarron felipe_rodrigues esantos vhari 15:01:09 hi 15:01:10 o/ 15:01:19 o/ 15:01:19 o/ 15:01:20 o/ 15:01:20 o/ 15:01:26 hi 15:01:51 hello o/ 15:02:13 thanks for joining, here's our agenda for the day: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:02:27 o/ 15:02:55 #topic Announcements 15:03:19 Xena-1 milestone is on May 28 15:03:26 #link https://releases.openstack.org/xena/schedule.html 15:03:46 #link https://launchpad.net/manila/+milestone/xena-1 15:04:11 we have a lot of bugs targeted to this milestone, if you own one, please take a look! 15:06:02 We also tagged the final release from the stable/train branch last week 15:06:33 #link https://releases.openstack.org/train/#manila 15:07:28 we have a number of issues with CI on this branch, so several bugfix patches didn't make it to this release; however, we're actively working on getting CI working again 15:07:42 so they should work pretty soon.. 15:08:17 there's a discussion on the ML regarding our use of freenode 15:08:45 if you have an opinion, do participate in this thread! 15:08:47 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022539.html 15:09:07 that;s all the announcements i had lined up.. anyone else got any? 15:10:06 we do have some good news from Outreachy :) but we'll share that next week as things formalize.. 15:10:12 #topic M-1 Bug Squash 15:11:08 vhari is working on putting a list together for this upcoming bug squash, but we've not decided the dates 15:11:28 so i wanted to know your thoughts on it 15:11:59 last cycle, we had two flavors of the bugsquash - one that lasted ~1 day and one that lasted the whole week 15:13:14 do folks have a preference on what to do this time around? 15:14:01 i don't think we dedicated all of the week, but we did land a lot of bugfixes, and focussed on reviews during the week 15:14:40 a successful bugsquash for me is when we all participate and feel good about contributing to a fix :) 15:15:34 so what makes sense? would you like a ~1 day bug squash for M-1 where we have a 1-hour sync meeting? 15:16:09 the m-f flavor, where we'd have a sync on monday and thursday 15:16:27 or a shorter 3 day flavor 15:16:47 i meant for this to be a ptg discussion topic - so excuse the verbosity of this 15:18:22 🦗 15:19:57 * gouthamr notes vhari has irc troubles 15:20:36 I guess we can try out the option of the m-f flavor 15:20:44 with a sync on monday and thursday 15:21:21 +1 15:22:20 i like that option - any objections? 15:23:40 its probably short notice to use next week, and i'm out a bit the week after, it's also a long weekend in the US 15:24:11 week of 7-11, 14-18 June is good 15:24:53 our spec freeze is on Jun 25 15:25:16 ++ 15:25:18 so we'll work a bit on the dates based on these constraints 15:26:13 and share more details on the ML soon 15:26:23 any questions/concerns/suggestions? 15:28:02 alright, lets move to the next, related topic 15:28:09 #topic 2-day M-2 hack-a-thon ideas 15:28:16 #link https://etherpad.opendev.org/p/xena-hackathon-manila (M-2 Hack-a-thon ideas) 15:28:57 alright, this is a new thing we're trying this cycle :) its much like the bugsquash 15:29:05 and much like a midcycle 15:29:15 except we'd be working on something together 15:29:43 we've done some localized hackathons in the past to work on some features 15:30:02 but it'll be fun to work on something together, albeit virtually 15:30:31 on that etherpad ^ there are a few ideas of things that allow any number of us to simultaneously code 15:31:20 my initial thoughts on this was to keep a bridge open with breakout rooms that we can get into for brainstorming 15:31:57 please feel free to add to the etherpad 15:32:11 we can gather ideas and use it as a sign up sheet 15:33:21 this would be closer to m-2, and we can circle back to this one in future irc meetings and get firmer ideas 15:35:21 #topic State of the CI 15:35:27 #link https://etherpad.opendev.org/p/manila-ci-issues (Manila CI issues) 15:35:34 so, we're in a pickle 15:35:55 we have a couple of bugs on two non-voting CI jobs on the trunk branch 15:36:25 - container driver: https://bugs.launchpad.net/manila/+bug/1921543 15:36:25 Launchpad bug 1921543 in OpenStack Shared File Systems Service (Manila) "Postgresql fails to apply default sort key when using "--with-count"" [Undecided,New] - Assigned to Carlos Eduardo (silvacarlose) 15:36:26 - generic driver cifs issue: https://bugs.launchpad.net/manila/+bug/1903922 15:36:27 Launchpad bug 1903922 in OpenStack Shared File Systems Service (Manila) "Generic driver fails CIFS online extension test " [Medium,New] 15:36:59 we should be okay now on stable/victoria 15:37:03 https://bugs.launchpad.net/manila/+bug/1928879 15:37:03 Launchpad bug 1928879 in OpenStack Shared File Systems Service (Manila) "[ci] stable/victoria tempest jobs fail because of incompatible API versions" [High,Fix released] - Assigned to Goutham Pacha Ravi (gouthamr) 15:37:40 so if you have patches in stable/victoria - or were waiting to make a backport, please check 15:38:28 i'm still working on stable/ussuri and stable/train changes - both of these branches have myriad issues 15:39:24 and i feel like we have too many jobs on extended maintenance branches (stable/train transitioned to extended maintenance last week) 15:40:23 a glimmer of hope is that a stable/ussuri job seems to work on manila-tempest-plugin with minimal configuration: 15:40:33 #link https://review.opendev.org/c/openstack/manila-tempest-plugin/+/725692 (Add stable branch jobs on the plugins master gate) 15:41:13 but, we don't use the native zuulv3 style jobs on this branch 15:41:31 and i dunno how much effort's involved in porting those to stable/ussuri 15:42:36 surely not a trivial amount, but that's one thread i'd like to chase today and find out 15:43:28 we have people proposing fixes to stable/queens, stable/train that would have to probably wait longer for these fixes to land 15:44:48 if you're affected, and would like to work to get the CI on these branches working - your help is much appreciated! 15:46:21 please ping me in case you want to learn how these fixes work too... i feel like this knowledge is best spread across the team and there's little we can document out of each specific fix 15:48:37 that's all on the topic - and in case you were wondering about all those CI patches floating around 15:48:49 any other thoughts? 15:49:18 thanks for working on those gouthamr! 15:50:06 :) 15:50:26 alright, we've 10 mins for a minor bug triage session 15:50:30 #topic Bug Triage (vhari) 15:50:49 vhari is having troubles with her irc today, so i'll take a peek 15:50:53 #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) 15:51:27 she's groomed the list for us! ty vhari! 15:51:29 #link https://bugs.launchpad.net/manila/+bug/1920888 15:51:29 Launchpad bug 1920888 in OpenStack Shared File Systems Service (Manila) "Share list sorted by 'availability_zone' return 'wrong sorting key' error." [Undecided,New] - Assigned to Jon Cui (czl389) 15:53:34 hmmm, that's certainly a bug 15:53:47 hmm 15:53:55 that should be on the cli 15:53:58 python-manilaclient 15:54:14 good point 15:54:17 seems the reporter is working on that 15:54:20 gouthamr, want me to triage? 15:54:42 not sure if this is reproducible in master, they claim it's on train 15:54:45 vkmc: yep.. 15:54:47 so we should check that 15:54:48 oki 15:55:36 thanks vkmc++ 15:56:10 i just checked trunk, with the latest manilaclient, and it doesn't have that issue 15:56:19 i dunno if this was fixed recently though :) 15:56:30 so we're perhaps missing some backport 15:56:39 yes 15:56:43 we will need to test with train 15:56:51 I'll ask the reporter and try to test on an environment 15:56:57 in the meantime I'll set this to medium 15:57:03 just leave this on new while we try to reproduce 15:57:04 ah yes! 15:57:07 #link https://review.opendev.org/c/openstack/python-manilaclient/+/782635 15:57:22 so you're right this is a client bug, vkmc 15:57:23 oh! 15:57:26 ok 15:57:38 merged last month 15:57:44 so, we can confirm this 15:57:49 the bot probably didn't close it because manilaclient wasn't in the list of affected projects 15:58:12 yep, we can mark this invalid against manila, and set manilaclient and tag it as "Fix Proposed" 15:58:18 * gouthamr ew paperwork 15:58:48 yep, but that is master, not train 15:58:51 so backport still needed 15:59:19 yep 15:59:23 oki, triaged 16:00:02 thanks vkmc - just posted the stable/wallaby backport 16:00:07 alright we're at the hour 16:00:13 hackerman 16:00:32 thanks for joining everyone - we'll sync on #openstack-manila and here next week! 16:00:37 stay safe.. 16:00:39 #endmeeting