00:01:24 <ekcs> #startmeeting congressteammeeting
00:01:25 <openstack> Meeting started Thu Aug 10 00:01:24 2017 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:01:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
00:01:28 <openstack> The meeting name has been set to 'congressteammeeting'
00:01:51 <ramineni_> ekcs: hi
00:01:58 <ekcs> hi all! hope everyone’s having a good week.
00:01:59 <ekcs> hi ramineni_
00:02:11 <ekcs> topics are here as usual: https://etherpad.openstack.org/p/congress-meeting-topics
00:02:28 <ekcs> please take a couple minutes to read/add/comment =)
00:04:42 <ekcs> ok let’s move along then.
00:04:49 <ekcs> #topic RC1
00:04:57 <ekcs> Pike RC1 is due today.
00:05:05 <ekcs> dashboard RC1 has been released
00:05:09 <ekcs> at this commit: https://github.com/openstack/congress-dashboard/commits/acc972d6563fb2b0a41cfa52f85088cbd9a23783
00:05:33 <ekcs> server RC1 release expected at this patch
00:05:34 <ekcs> https://review.openstack.org/#/c/491954/
00:06:21 <ekcs> several changes targeted for RC1 were aggregated patch because gate instability close to RC1 deadline makes it very hard to merge all changes separately.
00:06:38 <ekcs> Certainly not ideal but it’s what we could do given the situation.
00:07:09 <ekcs> The plan is to release once the patch merges.
00:07:40 <ekcs> Please take a moment to look at the merge to see if you disagree with something.
00:07:47 <ramineni_> ekcs: is doc migration is done completely for all 3 projects
00:08:30 <ramineni_> Once this patch is merged
00:08:33 <ekcs> ramineni_: I believe so.
00:08:47 <ramineni_> Ok
00:08:58 <ekcs> some more work to come in re-enabling pbr autodoc in congress server.
00:09:18 <ekcs> but that’s not totally necessary.
00:09:35 <ramineni_> Ohk ..got it
00:10:09 <ekcs> On the patch I also added a change that skips over loading policy files which are not .yaml or .yml
00:10:32 <ekcs> as well as allowing a file load to fail and be skipped without crashing congress.
00:11:28 <ramineni_> Ya ..great ..
00:11:42 <ekcs> thanks a lot for catching the problem.
00:11:48 <ramineni_> Hopefully the patch should merge now
00:12:28 <ekcs> yea. it’s finally passed check, hopefully gate passes too. otherwise it’ll be a long wait =/
00:12:32 <ramineni_> np :)
00:13:06 <ekcs> took close to 3 hrs for the check jobs to be done on the current patch set.
00:13:50 <ramineni_> Ya .. I noticed too
00:14:28 <ramineni_> Did we get all targeted bugs in rc1 right or anything pending for rc2
00:15:09 <ekcs> I don’t see anything we need to do for RC2. do you see anything?
00:16:13 <ramineni_> Ok .. no ..just confirming
00:16:47 <ekcs> yea I think the hope is RC1 will be final RC. unless we encounter a release blocking bug.
00:17:02 <ekcs> ok anything else on RC1?
00:17:57 <ramineni_> No
00:18:57 <ekcs> alright then
00:19:00 <ekcs> #topic PTG
00:19:54 <ekcs> I’ve started populating the planning etherpad. The idea right now is just to brainstorm and slap down things we may want to discuss.
00:20:02 <ekcs> #link https://etherpad.openstack.org/p/congress-ptg-queens
00:20:37 <ekcs> so everyone feel free to put down your thoughts in the next 1-2 weeks.
00:21:39 <ekcs> another thing about the PTG is solutions for connecting remote attendees.
00:22:07 <ekcs> If you have experience with solutions please suggest them on the planning etherpad =)
00:24:25 <ekcs> any other thoughts about possibly PTG topics, conferencing solutions, or anything else about the PTG?
00:25:29 <ramineni_> I'll check and update the etherpad if any
00:26:02 <ekcs> ok then =)
00:26:29 <ekcs> #topic open discussion
00:27:15 <ekcs> We could talk about gate problems some more, or any other topics, or end early.
00:27:25 <ramineni_> ekcs: I'll be going on vacation next week .. so won't be attending next week meeting
00:27:40 <ekcs> gotcha thanks for the heads up.
00:27:48 <ramineni_> Will catch up week later :)
00:28:02 <ekcs> yups have a great vacay!
00:28:15 <ramineni_> Thanks ...on gate issues
00:28:29 <ramineni_> Did u see timeout issue after that too
00:28:32 <ramineni_> ?
00:29:07 <ekcs> I think so but let me look again.
00:30:47 <ekcs> I saw the replica server not ready issue since fixing the problem of attempting to load RST as yaml.
00:30:48 <ekcs> http://logs.openstack.org/54/491954/3/check/gate-congress-dsvm-api-mysql-ubuntu-xenial/614afbb/testr_results.html.gz
00:31:08 <ekcs> that just happens from time to time. But seemed to me much more frequent as of late.
00:31:21 <ekcs> Now I’m checking the other patches I aggregated (which did not have the RST problem)
00:32:27 <ramineni_> Ohk .. Should we can increase the timeout for ha job .. Or leave it for now
00:32:43 <ramineni_> As its final patch for release
00:34:08 <ekcs> ok right so another patch I’m looking at had the Replica server not ready error too on two of the 4 dsvm tests.
00:34:09 <ekcs> https://review.openstack.org/#/c/483665/
00:34:29 <ekcs> another dsvm just timed out on setup.
00:34:50 <ekcs> and all those things were pretty common past week or more.
00:35:30 <ekcs> and also the one you filed a bug for: https://bugs.launchpad.net/congress/+bug/1703740
00:35:32 <openstack> Launchpad bug 1703740 in congress "gate failing occasionally with TestDseNode functions" [High,New] - Assigned to Anusha (anusha-iiitm)
00:35:39 <ekcs> also seems to have been much more frequent past week or so.
00:35:59 <ramineni_> Oohk .. py 35 job right
00:36:14 <ekcs> I suspect both are related to high load on infra (but I’m not sure).
00:36:35 <ramineni_> Py35 job used to fail before too
00:36:36 <ekcs> Also not sure why high load on infra would cause it and what we can do about it.
00:37:13 <ramineni_> I'll check on both things again ..if I find anything will update you
00:37:15 <ekcs> yes, all these failures are ones we’ve seen, but they’ve all greatly increased in frequency. and also py27 has the same failures.
00:37:52 <ekcs> right now we don’t really know why the failures occur at all, and also not whether/why they are related to higher infra work load.
00:38:26 <ramineni_> Ya ..I'll dig a bit on failures and let you know if I find anything
00:38:38 <ekcs> yea… hopefully we figure it out at some point. we can kind of ignore it most of the time but when it gets bad it’s a real problem.
00:38:48 <ekcs> great thanks lots!
00:39:10 <ekcs> anything else to talk about?
00:39:29 <ramineni_> No ..none from my side
00:39:48 <ekcs> alright then let’s end meeting =)
00:40:09 <ekcs> I’ll be on #congress if someone wants to reach me.
00:40:19 <ramineni_> Have a great week ..bye
00:40:26 <ekcs> you too see you later!
00:40:32 <ekcs> #endmeeting