15:02:12 <tbarron> #startmeeting manila
15:02:13 <openstack> Meeting started Thu Apr 18 15:02:12 2019 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:18 <openstack> The meeting name has been set to 'manila'
15:02:20 <gouthamr> o/
15:02:22 <lseki> hi
15:02:22 <xyang> hi
15:02:23 <carloss> hey :)
15:02:28 <ganso> hello
15:02:35 <vhariria> hi
15:02:39 <dviroel> o/
15:02:58 <_erlon_> hola!
15:03:01 <tbarron> hi all, let's wait a couple minutes
15:03:09 <jgrosso> hi
15:04:04 <tbarron> manila meeting courtesy ping: gouthamr xyang toabctl bswartz ganso erlon tpsilva vkmc amito jgrosso
15:04:20 <tbarron> sorry for not filtering that list for people already present
15:04:41 <tbarron> Agenda: https://wiki.openstack.org/wiki/Manila/Meetings
15:04:52 <tbarron> OK, let's get started.
15:05:06 <tbarron> Some folks are off for a long weekend.
15:05:13 <tbarron> #topic announcments
15:05:36 <tbarron> Reminder that OpenInfra Summit is April 29-May1
15:05:47 <tbarron> Here are the manila talks:
15:06:00 <tbarron> #link https://www.openstack.org/summit/denver-2019/summit-schedule/global-search?t=Manila
15:06:15 <amito> Hey
15:06:22 <tbarron> If you are at Summit and want to help (even if just with Q&A) for the
15:06:27 <tbarron> Onboarding
15:06:33 <tbarron> or Project Update
15:06:40 <tbarron> please ping me.
15:06:58 <tbarron> We like to demonstrate that we work together, have good participation, etc. so
15:07:06 <tbarron> the more friendly faces the better.
15:07:25 <tbarron> PTG is May 2 - May 4
15:07:39 <tbarron> Thursday through Saturday though manila sessions are
15:07:52 <tbarron> scheduled for Thursday and the first half of Friday.
15:08:05 <tbarron> We already have a rich set of topics at
15:08:19 <tbarron> #link https://etherpad.openstack.org/p/manila-denver-train-ptg-planning
15:08:27 <tbarron> But feel free to add more.
15:08:47 <tbarron> And just a reminder - there's a spot at the top for you to indicate physical
15:08:54 <tbarron> or remote attendance
15:09:22 <tbarron> If there are topics that you especially want to discuss and you are remote
15:09:39 <tbarron> let me know and we'll try to schedule them at a time that will work both for Denver
15:09:46 <tbarron> and for your home time zone.
15:10:12 <tbarron> In the next week I'll be massaging this etherpad into a provisional schedule so
15:10:35 <tbarron> watch openstack-discuss list for notice that the provisional schedule is ready.
15:10:52 <tbarron> The overall PTG schedule, as a reminder, is here:
15:11:05 <tbarron> #link https://www.openstack.org/ptg#tab_schedule
15:11:26 <tbarron> Any other announcements?
15:12:00 <tbarron> #topic stable/* branch release cadence
15:12:15 <tbarron> gouthamr is our stable/* liaison and he volunteered to
15:12:30 <tbarron> start releasing stable branches on a three-week cadence
15:12:46 <tbarron> we can always do special releases if we need to get something critical out
15:12:54 <gouthamr> +1
15:12:55 <tbarron> gouthamr: thanks!
15:13:02 <gouthamr> you're welcome tbarron...
15:13:30 <tbarron> This should help manila users who aren't working from git repos
15:13:47 <tbarron> see bug fixes from their deistros in a more timely and predictable manner.
15:13:59 <tbarron> gouthamr: anything you want to add on this subject?
15:14:05 <gouthamr> if there's any user/deployer visible change in any of these repos: manila, python-manilaclient, manila-ui - it'll get picked up in a 3-week schedule
15:14:43 <gouthamr> so, if we don't propose a new tag for one of these projects on any of the stable branches, it just means that there were no changes
15:14:59 <gouthamr> that should affect anyone outside of our CI and tooling
15:15:28 <tbarron> Any questions about this process?
15:15:39 <tbarron> ok
15:15:41 <gouthamr> also, pike is on EM, and we've cut the final releases...
15:15:55 <tbarron> ah, right, thanks for the reminder
15:16:01 <tbarron> and explain "EM"?
15:16:19 <ganso> extended maintenance
15:16:43 <tbarron> ganso: thanks, I don't have the link handy, but that means
15:16:53 <tbarron> no new releases on that branch
15:17:07 <tbarron> but if we want, we can still backport fixes to it
15:17:17 <gouthamr> #LINK https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases
15:17:24 <tbarron> gouthamr: nice, ty
15:17:31 <gouthamr> "All bugfixes (that meet the criteria described below) are appropriate. No Releases produced, reduced CI commitment."
15:17:50 <gouthamr> please see criteria on the page :)
15:17:57 <tbarron> cool
15:18:16 <tbarron> #topic bugs
15:18:26 <tbarron> jgross welcome back, got anything for us?
15:18:32 <tbarron> jgrosso^
15:18:51 <jgrosso> not alot of new ones great work all keeping up with the new defects
15:19:03 <jgrosso> https://bugs.launchpad.net/manila/+bug/1823750
15:19:04 <openstack> Launchpad bug 1823750 in Manila "WsgiLimiterProxy code looks suspect" [Undecided,Confirmed]
15:19:13 <tbarron> jgrosso: awesome work cleaning up our old backlog!
15:19:18 <jgrosso> confirmed but is anyone assigned ?
15:19:41 <jgrosso> tbarron: your welcome
15:19:43 <tbarron> I recommend this bug for anyone who appreciates eharney's understated humor
15:19:49 <jgrosso> haha
15:19:57 <tbarron> There is a clear logic error.
15:20:08 <tbarron> so he says "suspect"
15:20:36 <tbarron> jgrosso: maybe mark this low hanging fruit
15:20:41 <jgrosso> got it will do
15:20:55 <jgrosso> I have some questions of very old bugs ?
15:20:58 <tbarron> jgrosso: I think someone should just grab it, make the suggested fix, and test to see
15:21:00 <jgrosso> if you all dont mind
15:21:02 <tbarron> if anything breaks.
15:21:11 <jgrosso> sounds good tbarron
15:21:23 <gouthamr> https://github.com/openstack/manila/blob/16bfc82962785409d1373571608508de75122645/manila/api/v1/limits.py#L423
15:21:24 <tbarron> like someone could have written (bad) unit tests that will break b/c of this :)
15:21:30 <gouthamr> low-hanging-fruit ?
15:22:08 <ganso> better call Sherlock to investigate this suspect
15:22:10 <tbarron> gouthamr: I left off the hyphens but suggested that
15:23:05 <gouthamr> ganso: no need, i just did: https://github.com/openstack/manila/commit/f99ef92c9024b1dfc604646c8c0912b963c11523
15:23:05 <tbarron> ganso: haha
15:23:30 * gouthamr all bugs are cinder
15:23:36 <ganso> gouthamr: Detective Goutham
15:24:00 <lseki> lol
15:24:13 <jgrosso> https://bugs.launchpad.net/manila/+bug/1700138
15:24:14 <openstack> Launchpad bug 1700138 in Manila "Manila NetApp driver don't delete share-server when cifs configured manually" [Low,Confirmed]
15:24:23 <jgrosso> old one
15:24:47 <jgrosso> its low and confirmed
15:24:57 <jgrosso> :)
15:25:02 <gouthamr> ah, i seem to have triaged thos
15:25:04 <gouthamr> this*
15:25:33 <gouthamr> i was using the instruction from bswartz: "if it's a vendor bug that doesn't affect the driver starting up, set the priority to low"
15:25:44 <gouthamr> or medium, depending on the situation
15:26:33 <jgrosso> ok so leave it unassgined for now til someone picks it up?
15:26:37 <gouthamr> i think i see what's going on
15:27:39 <gouthamr> OP assigned a security service "manually" - i.e, they began with a NFS share server, and configured cifs directly on the backend
15:28:15 <gouthamr> manila doesn't know about this security service, and the driver fails to perform cleanup
15:28:33 <jgrosso> so easy fix?
15:28:39 <jgrosso> right  :)
15:28:40 <gouthamr> seems legit to me to call it a feature and not a bug :)
15:28:59 <jgrosso> ok
15:29:06 <jgrosso> will do that
15:29:08 <gouthamr> i.e, if someone configures something on the backend, manila fails to delete it - and that sounds appropriate
15:29:19 <gouthamr> no wait, please let folks from netapp do that :)
15:29:51 <gouthamr> lseki carloss: can one of you take a look ^
15:29:57 <lseki> I will
15:30:03 <tbarron> jgrosso: yeah we need to move to having separate INBOX queues, so that if it
15:30:22 <tbarron> it is a back end issue it goes to the backlog for that back end
15:30:29 <lseki> gouthamr: will reproduce it manually and check the behavior you described
15:30:39 <jgrosso> tbarron: ok got it
15:31:05 <tbarron> jgrosso: not sure how we instrument that yet, but I think it's a goal
15:31:13 <gouthamr> thank you lseki
15:31:23 <tbarron> lseki: yeah, thanks!
15:31:27 <jgrosso> ok wil look it that
15:31:34 <jgrosso> thanks lseki
15:31:40 <lseki> gouthamr: thank you for the clue :-)
15:31:57 <jgrosso> https://bugs.launchpad.net/manila/+bug/1706092
15:31:58 <openstack> Launchpad bug 1706092 in Manila "Deadlock occurs when share server create is called but fails" [Low,Confirmed]
15:32:09 <jgrosso> another low confirmed
15:32:56 <ganso> I believe that is no longer true
15:33:02 <gouthamr> "To work around the issue, presently, one has to enter the database and change the state of the share server from creating to a final state."
15:33:14 <gouthamr> yes
15:33:29 <gouthamr> there's a share server reset-state since Stein
15:33:36 <jgrosso> ok I will close it as not a bug
15:33:46 <tbarron> with that remark
15:33:53 <gouthamr> although, i'm not sure what the deadlock here is
15:34:07 <ganso> not only that, during my implementation of Manage-Unmanage I had several cases of share server creation failing, and never got stuck in "creating", always "error"
15:34:39 <ganso> so I think that problem has already been fixed by another bugfix
15:34:46 <gouthamr> ack
15:34:46 <tbarron> jgrosso: probably ask them to open a new bug if they can repro and provide logs
15:35:00 <jgrosso> will do
15:35:10 <jgrosso> last one
15:35:13 <jgrosso> https://bugs.launchpad.net/manila/+bug/1488356
15:35:14 <openstack> Launchpad bug 1488356 in Manila "glusterFS_native_driver: share size may be misleading" [Medium,In progress]
15:35:18 <tbarron> but say that we think the issue has been fixed and in any case they can now reset, etc.
15:35:32 <jgrosso> tbarron: ok thanks !
15:35:44 <tbarron> jgrosso: won't fix b/c we don't have anyone supporting the gluster driver ???
15:35:58 <jgrosso> ahh that is correct
15:36:01 <jgrosso> my bad tbarron
15:36:09 <jgrosso> totally forgot
15:36:21 <tbarron> well it's good to bring this out into public
15:36:28 <tbarron> and into our meeting minutes
15:36:41 <tbarron> there are people using gluster with manila successfully today
15:36:55 <tbarron> they are just making changes to their own forks of manila
15:37:01 <jgrosso> ahh ok
15:37:03 <tbarron> we need contributors for gluster
15:37:28 <jgrosso> well that is all I had for today
15:37:36 <jgrosso> thanks all
15:37:45 <tbarron> jgrosso: thank you!!
15:37:52 <tbarron> #topic open discussion
15:38:01 <tbarron> Anyone have anything else for today?
15:38:38 <tbarron> OK, for those of you with a holdiday weekend, enjoy!
15:38:48 <tbarron> See you in #openstack-manila
15:38:51 <tbarron> Thanks everyon!
15:38:55 <tbarron> everyone
15:39:01 <tbarron> #endmeeting