## Template for LP Production Meeting logs. Just paste xchat log below and the format IRC line will take care of formatting correctly #format IRC Meeting started at 10:00. The chair is matsubara. Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] 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. [TOPIC] Roll Call New Topic: Roll Call me Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us! ni! me me me me, sitting in for sinzui Ursinha, Chex: hi * flacoste (n=francis@canonical/launchpad/flacoste) has joined #launchpad-meeting me danilos, are you joining us? * Chex is here matsubara, flaky internet allenap, hi me matsubara: yes me danilos, shall I make you the default translations person for the LP prod meeting? me? you! hi mbarnett welcome :-) :) ok, everyone is here [TOPIC] Agenda New Topic: Agenda * Actions from last meeting * Oops report & Critical Bugs & Broken scripts * Operations report (mthaddon/Chex/spm/mbarnett) * DBA report (stub) * Proposed items [TOPIC] * Actions from last meeting New Topic: * Actions from last meeting * barry to continue debug on bug 403606 after finishing 3.0 UI stuff * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it Launchpad bug 403606 in launchpad-registry "ExpatError errors should be handled to not generate the OOPSes" [High,Triaged] https://launchpad.net/bugs/403606 matsubara: yes I still suck, haven't done that one. [action] * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it ACTION received: * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it EdwinGrubbs, I'll keep the action item for barry in the list since 3.0 crazyness is not over yet :-) [action] * barry to continue debug on bug 403606 after finishing 3.0 UI stuff ACTION received: * barry to continue debug on bug 403606 after finishing 3.0 UI stuff Launchpad bug 403606 in launchpad-registry "ExpatError errors should be handled to not generate the OOPSes" [High,Triaged] https://launchpad.net/bugs/403606 [action] matsubara to update translations qa contact on meeting agenda page ACTION received: matsubara to update translations qa contact on meeting agenda page [TOPIC] * Oops report & Critical Bugs & Broken scripts New Topic: * Oops report & Critical Bugs & Broken scripts Ursinha, go ahead hmm Ursinha was having connectivity problems before the meeting ok, so, let me take over for what I can bac is doing a great job with managing release of 3.0 and any critical bugs what we've seen is already listed on https://dev.launchpad.net/CurrentRolloutBlockers thanks. getting lots of good help. we have noticed increased timeouts on production DBs, due to postgres restart for more details, Ursinha will have to fill us in we had a bunch of disconnection errors as well matsubara: around the time of rollout or? (because that'd be expected if so) * Ursinha has quit (Read error: 113 (No route to host)) danilos, not sure, Ursinha just sms'ed me and asked me to bring it up but I take the increase on those are due to the rollout, yes so, Ursinha and I will keep looking for the new oopses that happened since the rollout 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 and let each affected team about them and add them to the CRB page matsubara: thanks matsubara, that'd be great we had some script failures as well related to the rollout and another one unrelated which bigjools already replied to (which is the packagediffs thing) we have 6 critical bugs fixed in the rollout 2 fix committed, 3 in progress and one triaged danilos, the one triaged is in rosetta. what's up? are you expecting to land code for that one for the second rollout? bac, do you have a time for the second rollout? matsubara: it's in progress thanks bigjools danilos, I mean bug 435891 Launchpad bug 435891 in rosetta "recent update broke the urls used in launchpad integration" [Critical,Triaged] https://launchpad.net/bugs/435891 matsubara: it's in progress matsubara: we anticipate a second roll out. perhaps later today, though no decision has been made yet. danilos, it's not what LP says :-) matsubara: it's what I say :) bug 435891 is in progress :) danilos, I trust you to beat LP and make it behave :-) thanks danilos the other in-progress one is almost landed (in pqm) matsubara: Disconnection errors about them do you know if they happened before or after the roll-out? if they happened before/during the roll-out they are expected we had a bug, now fixed, that logged DisconnectionError as regular OOPS are you in the production meeting? where it should be logged as a soft oops bac: yes, this is the production meeting sorry, wrong window so DisconnectionError logged after the roll-out are a problem flacoste, after the meeting I'll generate a new summary to find that out. ones before or during it (when running with unfixed code) is not a problem [action] matsubara to generate new oops summary including oopses only for after the rollout ACTION received: matsubara to generate new oops summary including oopses only for after the rollout matsubara, bac: we can determine the second roll-out time after we have that report I'll defer the answer to bac matsubara: i was just made aware of bug 435628 that the bugs team is working on for a re-roll Launchpad bug 435628 in malone "Attempting to file a bug on an Ubuntu source packages OOPSes when bug filing is disabled" [High,Triaged] https://launchpad.net/bugs/435628 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. matsubara: i agree with flacoste that we can make a decision after getting your report all right erm... gary... not barry :-) heh ok, I think that's all for this section let's move on thanks everyone! [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett) New Topic: * Operations report (mthaddon/Chex/spm/mbarnett) HI everyone, brief LOSA report this week. - LP 3.0 rollout: The rollout dominated Launchpad work this week. Briefly, things went fairly well, we observed a number of items in the rollout process that are being addressed. We have emailed out the full report today. And that it for us, unless anyone has questions? three cheers for losas. :-) thanks Chex gary_poster: I think you mean three *beers* for each losa... lol, yeah, probably more appreciated :) * stub raises a glass and says 'cheers' * Chex drinks to that so, drunken DB report comes next? :) let's go to the bar, err, move on [TOPIC] * DBA report (stub) New Topic: * DBA report (stub) * stub is now known as 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. 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. 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. :) Launchpad bug 435674 in launchpad-foundations "fti.py wants to lock all replication sets" [High,Triaged] https://launchpad.net/bugs/435674 oot. lol * drunken_master is now known as stub heh thanks for the update drunken_master, always appreciated thanks stub [TOPIC] * Proposed items New Topic: * Proposed items no proposed items * Ursinha (n=ursula@canonical/launchpad/ursinha) has joined #launchpad-meeting anything else before I close? hi Ursinha just in time :-) I just want to say sorry and congrats to all lp team because LP 3.0 rocks :) indeed! Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs. #endmeeting Meeting finished at 10:27.