15:00:20 #startmeeting manila 15:00:20 Meeting started Thu Mar 31 15:00:20 2022 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:20 The meeting name has been set to 'manila' 15:00:33 o/ 15:00:39 o/ 15:00:45 o/ 15:01:06 o/ 15:01:29 o/ 15:01:36 o/ 15:01:42 o/ 15:01:53 o/ 15:01:58 o/ hello!! 15:02:25 o/ 15:02:43 courtesy ping: ganso vkmc dviroel tbarron vhari fabiooliveira 15:02:57 hello everyone! 15:03:14 glad to have you here 15:03:17 let's get started 15:03:35 o/ 15:03:45 o/ 15:04:35 gouthamr mentioned in the last meeting, but the OpenInfra live featuring the updates for the Yoga release is happening right now! 15:04:51 we had a couple of contributors to share the updates of their projects already 15:05:09 but if you want to watch it after, just go to the OpenInfra foundation channel 15:05:12 #link https://www.youtube.com/channel/UCQ74G2gKXdpwZkXEsclzcrA 15:05:25 starting with today's agenda: 15:05:34 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:05:49 #topic Announcements 15:06:27 The announcement for today is that Yoga is officially released! \o/ 15:06:39 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027916.html 15:06:51 There is some information on the release itself here: 15:06:55 #link https://www.openstack.org/software/yoga/ 15:07:49 so a huge thank you to the contributors of the Yoga release. It was a good cycle 15:08:08 the release notes for the projects are available here: 15:08:10 #link https://releases.openstack.org/yoga/?_ga=2.62372202.777024167.1648654764-1433121945.1640635379 15:08:21 it's also a good way to see what's happening around in openstack :) 15:09:01 ++++ certainly hope they get read :) 15:09:13 congratulations everyone! \o/ 15:09:39 \o/ 15:11:13 great! 15:11:16 anyone else has an announcement for today? 15:11:35 yes 15:11:40 i'm very glad to see felipe_rodrigues 15:11:49 and a lil zorilla in tow 15:12:08 yes! good to have you back felipe_rodrigues 15:12:09 thank you :) 15:12:11 congratulations to your significant other and you on becoming parents, felipe_rodrigues 15:12:13 felipe_rodrigues++ 15:12:24 have you reserved the nickname already? 15:12:25 :p 15:12:37 not yet kkkk 15:13:00 there's still time for that felipe_rodrigues :D 15:13:09 never too soon to become a zorilla 15:13:14 I'll think about it kkkk 15:13:17 for sure 15:14:01 :D 15:14:15 it's a girl.. she will be coding soon kkk 15:14:40 hahaha 15:14:43 nice 8) - it's in the dna 15:14:50 kkkkk 15:14:56 hahaha 15:15:34 awesome! 15:15:44 any other announcement? 15:16:41 * carloss is taking silence as a no 15:16:50 Next up: 15:16:55 #topic Zorilla PTG 15:17:01 Zorilla PTG is next week! 15:17:01 :o 15:17:03 time flies 15:17:20 I sent an email yesterday with the proposed schedule and time slots 15:17:30 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027930.html 15:17:44 if you haven't already, please check the slots in the etherpad 15:17:46 #link https://etherpad.opendev.org/p/zorilla-ptg-manila 15:18:36 there has been some changes since yesterday to accommodate some requests 15:19:03 in summary I moved one of the NetAppers topics to wednesday 15:19:17 so nahimsouza[m] fabiooliveira, could please check if it still works for you? 15:20:29 it's ok for me, thanks carlos 15:20:41 yw nahimsouza[m] :D 15:20:43 thanks for checking 15:21:05 so, in the event of the PTG next week, and as we will be quite busy with the meetings 15:21:40 I will be sending an email today cancelling the next week's manila meeting 15:21:47 ++ 15:21:51 (even because it conflicts with the PTG time :)) 15:23:09 carloss on friday 8, we will present the rest talk to cinder ptg it's conflicting with zuul v3 talk in manila. It's possible to change a little bit? 15:24:02 I can move it around andrebeltrami[m], is it okay to use the same day but other slot? 15:24:45 yep, the talk in cinder will be starting 13:00 UTC 15:25:00 looks like cinder has a light schedule on Thuesday 15:25:09 may be we could check with them first 15:25:16 ops 15:25:30 Thursday 15:25:38 oh, cool... i tried to make it earlier in the day because we can accommodate even more timezones 15:26:28 I will check with Rajat 15:26:38 great, thanks sfernand :D 15:27:09 okay, so wdyt about cancelling the meeting after the PTG too? 15:27:13 starting a poll for that :D 15:27:17 #startvote Should we cancel the IRC meeting on Apr 14th? Yes, No, Don't Care Either Way 15:27:17 Begin voting on: Should we cancel the IRC meeting on Apr 14th? Valid vote options are Yes, No, Don, t, Care, Either, Way. 15:27:17 Vote using '#vote OPTION'. Only your last vote counts. 15:29:08 #vote Yes 15:29:16 ^ its a tradition :) 15:29:32 #vote Yes 15:29:50 #vote Don't Care 15:29:50 felipe_rodrigues: Don't Care is not a valid option. Valid options are Yes, No, Don, t, Care, Either, Way. 15:29:57 ah crap :P 15:30:00 #vote Don't Care Either Way 15:30:00 felipe_rodrigues: Don't Care Either Way is not a valid option. Valid options are Yes, No, Don, t, Care, Either, Way. 15:30:05 lol 15:30:12 haha 15:30:13 sorry, you got to care felipe_rodrigues 15:30:16 haha, the bot doesn't like spaces :/ 15:30:17 kkkkkkkkkkk 15:30:22 #vote Yes 15:30:24 #vote Yes 15:30:31 we broke the bot :D 15:30:32 #vote Yes 15:30:36 #vote Yes 15:31:13 going once.. 15:31:28 going twice.. 15:31:49 #endvote 15:31:49 Voted on "Should we cancel the IRC meeting on Apr 14th?" Results are 15:31:49 Yes (6): gouthamr, caiquemello[m], andrebeltrami[m], dviroel, ashrodri, nahimsouza[m] 15:32:07 awesome! thank you... I'll send the email cancelling both meetings today 15:32:54 the last thing on PTG: if you haven't registered yet and intends to participate 15:32:56 please do so: 15:33:21 #link https://openinfra-ptg.eventbrite.com/ 15:34:23 cool, next up 15:34:29 #topic Bug Triage 15:34:35 #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new 15:35:05 vhari couldn't join us today, but she gathered the list of bugs for us :D 15:35:10 vhari++ 15:36:18 first in the list we have 15:36:19 #link https://bugs.launchpad.net/manila/+bug/1966198 15:37:46 sounds something like lack of credentials or not having the permissions to access the given resource 15:38:26 i'll take a look on that 15:38:53 andrebeltrami[m]++ thanks! 15:39:43 this may be related to the ability to configure a single share network for tests 15:40:01 its a very limited use case, but the Dell/EMC CI iirc does this 15:40:22 andrebeltrami[m]: could you confirm by asking for the [share] section of their tempest.conf 15:40:55 if they have a single share network configured, we shouldn't allow modifying it.. since the network is created outside of tempest 15:41:30 yeah 15:42:20 do you mean the pre-configured share network passed in tempest conf, right? 15:43:39 yes 15:44:07 ok, thanks, i'll take a look 15:44:24 thanks andrebeltrami[m] 15:44:25 awesome! thank you folks 15:44:41 next is: 15:44:43 #link https://bugs.launchpad.net/manila/+bug/1966807 15:45:40 this issue was found when we were walking through some code we have 15:45:49 so currently we return a status for security services 15:46:42 but if you check the security service model, you'll realize that there's no such thing https://github.com/openstack/manila/blob/master/manila/db/sqlalchemy/models.py#L900-L915 15:46:54 and then we checked the view: https://github.com/openstack/manila/blob/stable/yoga/manila/api/views/security_service.py#L43-L46 15:47:25 there's an old note there who states this should be removed as soon as there aren't people using it 15:47:42 we think this could be a good opportunity to remove this 15:47:49 ++ so the idea is to remove it in a microversion bump? 15:47:50 so it's a LHF bug 15:48:03 yes, I think microversion bump for this would be appropriate 15:48:17 since we will be removing one property that was returned in the API 15:48:33 maybe a job for lucasmoliveira059 15:48:41 :P 15:48:54 ++ it always bugged me that it stayed in status new and did not move to active or available or something but I never looked in the code what the status was even for 15:49:28 o/ 15:49:33 ++ 15:49:40 awesome! ++ 15:49:59 importance I'd say low 15:50:06 but I might be underestimating it :) 15:50:13 wdyt? 15:51:14 I agree 15:51:43 carthaca: ++ 15:51:43 low is good 15:52:00 No problem. Anything, I'll ask for help 15:52:23 cool lucasmoliveira059, we'll be glad to help you :) 15:52:26 I can hel you lucas no problem 15:52:37 Thank you =) 15:53:09 okay, so I think there's time for another bug 15:53:11 #link https://bugs.launchpad.net/manila/+bug/1824442 15:53:26 it's a revisit, vhari was looking for an update on this 15:53:48 yeah this is an old one; and another LHF 15:54:16 we need a policy around the segmentation_id and network_type fields 15:55:41 cool, any taker? :D 15:56:03 yup, i wanna take this one 15:56:13 awesome! archanaserver++ 15:56:23 archanaserver++ thanks, feel free to reach out in case you have questions 15:56:30 yep fix seems trivial, is high the correct importance? 15:56:38 sure, thank you! 15:57:12 sfernand: i think it was high because it was reported as a security bug; i don't mind us downgrading to "medium" after the subsequent discussion 15:57:13 can't think a way to exploit those infos 15:57:17 yes 15:57:21 ahh ok 15:57:25 got it 15:58:28 yes medium makes more sense to me 15:58:41 medium++ 15:58:45 thanks! 15:58:52 alright 15:58:56 #topic Open Discuss 15:58:59 2 minutes to go :p 15:59:03 1 now 16:00:01 I want to share, that we were hit by https://bugs.launchpad.net/oslo.messaging/+bug/1961402 16:00:20 Be careful when upgrading from victoria to a newer release if you use rabbitmq ;) 16:00:34 oh, thanks carthaca :D 16:00:46 Stuck manila-scheduler service is not a fun thing to observe in production 16:01:09 xD 16:01:15 oh! 16:01:17 thanks carloss 16:01:20 carthaca* 16:01:39 did the solution remove the issue for you? (setting heartbeat_in_pthread? ) 16:01:56 alright, we are 1 minute over... we can continue the discussion in #openstack-manila. thank you all for joining! see you on IRC, and I hope to see you all in the next week's PTG as well! :D 16:01:58 Hopefully - just did the rollout today 16:02:03 #endmeeting