15:03:09 #startmeeting Manila 15:03:09 Meeting started Thu Nov 11 15:03:09 2021 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:09 The meeting name has been set to 'manila' 15:03:19 o/ 15:03:21 * carloss was having troubles with irc cloud 15:03:23 o/ 15:03:38 \o 15:03:40 courtesy ping: ganso vkmc tbarron felipe_rodrigues ecsantos vhari fabiooliveira 15:03:45 o/ 15:03:45 o/ 15:03:49 o/ 15:03:52 o/ 15:04:05 o/ 15:04:19 o/ 15:05:16 I believe other people might be having troubles with irccloud too :) 15:05:28 hi 15:05:32 hi 15:05:43 * tbarron is in two meetings ... 15:05:46 I think we have a good quorum, so let's get started with our meeting agenda :) 15:05:51 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:06:19 #topic Announcements 15:06:37 The first announcement we have is about our first milestone of this cycle 15:07:01 M1 deadline is next week! 15:07:17 #link https://releases.openstack.org/yoga/schedule.html 15:07:33 wow, M1... Time is flying! :) 15:07:44 #link https://launchpad.net/manila/+milestone/yoga-1 15:08:10 if you have a bug targeted to this milestone, there's still time :) 15:08:45 ping reviewers if you need some help or if you want to re-target a change you have, please let us know 15:09:02 and the last announcement we have for today: 15:09:15 Our first bugsquash of the year! \o/ 15:09:43 \o/ yaaay 15:09:55 we have some new faces here, so I'll briefly mention what usually happens during the bugsquash event 15:10:14 this event is focused on closing the most bugs we can... 15:10:44 we have a bigger number of changes being submitted and reviewers more focused on reviewing the bugfixes 15:11:10 it is a good opportunity to get to work with other community members 15:11:20 also, good to learn with reviews and solving some bugs :) 15:11:46 we usually start with a list of bugs (that are commonly gathered by vhari) 15:12:29 if we have bugs that don't have an assignee, we try to find a volunteer to work on such bug during the bugsquash week 15:12:45 * vkmc in two meetings too 15:12:48 buzyrillas 15:13:06 this event has been a success in the past cycles and we're excited for the next one 15:13:15 xD 15:14:23 the list of bugs for the bugsquash is being formed 15:14:36 and the date should be defined in the next few days... 15:15:14 so stay tuned in the openstack-discuss mailing list :) 15:15:33 alright, that's everything I had in terms of announcements 15:15:37 anyone else got any? :) 15:17:23 taking the silence as a no 15:17:23 :D 15:17:26 okay, moving on... 15:17:35 #topic Reviews needing attention 15:17:52 #link https://etherpad.opendev.org/p/manila-yoga-review-focus 15:18:24 there are few items on this list and some of them depending on action from reviewers 15:18:33 or for some, the change owners 15:18:46 reviews on those are always welcome... 15:19:26 for this meeting, I'd like to ask if someone wants to bring our attention to a specific change 15:21:36 * crickets * 15:21:40 :) 15:22:05 okay, moving on... 15:22:05 800753: Manila share support Recycle Bin | https://review.opendev.org/c/openstack/manila/+/800753 15:22:12 this need attention 15:22:14 oh, great 15:22:32 :) 15:23:06 this change miss X version freeze 15:23:58 yes... thanks for bringing our attention to it haixin 15:24:10 I'll take a look on it 15:24:21 thanks carloss! 15:24:31 anytime haixin 15:24:45 on to the next topic... 15:24:59 #topic Bug Triage (vhari) 15:25:21 I see vhari couldn't join us today 15:25:34 but she gathered the list and we can take a look in the items :) 15:25:37 but I'm here for her 15:25:38 :D 15:25:45 oh, good vkmc :D 15:25:46 #link https://etherpad.opendev.org/p/manila-bug-triage-pad-new 15:26:11 first bug in the list 15:26:13 #link https://bugs.launchpad.net/manila/+bug/1950313 15:26:43 seems to be a feature request? 15:27:57 it seems like it 15:28:02 or at least a RFE 15:28:16 yeah 15:28:23 not sure if anybody is working on it 15:28:30 and if there is a target 15:28:43 I see Kiran has been working on it 15:28:43 https://review.opendev.org/c/openstack/manila/+/817379 15:28:48 #link https://review.opendev.org/c/openstack/manila/+/817379 15:28:48 oh cool 15:29:23 so 15:29:25 as we already have the change, should it be targeted to m-2? 15:29:51 I think so 15:30:32 medium, confirmed 15:30:44 and assigned to Kieran 15:30:47 next one 15:31:14 #link https://bugs.launchpad.net/manila/+bug/1723513 15:31:19 this one seems to be triaged already 15:32:32 seems it's being reproduced in centos 7 15:33:11 yes... 15:33:41 it is assigned to me (and it was assigned to dviroel before he handed it to me :)) 15:33:54 I didn't get a chance to reproduce nor fix this issue in the past though 15:34:00 looking 15:34:21 but as we have customers hitting it now, I believe we could reassign it to one of the NetAppers :) 15:34:29 reported in 2017 15:34:30 =x 15:35:06 yes sfernand 15:35:39 any NetApper willing to take it? :) 15:36:20 * i think* that we solved a similar issue, with retries, let me search on the code and will add my concerns in the bug 15:36:23 can you assign it to Fabio? He will be prioritizing NetApp bugs for Cinder and Manila during the next week 15:37:44 sfernand, ack. thanks! 15:37:53 thanks dviroel :) 15:38:52 dviroel: cool 15:38:55 sometimes, ontap lies to us :P 15:39:06 and we need to ask again 15:39:32 hahaha yep, sometime happen with snapmirros 15:42:15 :) 15:42:17 nice 15:42:18 next one? 15:42:46 next one 15:42:47 #link https://bugs.launchpad.net/manila/+bug/1824442 15:43:05 shall we move this one to won't fix? 15:44:27 hmm 15:46:16 * carloss reads the discussion in the bug's comments 15:46:55 seems yes to me 15:46:55 but 15:46:59 need another +1 15:47:00 :) 15:47:02 makes sense to me to do that :) 15:47:30 s/to do that/to move it to won't fix 15:47:44 done 15:47:56 I'm still somewhat inclined to say that we should just not expose that info, but others said that "fixing" that would be backwards-incompatible 15:49:10 there is place for enhancement there 15:49:45 we should keep it for future improvement 15:50:49 * vkmc won't fix -> high 15:50:55 * vkmc won't fix -> confirmed* 15:51:29 vkmc: I don't think it's a major security risk, just not regular user's business 15:51:54 yeah 15:51:59 tbarron++ 15:52:08 orobably the right fix would be to make it controlled by policy 15:52:09 and wrt backwards compatibility 15:52:13 probably 15:52:17 if it's not users biz 15:52:25 why hiding it would impose an issue? 15:52:52 because we used to expose it and somebody may have tooling that counts on the old api response 15:53:15 * tbarron makes the position against his suggested fix 15:53:42 xD 15:54:15 well, but here we should take a stand 15:54:16 and say 15:54:24 "because we care about you, we will hide this" 15:54:36 maybe do it gentle 15:54:37 but do it 15:56:02 ok, let's move it to confirmed and we can revisit 15:56:33 next one 15:56:36 #link #link https://bugs.launchpad.net/manila/+bug/1475351 15:56:39 agh 15:56:40 #link https://bugs.launchpad.net/manila/+bug/1475351 15:58:21 apparently we need a new taker for this bug, right? :) 15:59:28 yeah, seems it's a sneaky one 15:59:33 ok, we are one minute away 15:59:37 let's push it for next meeting 15:59:42 ack :) 15:59:46 thanks vkmc 15:59:48 (one min away for the end of the meeting) 15:59:51 thanks folks 15:59:57 (and thanks vhari for putting the list together) 16:00:04 alright folks! 16:00:15 thank you all for joining today! 16:00:16 carloss++ 16:00:23 see you in #openstack-manila :D 16:00:28 #endmeeting