15:00:40 <bswartz> #startmeeting manila
15:00:40 <openstack> Meeting started Thu Nov  9 15:00:40 2017 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:41 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:44 <openstack> The meeting name has been set to 'manila'
15:00:46 <amito-infinidat> o/
15:00:49 <bswartz> hello all!
15:01:00 <zhongjun> hi
15:01:05 <tbarron> hi
15:01:20 <bswartz> courtesy ping: cknight vponomaryov gouthamr markstur xyang ganso toabctl
15:01:45 * bswartz suspects attendance will be low on account of the summit
15:01:58 <bswartz> also, I bet a lot of people forgot about the time change
15:02:01 <tbarron> gouthamr vkmc ganso are likely summit / traveling
15:02:35 <bswartz> well we've got 4 of us -- that doesn't really count as a quorum
15:02:40 <bswartz> anything we need to discuss?
15:03:23 <bswartz> if not, we can just gavel this session closed and reconvene next week
15:03:52 <bswartz> tbarron: you're not in the stable channel, but I posted a link to your backport there, asking for opinions
15:04:00 <bswartz> no response yet
15:04:07 <tbarron> bswartz: is it #openstack-stable ?
15:04:11 <bswartz> y
15:04:14 <tbarron> thanks
15:04:17 <zhongjun> I saw dustins have a topic about over new bugs?
15:04:29 <bswartz> zhongjun: that's a weekly topic from now on
15:04:47 <tbarron> dustin is in training today
15:04:51 <bswartz> but even our bug czar forgot about this meeting
15:04:57 <bswartz> ^ or he's in training ;-)
15:05:11 <tbarron> we have a pretty bad bug maybe though, sec
15:05:14 <zhongjun> :)
15:05:46 <bswartz> #topic Let's go over new bugs
15:05:51 <bswartz> #link https://etherpad.openstack.org/p/manila-bug-triage-pad
15:06:04 <bswartz> tbarron: ^ one of these?
15:06:16 * tbarron looks
15:06:31 <tbarron> no, sec
15:06:49 <tbarron> https://bugs.launchpad.net/bugs/1730529
15:06:50 <openstack> Launchpad bug 1730529 in Manila "Running Pike manila-api directly with SSL does not speak SSL" [Undecided,New]
15:07:19 <bswartz> ouch
15:07:28 <bswartz> that does seems serious
15:07:31 <bswartz> how is that possible?
15:07:37 <bswartz> do we not test this kind of thing?
15:08:14 <zhongjun> Do we still have this problem now?
15:08:29 <tbarron> I've not verified it, may only happen with ways of running the API ?
15:08:55 <tbarron> zhongjun: the report says Pike
15:09:10 <bswartz> okay so the theory is that if you run under apache it's fine?
15:09:20 <tbarron> bswartz: seems like it
15:09:26 <bswartz> it's just the python wsgi container that has issues?
15:09:35 <bswartz> I wonder how far back that goes
15:09:48 <tbarron> s/container/wrapper/ :-)
15:09:53 <bswartz> if it's always been thus, or if it was broken in the wsgi move
15:10:00 <tbarron> maybe also when it's in a container too
15:10:20 <tbarron> I agree that that's a good question.
15:10:44 <tbarron> Anyways, I'm probably not going to have time in the next couple weeks to look at this one.
15:10:57 <bswartz> if it's only broken recently, and not under apache, then I feel it's less urgent
15:11:25 <tbarron> So if anyone knows about wsgi and ssl it would be great to confirm the bug and it's scope
15:11:53 <tbarron> s/it's/its/
15:11:53 <bswartz> also, I'd like to know how we obtain test coverage over this use case
15:12:08 <bswartz> if it's not tested, we can assume it will break again after we fix it
15:12:58 <bswartz> tbarron: probably better to bring this up again when we have more people
15:13:03 <tbarron> yeah, I guess we need functional test framework ?
15:13:06 <bswartz> I added it to the dustins etherppad
15:13:07 <tbarron> bswartz: +1
15:13:26 <bswartz> since we don't have quorum, I'll go ahead and end the meeting
15:13:36 <tbarron> hmm, I did too :-)
15:13:50 <bswartz> we should have everyone back next week
15:14:11 <bswartz> tbarron: Oh I see
15:14:33 <bswartz> Fixed
15:14:34 <tbarron> all good
15:14:38 <bswartz> thanks all
15:14:42 <bswartz> #endmeeting