15:01:04 #startmeeting manila 15:01:05 Meeting started Thu Feb 6 15:01:04 2020 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:08 The meeting name has been set to 'manila' 15:01:13 hi :) 15:01:14 o/ 15:01:15 o/ 15:01:24 o/ 15:01:25 courtesy ping: xyang toabctl ganso vkmc amito jgrosso tbarron 15:01:31 o/ 15:01:38 hi all :) 15:01:51 hi 15:01:51 hi 15:02:25 hello o/ 15:02:54 o/ 15:03:07 good, we have quorum.. 15:03:29 our agenda looks short today: 15:03:31 #link: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:03:44 Let's get rolling 15:03:46 our agenda looks short today: <- last famous words 15:03:53 haha :D 15:03:57 #topic Announcements 15:04:34 sticky reminder to the Ussuri schedule, which, all of you imo are following diligently 15:04:47 #link: https://releases.openstack.org/ussuri/schedule.html (Ussuri schedule) 15:05:16 next week is our new driver and specification freeze 15:05:43 we'll talk about pending ones in a bit, but this is your reminder that any new specs must be submitted before next week 15:06:33 next, ty dviroel for taking our discussion from the last meeting to the OpenStack discuss ML 15:06:38 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012365.html (ML post on third party CIs) 15:07:02 gouthamr yw 15:07:36 there are some AIs there for vendor driver maintainers, if you're one of them, please pay attention - we'll check back likely during M-3 15:08:06 that's all the new stories i had; anyone else got anything? 15:08:54 #topic Tracking our work 15:09:35 dviroel++ 15:09:37 we're making good progress with the specs, we have two unmerged specs: 15:09:44 #link https://review.opendev.org/#/c/700776/ (Update Create Share from Snapshot in Another Pool) 15:10:06 ^ new PS sent today 15:10:20 We are almost there I think 15:10:50 ah, nice - i think my concerns are addressed with your latest PS 15:11:07 gouthamr yes 15:11:33 lets watch out for reviews from the rest of us, and look to close on this 15:12:15 #link https://review.opendev.org/#/c/704793/ (Add lite spec to fix unlimited share replicas per share) 15:12:38 you folks are early risers 15:13:01 there's a new patchset for this lite-spec too, please take a look 15:13:24 this is the first time we're doing one of these "lite" specs, ty carloss 15:13:32 carloss++ 15:13:46 my pleasure :) 15:14:29 cool.. Reviews needing attention: 15:14:48 Can we backport these to Train? (mnaser/tbarron) 15:14:48 #link https://review.opendev.org/#/q/topic:manila/generic-improvements+(status:open+OR+status:merged) 15:15:07 i think we should but im biased 15:15:08 :P 15:15:52 IMHO the changes are relatively small and localized, and help make me and users avoid running a fork to be able to use generic driver with no neutron-*-agent running 15:15:57 and the tests are there too 15:16:49 i'm inclined to see these as fixes/improvements rather than "new feature" but admit it's a grey area 15:16:58 and I want to avoid forks 15:17:03 +1 15:17:12 #link https://docs.openstack.org/project-team-guide/stable-branches.html (Stable branch policies) 15:17:31 mnaser: Train is the final destination for these 15:17:33 ? 15:18:36 although we tweaked the definition of the stable branches a while ago, and they no longer make a distinction between the last release and previous releases 15:19:23 it's less risky for us to backport this to train than earlier versions, knowing that distributors are still actively following Train 15:19:52 and may not be tracking other branches as much, going by my limited knowledge of distros (i work for one) 15:20:37 s/tracking/tracking, syncing, packaging, testing/g 15:22:02 ... 15:22:41 okay, if there don't seem to be any objections here, please propose the backports and we'll take comments/concerns to review 15:23:14 +1 15:23:43 #link: https://review.opendev.org/#/q/owner:tamm.maari%2540gmail.com+status:open 15:24:02 maaritamm: it looks like you need to rebase some of these 15:24:22 ty for adding stuff to the osc repository 15:24:28 * gouthamr adds it to review backlog 15:25:16 yeap, will rebase 15:25:44 ty maaritamm, and for those that are actively reviewing these 15:26:08 :) 15:26:11 ++ 15:26:33 ty maaritamm 15:27:18 ty maaritamm 15:27:30 rest of you, please take some time to review these, there's a ton to do for OSC parity with our client - and maaritamm could use some feedback and motivation :D 15:27:37 #link https://review.opendev.org/#/c/701340/ 15:28:46 ^ solves an interesting problem for u 15:28:48 us* 15:29:17 it removes test classes from showing up as "skipped" when they don't make sense at all 15:29:55 for example, tests that attempt running GlusterFS specific tests against the ZFSOnLinux driver 15:30:30 because of this refactor, we can now not have those tests show up in the test listing as well 15:31:45 it probably helps folks looking to certify manila backends - they can no longer worry about some types of skipped tests 15:32:52 so, ^ needs your reviews - please do so early, would like this to merge soon as well, so we can cut a new release for manila-tempest-plugin at M-2 15:33:26 any other reviews that we should talk about here? 15:33:59 #topic Bugs (vhari) 15:34:30 #link: https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) 15:34:55 * gouthamr paging vhari 15:34:59 gouthamr, ty 15:35:10 https://bugs.launchpad.net/manila/+bug/1860264 15:35:10 Launchpad bug 1860264 in Manila "Unitest failing with python 3.8" [Undecided,New] 15:36:18 this one's new to triage 15:36:28 ack ty vhari 15:37:08 * gouthamr checks something real quick 15:38:01 so, we have `openstack-tox-py38` running against manila on the master branch for weeks now 15:38:52 https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_2dd/706084/1/check/openstack-tox-py38/2dd0467/testr_results.html 15:39:08 all the hacking unit tests did pass on our CI 15:39:39 so am confused 15:39:42 interesting! 15:40:10 let me respond to this bug, and ask for a traceback 15:40:34 also haven't run py38 tests myself, i can take a look at this after this meeting 15:40:50 ack (y) 15:40:56 and i'll set the flags necessary if we're able to reproduce the failure locally 15:41:04 i'm* 15:41:37 next on the list, waiting for info .. could use some traction 15:41:40 https://bugs.launchpad.net/manila/+bug/1838189 15:41:40 Launchpad bug 1838189 in Manila "DevStack (./stack.sh) can not found test-requirement.txt dir" [Undecided,New] 15:42:25 hmmm, we asked the reporter a couple of questions 15:42:32 let's mark this one Incomplete 15:42:40 +1 15:42:48 +1 15:42:52 +1 15:43:45 cool .. moving on 15:44:04 next 2 are to be reviewed as possible dups 15:44:13 https://bugs.launchpad.net/manila/+bug/1631314 15:44:13 Launchpad bug 1631314 in Manila "Tempest tests "test_promote_out_of_sync_share_replica" and "test_resync_share_replica" are concurrency-prone" [Medium,Confirmed] - Assigned to Douglas Viroel (dviroel) 15:44:19 https://bugs.launchpad.net/manila/+bug/1607150 15:44:20 Launchpad bug 1607150 in Manila "Tempest test for dr/readable replication fails because share has two active replicas" [Medium,New] 15:45:28 both are results of racy operations, but they aren't duplicates 15:45:55 k 15:47:08 the latter can occur for a minute duration if users query the manila API while database transitions are happening - the bug proposes two ways to mitigate this 15:47:16 we need to find an owner to investigate 15:47:31 dviroel: any status on the first one? 15:48:15 gouthamr not yet, the proposed solution will take extra effort 15:49:31 cool, don't see a reason to rush this - these aren't user reported issues, but would be nice to have them fixed 15:50:14 cool, any more thoughts on this one? 15:50:19 it's highly unlikely that we'll hit these in production, and be negatively affected - i.e., a resource is already in the state you expect to put it in by the time you've pulled the trigger 15:51:50 anything else, vhari? 15:52:08 that's a wrap for this week :) 15:52:19 vhari: awesome, thank you 15:52:24 #topic Open Discussion 15:53:25 looks like we can take some time back :) 15:53:42 thank you all for joining, see you again next week 15:53:48 thks! 15:53:52 thanks 15:53:54 #endmeeting