15:00:08 <carloss> #startmeeting manila
15:00:08 <opendevmeet> Meeting started Thu Oct  5 15:00:08 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:08 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:08 <opendevmeet> The meeting name has been set to 'manila'
15:00:30 <carloss> courtesy ping: felipe_rodrigues vhari gouthamr carthaca msaravan pulluri
15:00:35 <Saikumar> o/
15:00:36 <gouthamr> hello o/
15:00:38 <thiagoalvoravel> o/
15:00:40 <felipe_rodrigues> o/
15:00:48 <kpdev> o/
15:02:05 <vhari> o/
15:02:24 <msaravan> o/
15:03:02 <jayaanand> o/
15:03:56 <gireesh> o/
15:04:00 <carloss> o/ hello everyone
15:04:15 <carloss> lighter meeting agenda today:
15:04:16 <carloss> #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting
15:04:52 <carloss> Bobcat release is official!
15:04:56 <carloss> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-October/035266.html
15:05:05 <carloss> this was announced in the openstack-discuss mailing list
15:05:14 <carloss> thank you everyone for participating and making it happen
15:05:57 <carloss> I'm really happy to see the commitment and things coming together in the Bobcat cycle
15:06:52 <carloss> #link https://www.openstack.org/software/openstack-bobcat
15:07:44 <carloss> this link has a bunch of names of people that had changes merged during the bobcat cycle - OpenStack had around 580 contributors, but I really think it's more than that
15:08:03 <carloss> in that page, you can see one manila special thing:
15:08:10 <carloss> #link https://www.openstack.org/blog/new-in-openstack-bobcat-manila-team-introduces-resource-lock-framework/ (Manila resource locks blog post)
15:08:36 <carloss> the foundation was looking at some features that they could highlight during this cycle
15:09:10 <carloss> resource locks was one of the features picked, and it ended up becoming an amazing blog post that talks about one of the biggest features we got done in this cycle
15:09:27 <carloss> gouthamr: thanks for working in the blog post
15:09:36 <carloss> and also the foundation for the PR :)
15:10:16 <gouthamr> :) it’s motivating to see the call out
15:10:16 <carloss> today, we also had the OpenInfra Live (which ended ~20 minutes ago)
15:10:36 <carloss> many projects featuring their highlights
15:10:43 <carloss> #link https://www.youtube.com/watch?v=q7WDncK3YuM (OpenInfra Live: Bobcat episode)
15:10:52 <carloss> gouthamr: totally!
15:11:15 <carloss> you could see the happiness in my face while I mentioned things we managed to put together in this cycle
15:11:15 <gouthamr> I wanted to echo the impact of the operator feedback loop that you mentioned in this ^
15:12:28 <msaravan> Amazed to see this. Very nice !!
15:13:33 <carloss> ++ - a operator feedback helped us shape many things, so that is proven to be highly important release after release
15:14:40 <carloss> always good to highlight that
15:15:05 <carloss> operator hour for the next PTG is a must have :)
15:16:22 <carloss> two more topics on announcements:
15:17:05 <carloss> last week I roughly mentioned the bug numbers after the bugsquash - I highlighted we had 11 closed bugs
15:17:17 <carloss> vhari: shared some more insights on the bug numbers with me:
15:17:36 <carloss> 11 -> 12 New bugs (might be a new bug report here :))
15:17:46 <carloss> 146 ->130 Open bugs
15:17:55 <vhari> ^^ \o/
15:17:55 <carloss> 46 -> 35 In-progress bugs
15:18:08 <gouthamr> wow, in a week? :)
15:18:11 <vhari> great work everyone
15:18:26 <carloss> gouthamr a week or so
15:18:27 <gouthamr> super nice, indeed! great going team!
15:18:29 <carloss> still impressive
15:18:51 <vhari> gouthamr, no, since last month when data was collected
15:19:00 <carloss> great outcome! thank you everyone for the participation
15:19:43 <vhari> this is the first time we've had such a great drop in open cases
15:21:08 <carloss> ++
15:21:44 <carloss> thanks everyone for pursuing backports as well.  I am planning to cut new releases for the stable branches soon
15:23:50 <carloss> that's all I had for $topic
15:23:57 <carloss> do you have an announcement you'd like to share?
15:25:08 <carloss> taking silence as no...
15:25:18 <carloss> #topic Bug Triage (vhari)
15:25:24 <carloss> #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)
15:25:37 <vhari> ty carloss .. will take it from here
15:26:01 <vhari> got a few bugs left over from previous weeks to triage and some new ones
15:26:03 <vhari> #link https://bugs.launchpad.net/manila/+bug/2035562
15:28:09 <carloss> thanks for the report gouthamr - I believe caiquemello[m] also mentioned this issue was happening on the NetApp CI
15:28:50 <gouthamr> yes, i didn't triage this.. it never happens on the voting jobs
15:28:53 <vhari> carloss, ack link to job is in comment #1
15:28:56 <gouthamr> so its been flying under the radar
15:31:21 <carloss> we'd need to check the issue, but if it's only test related, I believe low prio would fit it, considering it is an intermittent issue, but definitely good to fix this
15:34:44 <vhari> ++ any other considerations?
15:34:44 <carloss> maybe target this to c-2
15:34:58 <carloss> or better, c-1
15:35:13 <carloss> we'll need an assignee for it
15:36:47 <carloss> anyone willing to pick up?
15:37:39 <carloss> 🦗
15:37:52 <gouthamr> msaravan: if you're willing to look, this may be a good one ^ i can help triage this with you..
15:39:24 <msaravan> Sure, will look into that. Thank you Goutham.
15:39:53 <vhari> msaravan++
15:40:00 <vhari> next up   #link https://bugs.launchpad.net/manila/+bug/2035572
15:40:14 <carloss> msaravan++
15:40:20 <vhari> gouthamr, this is assigned to you .. do we need to discuss here?
15:40:34 <vhari> anything to share with the community
15:41:26 <gouthamr> thanks vhari
15:41:40 <gouthamr> not really; this was reported by a customer, and they didn't provide detailed logs..
15:42:23 <gouthamr> (a red hat customer)
15:42:29 <gouthamr> one aspect was my reproduction steps were guesswork; we have a problem during access rule cleanup.. but i'm not sure that fixing it will solve the user's real issue
15:43:02 <gouthamr> so i'm reaching out to them with some debugging steps to get more logs.. i can work on a fix based on their response
15:43:16 <gouthamr> there's a workaround for this issue:
15:43:41 <gouthamr> admins can reset the state of the share, and re-attempt share deletion and it'll work..
15:44:16 <gouthamr> but, my fear with that approach is that it can leave nfs-ganesha in an inconsistent state if the rules that we weren't able to cleanup still exist
15:44:43 <gouthamr> but so far, that workaround has been okay in this user's environment..
15:45:02 <vhari> good to know .. will add the workaround to bug comments
15:45:07 <gouthamr> so ++
15:45:12 <gouthamr> s/so//
15:45:30 <gouthamr> thanks vhari; i think it can be a "medium" and targeted to  "caracal-2"
15:45:51 <vhari> ty gouthamr
15:45:59 <carloss> ++
15:46:16 <vhari> done .. next up #link https://bugs.launchpad.net/manila/+bug/2037285
15:47:30 <carloss> carthaca: thanks for the report
15:47:57 <carloss> NetApp specific bug, an RFE to do an API call more efficiently
15:48:07 <carloss> msaravan: can we have someone from the NetApp team to look at it?
15:48:09 <msaravan> ack. We'll plan that.
15:48:15 <carloss> ack :)
15:49:40 <gouthamr> carthaca suggests a "low" priority
15:49:52 <vhari> ty msaravan
15:50:07 <gouthamr> i agree; an easy enhancement.. so perhaps target to caracal-2, msaravan?
15:50:43 <msaravan> yes gouthamr
15:50:55 <gouthamr> +1
15:51:17 <vhari> ++
15:51:29 <vhari> carloss, is there time for one more bug? :)
15:51:36 <carloss> vhari: yess
15:51:43 <vhari> #link https://bugs.launchpad.net/manila/+bug/2037681
15:51:56 <gireesh> I have one patch that is ready, https://review.opendev.org/c/openstack/manila/+/896759?usp=cherry-pick
15:52:17 <gireesh> if all fine we can merge that
15:52:44 <vhari> ty gireesh .. can we add this to the bug pls?
15:53:24 <carloss> ah, I think it is related to other bug vhari
15:53:36 <carloss> gireesh: thanks for working on the change. I see the backport to 2023.2 as well
15:53:41 <carloss> thanks for working on that
15:53:48 <carloss> gouthamr: can we have your eyes on the fix? :)
15:53:50 <gireesh> thanks carloss
15:53:58 <gouthamr> ack carloss
15:54:02 <carloss> ty
15:54:36 <carloss> on https://bugs.launchpad.net/manila/+bug/2037681
15:54:36 <carloss> this is an issue I spotted in the 2023.1 branch
15:54:53 <carloss> which has the ceph jobs constantly failing in the node setup
15:55:12 <carloss> there's a package missing, and I've opened a bug against devstack-plugin-ceph and also added manila as an impacted project
15:55:31 <carloss> I'd say it's a medium/high prio bug, as the Ceph drivers are failing due to that in the 2023.1 branch
15:55:32 <carloss> thoughts?
15:55:44 <gouthamr> it can be "medium"
15:55:57 <gouthamr> ashrodri: is this something you can help with?
15:56:22 <ashrodri> sure thing
15:57:00 <carloss> ty ashrodri :D
15:57:08 <vhari> ashrodri++
15:57:16 <gouthamr> thanks ashrodri
15:57:31 <vhari> milestone?
15:58:10 <carloss> is c1 feasible?
15:59:25 <ashrodri> i think so yes
15:59:30 <carloss> ack, ty
15:59:44 <vhari> so that's a wrap for bugs .. ty for pitching in  team :)
15:59:52 <carloss> ty vhari
15:59:59 <vhari> yw
16:00:18 <carloss> one last thing: next week's meeting (Oct 12) is a national holiday in Brazil
16:00:23 <carloss> so I'll be off
16:00:36 <carloss> ashrodri could you please run the upstream meeting next week? :)
16:01:08 <carloss> we can continue this on #openstack-manila
16:01:14 <carloss> ty for joining everyone
16:01:19 <carloss> let's wrap up :D
16:01:21 <carloss> #endmeeting