15:00:17 #startmeeting manila 15:00:17 Meeting started Thu May 1 15:00:17 2025 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:17 The meeting name has been set to 'manila' 15:00:24 o/ 15:00:29 o/ 15:00:48 courtesy ping: dviroel vhari carthaca msaravan ashrodri gireesh 15:02:17 alright, likely a super small crowd today.. 15:02:27 thanks for joining, lets get started 15:02:35 #topic Announcements 15:03:10 o/ 15:04:06 all functional testing is currently broken due to a change in setuptools: 15:04:06 #link https://bugs.launchpad.net/manila/+bug/2109645 15:04:45 its unfortunate, but, i guess we didn't pay attention to the deprecation timeline 15:05:10 #link https://discuss.python.org/t/adding-support-for-wsgi-scripts-entrypoint/30905 (Adding support for `wsgi_scripts` entrypoint?) 15:06:13 so we'd have to make some changes in the code to accommodate this 15:06:18 #link https://review.opendev.org/c/openstack/manila/+/948491 15:07:05 since this is a gate blocker, i'm hoping to get some eyes on this asap. This does affect stable/2025.1 as well, and a backport is warranted to get the CI unblocked on that branch 15:07:59 functionally, this may break deployments that rely on the "wsgi_scripts" behavior to create a script in the path to invoke the wsgi server 15:09:06 this is true for folks using apache/mod_wsgi to configure manila-api 15:09:44 most of our testing uses uwsgi, and the devstack plugin changes to use a python module path instead works well 15:09:59 it's in the patch if you'd like to look 15:10:15 haixin gireesh: can i have your eyes on this? 15:10:57 Goutham, I will inform Gireesh. Today is a holiday here in India. 15:11:14 ah! makes sense, thank you Sai 15:11:29 ok. i am busy this week 15:11:35 No worries! 15:11:40 now i remember, it's May Day in most of the world :) 15:12:28 today is also holiday here 15:12:50 Yeahh! 15:12:58 haixin: ah, np.. i don't mind single-core merging this to get the gate unblocked, +/- 1s are welcome too :) 15:13:11 thanks for joining despite the holiday 15:13:20 lets keep rolling and see if we can wrap this up soon 15:13:39 * ashrodri[m] sneaks in late o/ 15:13:49 o/ ashrodri[m] 15:14:13 the other announcement i had was this: 15:14:13 #link https://governance.openstack.org/tc/resolutions/20250317-extend-scope-VMT-cover-all-projects.html 15:15:09 the TC adopted this yesterday and in effect, manila's security bug process will need to align to the OpenStack VMT 15:15:32 i'll be making changes to the bug trackers for the following projects: manila, python-manilaclient and manila-ui 15:16:23 manila-coresec as a group would still exist, but, security bugs will get triaged through the OpenStack Vulnerability Management Team (VMT) rather than being visible to the coresec folks 15:17:28 all security bugs begin as embargoed/private issues.. and today, if you're a bug subscriber that's also a part of the LP group: manila-coresec, you get notified when a new one is created 15:18:08 this will change, the notification will go to the VMT, and they'll in turn pull in manila-coresec as necessary 15:18:56 any questions/concerns wrt this? 15:21:09 i think this is huge and i've always wanted to get manila under the VMT \o/ however, i'll note that we've worked with the VMT on lots of security issues including CVEs because they've been generous to consult on topics 15:21:43 if anything, this establishes a consistency that contributors/operators/users expect 15:21:51 s/a// 15:22:05 that's all i had for announcements today 15:22:10 does anyone else have any? 15:22:32 gouthamr, ack .. to clarify, coresec members will no longer be able to view new bugs ? 15:23:09 vhari: yes, we won't be able to see private security bugs until we're subscribed by the VMT, or the bug has been marked public 15:23:13 and how about existing bugs? will they still be visible to the members? 15:23:45 yes, i don't plan to change settings for existing bugs.. it might mess things up 15:24:01 ack 15:24:29 ty for checking 15:24:43 a note about the schedule: 15:24:49 #link https://releases.openstack.org/flamingo/schedule.html (Flamingo Schedule) 15:25:02 we're two weeks away from Milestone-1 15:25:20 and at the end of this month, we'll have our first bug squash event 15:25:46 these are the two upcoming deadlines we need to pay attention to atm 15:25:53 #topic Review focus 15:25:58 #link https://etherpad.opendev.org/p/manila-flamingo-review-focus 15:26:23 i'd put the gate issue on top of this list for now :) 15:26:26 #link https://review.opendev.org/c/openstack/manila/+/948491 15:26:52 i think the specs have been getting reviews 15:27:15 i've to get back to the share backup restore specification 15:27:20 #link https://review.opendev.org/c/openstack/manila-specs/+/942694 15:27:39 kpdev's been looking as well 15:28:16 ashrodri[m] vhari Sai this could use your eyes too; i don't want to put anymore on your plate haixin, but, if you happen to look :) 15:28:28 can do 15:28:42 will do 15:28:49 Okay Goutham. 15:28:52 thank you! 15:29:59 ack, np 15:30:05 thanks, 15:30:18 vhari: ty for looking at the share configuration change for the tempest plugin 15:30:33 vhari: can i add this one to your list too: 15:30:42 #link https://review.opendev.org/c/openstack/manila-tempest-plugin/+/877917 (Add tests for Share Network Subnet Metadata) 15:30:42 :) sure thing 15:31:44 i went through the list, and see that many things are moving well through reviews, or waiting for the author to respond 15:32:08 does anyone have any review to discuss in particular? 15:32:47 i feel we could have a collab-review on share encryption's design 15:33:16 if kpdev's up for it, we could schedule this for the next week.. 15:34:13 #topic Bug Triage 15:34:21 vhari: the floor is yours 15:34:30 ty gouthamr 15:34:35 #link https://bugs.launchpad.net/manila/+bug/2109376 15:35:17 looking for minor triage to start 15:35:55 ah nice, this was created by one of our interns 15:36:06 cool, how reproducible is this 15:36:07 good amount of detail here 15:36:15 unfortunately, we can't test this with tempest 15:37:25 so i'm unsure what is breaking in the API 15:38:00 the bug claims that the API is unusable, i'd be between medium and high 15:38:14 would need to reproduce this to be sure of the impact though 15:39:11 anyone interestd to own this? 15:39:19 ack, will set this to high for attention 15:39:24 yes 15:39:28 prio can be changed once more data is available 15:39:54 if no one picks this up, we can have carloss look and respond since he's most familiar with this code path 15:42:21 i obfuscated a few things in the bug description 15:42:22 taking silence as no :) will do gouthamr 15:42:33 ty vhari 15:42:51 sure thing .. 15:43:03 gouthamr, ty for the additional notes 15:43:29 next looping back #link https://bugs.launchpad.net/manila/+bug/2108851 per request 15:43:56 nice 15:44:12 ashrodri[m]: is this somethng we can assign to you, and discuss with one of the interns? maria perhaps? 15:44:48 sure, we can discuss it next time we meet 15:45:28 perfect; lets set m-3 as the target.. if we can't get any intern to pick this up, we can pop off the assignee and re-target 15:45:39 ack 15:46:14 ashrodri[m]++ 15:46:29 last bug for the week #link https://bugs.launchpad.net/python-manilaclient/+bug/210899 15:48:17 fix was release .. 15:48:29 someone added to the etherpad .. 15:49:00 is there anything to discuss wrt to the bug or the fix? 15:49:57 is there a missing number? 15:50:13 the bug redirects to a bug on "Launchpad itself" 15:50:54 the link pulls up the bug for me 15:50:55 ah 15:50:59 its: 15:51:03 #link https://bugs.launchpad.net/python-manilaclient/+bug/2108991 15:51:18 fixed it on the etherpad 15:51:34 interesting.. ty gouthamr 15:51:43 deja vu 15:52:05 don't know if we discussed this last week, but i tacked a "low hanging fruit" tag on it 15:52:16 it should be a pretty straight forward fix 15:52:32 I dk who pasted it .. but the bug link worked fine :) 15:52:39 ack 15:52:51 anyone keen on picking this up? 15:56:37 *crickets* :D 15:56:49 okay, vhari lets keep this on the list unassigned 15:57:06 we usually run out of lhf bugs which we farm out to new contributors 15:57:12 k 15:57:46 because there's a workaround - i.e., using the manila CLI, we can mark this medium 15:59:40 anything else for today, vhari ? 16:00:21 no, it's wrap for bugs 16:00:30 thank you 16:00:34 we're at the top of the hour 16:00:42 yw 16:01:16 the last releases of manila, manila-ui and python-manilaclient from the Bobcat (2023.2) branch were made a little while ago 16:01:40 #link https://review.opendev.org/c/openstack/releases/+/948233 16:01:47 We'll be sunsetting this branch today 16:01:58 that's just an informational update :) 16:02:06 and with that, lets close up 16:02:12 thank you for joining! 16:02:15 see you here next week 16:02:21 and in #openstack-manila in the meantime 16:02:26 #endmeeting