15:00:07 #startmeeting manila 15:00:07 Meeting started Thu Jan 25 15:00:07 2024 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:07 The meeting name has been set to 'manila' 15:00:27 courtesy ping: dviroel vhari gouthamr carthaca msaravan pulluri 15:00:33 o/ 15:00:41 o/ 15:01:18 o/ 15:01:28 o/ 15:02:14 hi 15:02:22 o/ 15:03:29 o/ hello everyone! welcome :) 15:04:12 o/ 15:04:58 today's meeting agenda: 15:05:00 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:05:45 let's start with our announcements 15:05:47 #topic Announcements 15:05:53 Schedule and Deadlines: 15:05:59 #link https://releases.openstack.org/caracal/schedule.html 15:06:36 so, we can already see the manila milestones in the schedule :) 15:07:03 next week will be our feature proposal freeze 15:07:24 which means: all new Manila features must be proposed and substantially completed, with unit, functional and integration tests by the end of the week 15:08:28 so please submit your features to gerrit 15:08:35 and if you need exceptions, please reach us out 15:10:09 light announcements list for today 15:10:16 do you have something you'd like to share with us today? 15:11:55 taking silence as no... 15:12:01 #topic Review Focus 15:12:07 #link https://etherpad.opendev.org/p/manila-caracal-review-focus (Review Focus etherpad) 15:13:32 gouthamr: thank you for reviewing the specs as well 15:13:39 #link https://review.opendev.org/c/openstack/manila-specs/+/898999 (Share encryption spec) 15:13:47 that's the only spec left and comments have been there for a while 15:14:21 I intend to ping kpdev and check if he plans to post updates soon 15:15:25 ++ 15:15:46 we are 2 weeks past spec freeze, so we should be merging this asap 15:16:33 also, I have proposed some stable branches releases 15:16:36 #link https://review.opendev.org/q/owner:ces.eduardo98@gmail.com+project:openstack/releases+status:open 15:17:03 thank you everyone that reviewed and proposed backports... there's a lot of content shipping in those releases :) 15:17:27 there are a couple more changes that I want to land in the python-manilaclient repo stable branches 15:17:30 but we'll get there 15:17:42 do you have a change you'd like to bring up today? 15:20:21 * carloss takes silence as no 15:20:31 #topic Bug Triage (vhari) 15:20:37 #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) 15:20:57 ty carloss 15:21:11 #link https://bugs.launchpad.net/manila/+bug/2049632 15:21:43 the bug was initially triaged 15:22:01 and made some comments 15:22:29 looping back in case we need anything else related to this issue 15:23:04 I think we didn't set the priority for this bug 15:23:08 I wonder if vsadmin was ever expected to work 15:23:48 ack we could finish setting prio 15:24:07 doesn’t netapp maintain a list of “security login role” command directories that the driver is tested with? 15:26:12 https://netapp-openstack-dev.github.io/openstack-docs/wallaby/manila/configuration/ontap_configuration/section_ontap-config.html#account-permission-considerations 15:30:03 we need to check goutham... checking the code.. should be there 15:31:21 Ty msaravan ; this issue has come up before… I see a common theme with other backends too… in a data center, sometimes, the storage administrator isn’t the same as the openstack administrator 15:32:07 and the storage system’s tenancy model is relied upon where openstack is a tenant with minimal privileges 15:32:43 this is usually fine for Manila’s dhss=false drivers and cinder drivers… 15:33:02 yes; 15:33:41 it’s possible this bug is some regression; it’d be nice to test this in CI… you might find some API was introduced without privilege checks 15:34:47 ty gouthamr and msaravan for additional triage data points 15:35:29 do we have enough info to set prio? 15:37:11 if not, pls consider it for later 15:37:26 jumping to the next bug 15:37:27 #link https://bugs.launchpad.net/manila/+bug/2050010 15:37:29 I think it's okay leaving it to when we can confirm the bug 15:37:42 carloss++ 15:38:27 ah, I think this is a follow-up to the last week's CephFS bug report 15:39:08 gouthamr: thank you for splitting the issue into two separate things 15:40:00 yw , it’s been triaged, I’m gathering data downstream and will work on a fix 15:40:18 great ty gouthamr 15:40:25 gouthamr++ 15:40:53 next bug #link https://bugs.launchpad.net/manila/+bug/2050101 15:44:26 hmmm; I agree, this isn’t expected behavior… you’d need another hint besides “snapshot_id” to differentiate snapshot cloning vs other operations like extend 15:44:56 ++ 15:47:10 and good catch 15:47:40 I think low-medium prio for this 15:47:54 ack, anyone wants to take a stab at this bug? 15:49:05 carloss, crickets say no? :) 15:49:07 if we don't have volunteers, we can ask carthaca if they have someone in mind to work on it 15:49:26 good plan .. will do 15:49:35 last bug of the day 15:49:36 #link https://bugs.launchpad.net/manila/+bug/1943035 15:49:50 revisit from 1/11 15:50:07 looking if the recheck results look different 15:51:31 yeah, there's the issue with the glusterfs jobs failing to install gluster :/ 15:52:12 the failures on LVM and generic seem to be related to a possible timeout 15:52:21 some operations took a while in scenario tests 15:52:27 perhaps worth another rechec 15:52:31 ack, needs further triage manila-tempest-plugin-lvm 15:53:08 ack, will keep monitoring the recheck results or triage the failures 15:53:11 carloss++ 15:53:13 ty vhari 15:53:28 so that's wrap for bugs 15:53:36 vhari: ty :D 15:53:38 ty everyone for pitching is as usual 15:53:50 yw carloss :) 15:53:53 ty for working on the bugs list and sharing with us 15:53:56 #topic Open Discussion 15:55:55 * carloss crickets... 15:56:05 alright, let's wrap up 15:56:14 thank you for attending and participating! 15:56:18 see you on #openstack-manila 15:56:24 #endmeeting