## Template for LP Production Meeting logs. Just paste xchat log below and the format IRC line will take care of formatting correctly #format IRC #startmeeting me Meeting started at 11: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 Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us! chex, gary_poster, rockstar, bigjools, allenap: hi me, sorry * rockstar are here I meed earlier sorry bigjools, missed that apologies from Translations. they're sprinting easily missed I was premature :) here me * sinzui (~sinzui@pool-71-163-158-16.washdc.fios.verizon.net) has joined #launchpad-meeting hi sinzui me 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 * Ursinha to send email to stub about the dba report * sinzui to follow up in work with losas to set the increase threshold for the product release finder monitoring script * matsubara to talk to gary_poster about bug 535071 * Done. * Ursinha to send email to TLs about QA summaries * matsubara to triage open oops-tools bugs * Ursinha to triage open lp-qa-tools bugs Launchpad bug 535071 in launchpad-foundations "Better error handling when librarian is offline" [High,Triaged] https://launchpad.net/bugs/535071 * danilos (~danilo@canonical/launchpad/danilos) has joined #launchpad-meeting I did some triage for oops-tools bugs, still some to look at matsubara: done the 1st and the 3rd, not the 2nd matsubara: I have instructions from spm regarding how to change the window or schedule. I will try to land a change next week [action] * Ursinha to send email to TLs about QA summaries ACTION received: * Ursinha to send email to TLs about QA summaries [action] * matsubara to triage open oops-tools bugs ACTION received: * matsubara to triage open oops-tools bugs thanks sinzui and Ursinha np matsubara sinzui, should I add the action item again or can I consider it as done? matsubara: yes. pease do [action] * sinzui to follow up in work with losas to set the increase threshold for the product release finder monitoring script ACTION received: * sinzui to follow up in work with losas to set the increase threshold for the product release finder monitoring script [TOPIC] * Oops report & Critical Bugs & Broken scripts New Topic: * Oops report & Critical Bugs & Broken scripts We're still seeing https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1541O1653 which seems to be a regression of bug 527985 Launchpad bug 527985 in launchpad-foundations "backing out of openid dance creates oops" [High,Fix released] https://launchpad.net/bugs/527985 https://lp-oops.canonical.com/oops.py/?oopsid=1541O1653 another one that seems to be a regression: https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1545E465 --> bug 408738 Launchpad bug 408738 in malone "OOPS when rendering bug activity" [High,Fix released] https://launchpad.net/bugs/408738 https://lp-oops.canonical.com/oops.py/?oopsid=1545E465 and https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1544A949 regression of bug 508302 Launchpad bug 508302 in malone "NotImplementedError OOPS when reporting a bug" [High,Fix released] https://launchpad.net/bugs/508302 https://lp-oops.canonical.com/oops.py/?oopsid=1544A949 sinzui, timeout retrieving vouchers: https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1543EA744, I remember a bug about that but couldn't find it https://lp-oops.canonical.com/oops.py/?oopsid=1543EA744 not sure if it's the same thing matsubara: that was brad and myself matsubara: ISD is still making changes to services we depend on gary_poster, can you look at foundations one ^? matsubara: at this time we are fortunate that only bac and myself are affected looking allenap, can you take a look at the two bugs above? * allenap looks sinzui: argh sinzui, so should we just ignore those oopses for now? is there a bug that we could link to that oops report? * sinzui read the oopses and knows what bac is up to during his work hours matsubara: I have not had a problem in the last two days. matsubara: If it persists I will report a bug on the correct ISD project, sinzui, matsubara : i see that user's project has had a voucher applied so perhaps it was spurious. have we heard from him? bac, nope, I caught that in the oops summary matsubara: bac: this was a networking issue with saleforce. The reason you could not find the bug is that ISD retargeted the other bugs to their porjects matsubara: I'll file a new bug for OOPS-1545E465; the linked bug is not right. https://lp-oops.canonical.com/oops.py/?oopsid=1545E465 sinzui, looks like the oops is triggerable by regular users as well matsubara: anyone using +vouchers is a regular user matsubara: I'll talk to deryck about OOPS-1544A949. https://lp-oops.canonical.com/oops.py/?oopsid=1544A949 [action] allenap to discuss with deryck about OOPS-1544A949 and file a bug for OOPS-1545E465. https://lp-oops.canonical.com/oops.py/?oopsid=1544A949 ACTION received: allenap to discuss with deryck about OOPS-1544A949 and file a bug for OOPS-1545E465. https://lp-oops.canonical.com/oops.py/?oopsid=1545E465 https://lp-oops.canonical.com/oops.py/?oopsid=1544A949 https://lp-oops.canonical.com/oops.py/?oopsid=1545E465 matsubara: the oops is not in launchpad, it is salesforce. We started talking to ISD last month when vouchers broke [action] matsubara to fix linked bug for OOPS-1545E465 https://lp-oops.canonical.com/oops.py/?oopsid=1545E465 ACTION received: matsubara to fix linked bug for OOPS-1545E465 https://lp-oops.canonical.com/oops.py/?oopsid=1545E465 matsubara: I'll be discussing my oops with salgado and filing a new bug or something allenap, gary_poster, thanks (s/or something/or reopening the old one) [action] gary_poster to discuss OOPS-1541O1653 with salgado and file a bug for it. ACTION received: gary_poster to discuss OOPS-1541O1653 with salgado and file a bug for it. https://lp-oops.canonical.com/oops.py/?oopsid=1541O1653 https://lp-oops.canonical.com/oops.py/?oopsid=1541O1653 sinzui, in any case, lp should degrade gracefully when salesforce is offline or timing out DUDE! I know that This is not the channel to discuss ISD's changes to systems that affect launchpad and landscape ok lebowski, I know that you know that. just making sure we're in the same page. I'm more interested in the changes that we can make to avoid the oops from happening (i.e. degrade gracefully) lol I favor removing salesforce. It is not my decision. We can evaluate our dependencies on outsiders when we start NewCo sinzui, rather than removing salesforce, can't we show a page saying that LP couldn't talk to salesforce while the duderino was browsing +vouchers? much like as your proposed solution to bug 267852? Launchpad bug 267852 in launchpad-foundations "google search timeouts are not usable" [Low,Triaged] https://launchpad.net/bugs/267852 matsubara: because it is an oops. there is nothing to show nor any action to take. I could not license Canonical projects for an hour sigh - s/note/not/ oops sinzui, makes sense then. I'll let you know if I see more of these OOPS and then you can escalate with ISD. thanks sinzui we have 5 critical bugs 3 fix committed, one in progress and one confirmed the one confirmed is assigned to me and I'll take care of it today the only broken script is flag-expired-memberships, which stub will take care of thanks everyone, let's move on [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett) New Topic: * Operations report (mthaddon/Chex/spm/mbarnett) * matsubara hands the mic to chex hello everyone here is the LOSA report for this week: - New ImportD server 'pear' has been setup this week and is processing jobs now. - PQM is closing at 2300 UTC Friday for LP roll-out next week. - SSO DB Migration project away from LP DB is delayed due to some issues, does anyone know where we are placed with this now? - LP incidents of note: ; LP Cherry-picks: 22-Mar: CP 9095 to lpnet*, & codehost 24-Mar: CP 9097 to loganberry/checkwatches and 9098 to shipit* and thats the report for this week, any comments/questions?? gary_poster, do you know about the SSO DB migration ^? chex, matsubara, yes chex, losas were cc'd on relevant emails summary: um... other Canonical openid apps that relied on launchpad team membership for privileges were going to break. We have to handle that. A plan is now in place to do so It will involve some DB changes that stub is working on, and some changes for ISD gary_poster: ok, great, sounds good then, thanks We regard splitting the by no later than two weeks from now as an absolute necessity, because of various pressures such as HD space and other excitement, and hope to have it addressed sooner (beginning of week after next) thanks gary_poster, chex [TOPIC] * DBA report (stub) New Topic: * DBA report (stub) I'll email stub for the dba report [action] matsubara to email stub asking the dba report ACTION received: matsubara to email stub asking the dba report [topic] QA Stats of the Week New Topic: QA Stats of the Week Soyuz (soyuz): 70 launchpadlib (launchpadlib): 25 OOPS Tools (oops-tools): 21 Launchpad Developer Utilities (lp-dev-utils): 9 Launchpad Bugs (malone): 8 Launchpad Development Wiki Moin theme (launchpad-dev-moin-theme): 5 Launchpad Auto Build System (launchpad-buildd): 5 Launchpad Buildbot Configuration (lpbuildbot): 2 those are the launchpad projects with untriaged bugs (new state) I'd like to point out that most of the soyuz ones are >2 years old close them all or mark them as triage low :-) triaged, I mean I do so when I have time thanks bigjools I spend more time triaging new ones cool Also please take a look at https://wiki.canonical.com/Launchpad/QATeam/OrphanedCommits/10.03-db-devel and https://wiki.canonical.com/Launchpad/QATeam/OrphanedCommits/10.03-devel bigjools: if you have ignored the issue for more than 6 months, it is 99% of the time low/triaged. the remaining 1% are security issues we should have fixed those are the landings for the 10.03 cycle which are not tracked in the http://people.canonical.com/~lpqateam/test-plan-report-10.03.html burndown sinzui: many of them are simply not bugs any more, in fact bigjools: yep * sinzui closed 1/3 of the bugs as fixed that were supposed to go to launchpad-web [TOPIC] * Proposed items New Topic: * Proposed items there's no new proposed items anything else before I close? Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs. #endmeeting