15:00:34 <tbarron> #startmeeting manila
15:00:34 <openstack> Meeting started Thu May  3 15:00:34 2018 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:35 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:38 <openstack> The meeting name has been set to 'manila'
15:00:47 <tbarron> manila courtesy ping:  gouthamr zhongjun xyang markstur vponomaryov cknight toabctl bswartz ganso
15:00:49 <zhongjun_> Hi
15:00:51 <dustins> \o
15:00:57 <markstur> hi
15:01:11 <ganso> hello
15:01:20 <vkmc> o/
15:01:31 <tbarron> Hi all!
15:01:42 <bswartz> .o/
15:01:43 <vgreen> hi
15:01:54 <tbarron> #topic Announcements
15:02:06 <tbarron> TC elections completed
15:02:17 <tbarron> #link  http://lists.openstack.org/pipermail/openstack-dev/2018-May/130052.html
15:02:27 <tbarron> Congratulations to our new TC!!
15:02:53 <tbarron> PTG earlybird registration has been extended to 5/18
15:03:04 <tbarron> #link http://lists.openstack.org/pipermail/openstack-dev/2018-May/130082.html
15:03:11 <gouthamr> o/
15:03:19 <tbarron> You save $200 if you register before that date.
15:03:38 <tbarron> Manila spec process has completed!
15:03:56 <tbarron> I know that I dragged this out a bit this time :)
15:04:12 <tbarron> Thanks to all the reviewers and to Jun for her patience.
15:04:31 <tbarron> Any other announcements?
15:04:50 <zhongjun_> Thanks to all the reviewers
15:05:01 <tbarron> OK, we have a short agenda today.
15:05:20 <tbarron> #link  https://wiki.openstack.org/w/index.php?title=Manila/Meetings&section=2
15:05:28 <tbarron> #topic Drivers
15:05:33 <xyang> Hi
15:05:42 <tbarron> #link  https://etherpad.openstack.org/p/manila-rocky-drivers
15:05:46 <tbarron> hi xyang :)
15:06:15 <tbarron> As you see, we have two new drivers proposed for Rocky.
15:07:01 <tbarron> And we have an M2 deadline for submission, where that is defined as being
15:07:14 <tbarron> substantially complete, with unit tests, and passing CI.
15:07:48 <tbarron> I'll encourage folks to add your names to the above etherpad and add your review comments.
15:08:19 <tbarron> The Inspur driver appears to be passing CI now though I haven't audited the tests that it is running yet.
15:08:48 <tbarron> Jun has reviewed but we need some more eyes.
15:08:57 <tbarron> It seems to be making good progress.
15:09:42 <tbarron> I don't see the Pure folks online today ...
15:10:03 <tbarron> Pure driver has good review comments, some still not answered.
15:10:11 <tbarron> No CI yet ...
15:10:50 <tbarron> There's still time but we don't want to get into a last-minute-jam.
15:11:08 <tbarron> Anything else on this topic today?
15:11:34 <tbarron> ok, moving on
15:11:44 <tbarron> #topic New Bugs
15:11:54 <tbarron> Dustin, what do you have for us today?
15:12:05 <amito> o/
15:12:07 <tbarron> #link https://etherpad.openstack.org/p/manila-bug-triage-pad
15:12:08 <dustins> Let's start with some follow up
15:12:17 <tbarron> Amit!
15:12:26 <amito> :D
15:12:43 <dustins> #link https://bugs.launchpad.net/manila/+bug/1762900
15:12:44 <openstack> Launchpad bug 1762900 in Manila "tearDownClass manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest Failed" [Undecided,New]
15:13:57 <dustins> This is the bug that captures our issues with leaving artifacts behind after a Tempest run
15:14:02 <dustins> Especially with failed tests
15:15:10 <tbarron> dustins: so this bug's status is New
15:15:29 <bswartz> Leaving good artifacts or bad artifacts?
15:15:33 <tbarron> dustins: but you seem to be saying that you've seen the issue too, right?
15:16:18 <dustins> Indeed I have
15:16:25 <tbarron> bswartz: good artifacts would help us debug failures I take it?
15:16:48 <bswartz> Usually the word "artifact" has that positive cononnotati
15:16:50 <tbarron> this bug seems to be saying lack of cleanup is causing a test failure, am I reading it correctly?
15:16:55 <bswartz> connotation even
15:17:11 <bswartz> In this case I think we're talking about garbage left behind
15:17:16 <tbarron> bswartz: right
15:17:22 <dustins> Best term I could come up with to refer to the stuff left behind
15:17:42 <tbarron> dustins: so do you want to change its state to confirmed for a start?
15:17:50 <dustins> It likely stems from not performing cleanup when a test fails
15:17:51 <dustins> Sure
15:18:08 <gouthamr> am just waking up, but i think i started looking at this bug last week, and i wasn't able to reproduce it, one of the tests in that suite creates a share, which means a share server will be created
15:18:10 <tbarron> dustins: I think we have this same issue reported downstream as a BZ
15:18:49 <dustins> Wouldn't surprise me
15:19:52 <tbarron> dustins: so you saw *this* garbage?
15:20:12 <tbarron> and *this* test failure?
15:20:17 <dustins> Maybe not exactly this, but I've seen tempest leave a bunch of things behind
15:20:35 <tbarron> ah
15:20:55 <dustins> On one setup that I have now there are several neutron networks, subnets, routers, ports, etc all lying around after some failed tests
15:21:16 <tbarron> yeah we had a bug about that last week and confirmed it
15:22:32 <tbarron> #link https://bugzilla.redhat.com/show_bug.cgi?id=1573786
15:22:54 <openstack> bugzilla.redhat.com bug 1573786 in openstack-manila "tearDownClass manila_tempest_tests.tests.api.test_share_networks_negative.ShareNetworksNegativeTest Failed" [High,New] - Assigned to tbarron
15:22:54 <tbarron> is this the same issue?
15:22:54 <tbarron> both newton/osp10
15:23:07 <dustins> Yes, even created by the same person
15:23:10 <tbarron> I'm just the default assignee
15:23:43 <tbarron> ok, I'll take it upstream then too, at least till I give it to dustin or gouthamr :)
15:24:05 <dustins> Sounds like a plan
15:24:32 <gouthamr> +1 i can share what i tried tbarron, however, i think i stopped at trying to deploy the container driver to reproduce this issue
15:26:17 <tbarron> dustins: anything else on this one for now?
15:26:24 <dustins> No
15:27:26 <dustins> #link https://bugs.launchpad.net/manila/+bug/1753630
15:27:28 <openstack> Launchpad bug 1753630 in Manila "The net, router, and subnet created in the Manila tempest test process are not cleared" [Medium,Confirmed]
15:27:59 <dustins> Similar issue, though this bug report seems to imply that this occurs regardless of test run status
15:28:52 <tbarron> This is the one we marked confirmed last week I think.
15:29:13 <dustins> Right, just following up on it and the previous
15:29:33 <tbarron> and Shuali Wang has noted that there are other bugs for the same thing and
15:29:38 <gouthamr> there's a response linking to recent fixes: https://review.openstack.org/#/c/551206/ https://review.openstack.org/#/c/552506/
15:29:47 <tbarron> that ^^
15:30:22 <tbarron> So this issue is reportedly fixed in master, no?
15:31:00 <dustins> Looks that way, I guess
15:31:29 <gouthamr> yep, and manila-tempest-plugin is branchless, perhaps they can install the latest manila-tempest-plugin and report if it still exists
15:32:05 <tbarron> I'll follow up in this LP bug along those lines then.
15:32:20 <dustins> Sounds good
15:33:22 <dustins> Anything else on this one?
15:34:22 <dustins> #link https://bugs.launchpad.net/manila/+bug/1747721
15:34:24 <openstack> Launchpad bug 1747721 in python-openstackclient "openstack client not assagning floating ip to instance" [Undecided,Confirmed]
15:35:42 <tbarron> dustins: rishabh committed a fix/workaround for this so it no longer affects manila
15:36:26 <tbarron> but we leave the bug open for python-openstackclient to fix on their side
15:36:57 <dustins> Got it, I'll keep an eye on this one and close it when the osc fixes that issue
15:37:17 <tbarron> I think I'll set the manila bug status on this one to Fix committed
15:37:34 <dustins> Sounds good to me
15:38:09 <dustins> Anything else on this one?
15:38:51 <dustins> #link https://bugs.launchpad.net/manila/+bug/1760644
15:38:52 <openstack> Launchpad bug 1760644 in Manila "API refference contains mistakes" [Undecided,New]
15:39:07 <dustins> Looks like our API reference has some flaws
15:39:17 <bswartz> Doc bugs :-/
15:39:24 <gouthamr> heh, mistake in the bug
15:39:32 <bswartz> Those are low hanging fruit to fix at least
15:39:59 <tbarron> Is there any chance that he's looking at older versions of the api-ref?  We've had a fair number of fixes in the last couple releases.
15:40:24 <tbarron> gouthamr: ?
15:40:25 <gouthamr> tbarron: teh api ref is always current
15:40:34 <dustins> The link that they specified goes to the current version
15:40:38 <tbarron> kk
15:40:44 <tbarron> but what is the mistake in the bug?
15:41:00 <gouthamr> i was kidding, "refference"
15:41:29 <tbarron> ok, do we confirm this one then?
15:41:47 <gouthamr> +1
15:41:57 <tbarron> Anyone want to grab it?
15:42:15 <dustins> I would, but I can't commit to working on it for a couple of months
15:42:50 <gouthamr> but the solution seems to be to audit the API and the reference and fix everything that's incorrect. perhaps we can break down the effort?
15:42:58 <tbarron> We can leave the bug open and post incremental fixes.
15:43:13 <tbarron> start with the first bullet
15:43:18 <dustins> gouthamr: +1
15:43:37 <bswartz> Any chance we can get the submitter to also fix his own bug?
15:43:48 <bswartz> He seems like a developer if he's writing his own client
15:43:51 <tbarron> bswartz: good point
15:44:03 <tbarron> I'll ask him if he's willing to submit a patch.
15:45:02 <dustins> anything else on that one?
15:45:13 <tbarron> Dustin, would you put this in the backlog to check on again in a few weeks?
15:46:18 <dustins> of course
15:46:47 <dustins> #link https://bugs.launchpad.net/manila/+bug/1765420
15:46:48 <openstack> Launchpad bug 1765420 in Manila "NetApp Driver with Non-Cluster-Scoped Role and User Cannot Delete Shares" [Undecided,New]
15:47:01 <gouthamr> yay, didn't see this one come through
15:47:37 <tbarron> This one has an unreliable reporter :)
15:47:55 <dustins> Guy's kind of a hack, I hear
15:47:57 <dustins> :)
15:48:12 <gouthamr> fixed i think, ganso bswartz feel free to take over: https://review.openstack.org/#/c/559860/
15:48:38 <gouthamr> the -1 is because i write beautiful release notes that reno doesn't seem to get
15:48:50 <bswartz> Intereting bug
15:48:51 <tbarron> commit msg needs update with this LP bug # so that they link :)
15:48:58 <ganso> gouthamr: thanks, we'll take a look and validate it
15:49:05 <bswartz> ganso: have you looked at this?
15:49:12 <ganso> bswartz: no, I haven't yet
15:49:24 <bswartz> Thanks for the patch gouthamr
15:49:30 <tbarron> is there the same issue for cinder?
15:49:57 * tbarron wanders off the path
15:49:58 <dustins> ...can I not change the status of bugs that I opened?
15:50:03 * tbarron wanders back
15:50:54 <tbarron> dustins: maybe we need to add you to some launchpad group
15:51:16 <dustins> I thought I was in the super_bug_awesome group already
15:51:20 <gouthamr> you're on this one: https://launchpad.net/~manila-bug-supervisors
15:51:29 <bswartz> Only the bug czars can change the status
15:51:59 <dustins> I've been changing the bugs in the list just now, this one won't let me (with timeouts)
15:52:10 <dustins> Either I can't or LP is about to break :)
15:52:14 <bswartz> dusins: if it's in manila, you should be able to
15:52:18 <dustins> It is
15:52:22 <gouthamr> yeah dustins that happened to me too
15:52:23 <bswartz> Other projects maybe not
15:52:29 <gouthamr> something is up with LP this morning
15:52:35 <dustins> Good, not just me then
15:52:47 <dustins> We done broke it, whoops
15:52:49 <bswartz> It would not be the first time that LP has had problems
15:52:50 <tbarron> who wants this bug assigned to him
15:52:53 <tbarron> ?
15:53:45 <tbarron> ok, we'll catch up on this one when LP starts behaving
15:53:46 <gouthamr> "Timeout error, please try again in a few minutes." LP, you broke
15:53:54 <tbarron> any other bugs today?
15:53:55 * bswartz ducks
15:54:23 <dustins> None today, we'll have a new crop next week
15:54:27 <tbarron> #topic Open Discussion
15:54:52 <tbarron> vkmc: thanks for the noble battle with py3 and manila-ui
15:54:59 <gouthamr> thanks for the pointer on reno dhellmann, #TIL
15:55:06 <tbarron> vkmc: seems like you are making progress ...
15:55:21 <dhellmann> gouthamr : np, I'm glad to be of service
15:56:07 <vkmc_> \o/
15:56:17 <tbarron> manila-ui is in the doghouse with swift relative to py3 goals
15:56:46 <vkmc_> as mentioned... there is more work to do, but latest patch should make us py3 compatible
15:56:48 <tbarron> The rest of manila is in good shape I think.
15:57:17 <vkmc_> manila-ui deserves some love
15:57:24 <tbarron> or kicks
15:57:31 <ganso> tbarron: lol
15:57:36 <vkmc_> hahaha
15:58:00 <tbarron> Seriously though if you know people who want to work on UI stuff we should encourage them to come over here.
15:58:22 <tbarron> We can't make vkmc_ maintain this thing by herself forever.
15:58:51 <gouthamr> we can't?
15:59:04 <tbarron> :)
15:59:07 <vkmc_> haha
15:59:15 <tbarron> OK, anything else today?
15:59:43 <tbarron> Thanks everyone, see you in #openstack-manila!
15:59:48 <tbarron> #endmeeting