[00:10] <Ursinha> OOPS-1362EA10197
[16:00] <matsubara> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is matsubara.
[16:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:00] <matsubara> Welcome to this week's Launchpad Production Meeting. For the next 45 minutes or so, we'll be coordinating the resolution of specific Launchpad bugs and issues.
[16:00] <matsubara> [TOPIC] Roll Call
[16:00] <MootBot> New Topic:  Roll Call
[16:00] <bigjools> me
[16:00] <matsubara> Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us!
[16:00] <rockstar> ni!
[16:00] <bac> me
[16:00] <stub> me
[16:00] <gary_poster> me
[16:00] <EdwinGrubbs> me, sitting in for sinzui
[16:01] <matsubara> Ursinha, Chex: hi
[16:01] <Ursinha> me
[16:01]  * Chex is here
[16:01] <matsubara> danilos, are you joining us?
[16:01] <Ursinha> matsubara, flaky internet
[16:01] <matsubara> allenap, hi
[16:01] <danilos> me
[16:01] <danilos> matsubara: yes
[16:01] <allenap> me
[16:02] <matsubara> danilos, shall I make you the default translations person for the LP prod meeting?
[16:02] <mbarnett> me?
[16:02] <gary_poster> you!
[16:02] <matsubara> hi mbarnett
[16:02] <matsubara> welcome :-)
[16:02] <mbarnett>  :)
[16:02] <matsubara> ok, everyone is here
[16:02] <matsubara> [TOPIC] Agenda
[16:02] <MootBot> New Topic:  Agenda
[16:02] <matsubara>  * Actions from last meeting
[16:02] <matsubara>  * Oops report & Critical Bugs & Broken scripts
[16:02] <matsubara>  * Operations report (mthaddon/Chex/spm/mbarnett)
[16:02] <matsubara>  * DBA report (stub)
[16:02] <matsubara>  * Proposed items
[16:02] <matsubara> [TOPIC] * Actions from last meeting
[16:02] <MootBot> New Topic:  * Actions from last meeting
[16:03] <matsubara>     * barry to continue debug on bug 403606 after finishing 3.0 UI stuff
[16:03] <matsubara>     * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it
[16:03] <danilos> matsubara: yes
[16:03] <matsubara> I still suck, haven't done that one.
[16:03] <matsubara> [action]  * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it
[16:03] <MootBot> ACTION received:   * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it
[16:04] <matsubara> EdwinGrubbs, I'll keep the action item for barry in the list since 3.0 crazyness is not over yet :-)
[16:04] <matsubara> [action] * barry to continue debug on bug 403606 after finishing 3.0 UI stuff
[16:04] <MootBot> ACTION received:  * barry to continue debug on bug 403606 after finishing 3.0 UI stuff
[16:04] <matsubara> [action] matsubara to update translations qa contact on meeting agenda page
[16:04] <MootBot> ACTION received:  matsubara to update translations qa contact on meeting agenda page
[16:05] <matsubara> [TOPIC] * Oops report & Critical Bugs & Broken scripts
[16:05] <MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
[16:05] <matsubara> Ursinha, go ahead
[16:06] <matsubara> hmm Ursinha was having connectivity problems before the meeting
[16:07] <danilos> ok, so, let me take over for what I can
[16:08] <danilos> bac is doing a great job with managing release of 3.0 and any critical bugs
[16:08] <danilos> what we've seen is already listed on https://dev.launchpad.net/CurrentRolloutBlockers
[16:08] <bac> thanks.  getting lots of good help.
[16:08] <danilos> we have noticed increased timeouts on production DBs, due to postgres restart
[16:09] <danilos> for more details, Ursinha will have to fill us in
[16:09] <matsubara> we had a bunch of disconnection errors as well
[16:09] <danilos> matsubara: around the time of rollout or? (because that'd be expected if so)
[16:09] <matsubara> danilos, not sure, Ursinha just sms'ed me and asked me to bring it up
[16:10] <matsubara> but I take the increase on those are due to the rollout, yes
[16:11] <matsubara> so, Ursinha and I will keep looking for the new oopses that happened since the rollout
[16:11] <danilos> matsubara: I suggest we get more detailed input from Ursula when she shows up back online, but go on with the meeting for now; for what we know, all critical issues are being taken care of, and we are hoping for a re-rollout tonight
[16:11] <matsubara> and let each affected team about them and add them to the CRB page
[16:11] <danilos> matsubara: thanks matsubara, that'd be great
[16:11] <matsubara> we had some script failures as well related to the rollout
[16:11] <matsubara> and another one unrelated which bigjools already replied to
[16:12] <matsubara> (which is the packagediffs thing)
[16:12] <matsubara> we have 6 critical bugs
[16:12] <bigjools> fixed in the rollout
[16:13] <matsubara> 2 fix committed, 3 in progress and one triaged
[16:13] <matsubara> danilos, the one triaged is in rosetta. what's up? are you expecting to land code for that one for the second rollout?
[16:13] <matsubara> bac, do you have a time for the second rollout?
[16:14] <danilos> matsubara: it's in progress
[16:14] <matsubara> thanks bigjools
[16:14] <matsubara> danilos, I mean bug 435891
[16:14] <danilos> matsubara: it's in progress
[16:14] <bac> matsubara: we anticipate a second roll out.  perhaps later today, though no decision has been made yet.
[16:14] <matsubara> danilos, it's not what LP says :-)
[16:15] <danilos> matsubara: it's what I say :)
[16:15] <danilos> bug 435891 is in progress :)
[16:15] <matsubara> danilos, I trust you to beat LP and make it behave :-)
[16:15] <matsubara> thanks danilos
[16:15] <danilos> the other in-progress one is almost landed (in pqm)
[16:15] <flacoste> matsubara: Disconnection errors
[16:15] <flacoste> about them
[16:16] <flacoste> do you know if they happened before or after the roll-out?
[16:16] <flacoste> if they happened before/during the roll-out they are expected
[16:16] <flacoste> we had a bug, now fixed, that logged DisconnectionError as regular OOPS
[16:16] <bac> are you in the production meeting?
[16:16] <flacoste> where it should be logged as a soft oops
[16:16] <danilos> bac: yes, this is the production meeting
[16:16] <bac> sorry, wrong window
[16:16] <flacoste> so DisconnectionError logged after the roll-out are a problem
[16:16] <matsubara> flacoste, after the meeting I'll generate a new summary to find that out.
[16:17] <flacoste> ones before or during it (when running with unfixed code) is not a problem
[16:17] <matsubara> [action] matsubara to generate new oops summary including oopses only for after the rollout
[16:17] <MootBot> ACTION received:  matsubara to generate new oops summary including oopses only for after the rollout
[16:17] <flacoste> matsubara, bac: we can determine the second roll-out time after we have that report
[16:18] <bac> matsubara: i was just made aware of bug 435628 that the bugs team is working on for a re-roll
[16:18] <matsubara> I'll defer the answer to bac
[16:18] <stub> barry was going to look at annotating those oopses so we can tell if they where DisconnectionErrors returned to users, or just part of the normal reconnection workflow.
[16:19] <bac> matsubara: i agree with flacoste that we can make a decision after getting your report
[16:19] <matsubara> all right
[16:19] <stub> erm... gary... not barry
[16:19] <gary_poster> :-)
[16:19] <matsubara> heh
[16:19] <matsubara> ok, I think that's all for this section
[16:19] <matsubara> let's move on
[16:20] <matsubara> thanks everyone!
[16:20] <matsubara> [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
[16:20] <MootBot> New Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)
[16:20] <Chex> HI everyone, brief LOSA report this week.
[16:20] <Chex> - LP 3.0 rollout: The rollout dominated Launchpad work this week. Briefly, things went fairly well, we
[16:20] <Chex> observed a number of items in the rollout process that are being addressed.  We have emailed out the
[16:20] <Chex> full report today.
[16:21] <Chex> And that it for us, unless anyone has questions?
[16:22] <gary_poster> three cheers for losas. :-)
[16:22] <matsubara> thanks Chex
[16:22] <mthaddon> gary_poster: I think you mean three *beers* for each losa...
[16:22] <gary_poster> lol, yeah, probably more appreciated
[16:22] <mthaddon> :)
[16:22]  * stub raises a glass and says 'cheers'
[16:23]  * Chex drinks to that
[16:23] <danilos> so, drunken DB report comes next? :)
[16:23] <matsubara> let's go to the bar, err, move on
[16:23] <matsubara> [TOPIC] * DBA report (stub)
[16:23] <MootBot> New Topic:  * DBA report (stub)
[16:24] <drunken_master> Database update seems to have gone smoothly apart from Bug #435674 being discovered. This will have caused a short hang of the SSO servers, but it was probably quick and hopefully nobody noticed.
[16:24] <danilos> :)
[16:24] <drunken_master> After the update, I needed to do some data migration. That increased replication lag, putting extra load on the master db. All done now and load is back to normal. This will have contributed to timeouts, so you may wants to attribute timeouts before 1200 UTC to this.
[16:24] <drunken_master> The appservers where observed in the wild basing their decision to use the slave database on how lagged that particular slave is, not how lagged the cluster is as a whole. This means that building new slave databases will no longer stop the appservers going into master-only mode.
[16:24] <rockstar> :)
[16:24] <drunken_master> oot.
[16:24] <gary_poster> lol
[16:24] <mbarnett> heh
[16:25] <danilos> thanks for the update drunken_master, always appreciated
[16:25] <matsubara> thanks stub
[16:26] <matsubara> [TOPIC] * Proposed items
[16:26] <MootBot> New Topic:  * Proposed items
[16:26] <matsubara> no proposed items
[16:26] <matsubara> anything else before I close?
[16:26] <matsubara> hi Ursinha
[16:26] <matsubara> just in time :-)
[16:26] <Ursinha> I just want to say sorry
[16:27] <Ursinha> and congrats to all lp team because LP 3.0 rocks
[16:27] <Ursinha> :)
[16:27] <matsubara> indeed!
[16:27] <matsubara> Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.
[16:27] <matsubara> #endmeeting
[16:27] <MootBot> Meeting finished at 10:27.
[16:27] <gary_poster> thank you!