## Template for LP Production Meeting logs. Just paste xchat log below and the format IRC line will take care of formatting correctly
#format IRC
matsubara> #startmeeting
<MootBot> Meeting started at 10:00. The chair is matsubara.
<MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
<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. 
<matsubara> [TOPIC] Roll Call 
<MootBot> New Topic:  Roll Call
<allenap> me
<mrjazzcat> me
<matsubara> Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us! 
<matsubara> Chex, rockstar, bigjools, sinzui, danilos: hi
<matsubara> Ursinha, hi
<rockstar> me
<bigjools> hello
<Ursinha> me
<Ursinha> hi
<danilos> hi
<matsubara> apologies from Gary, he's in a meeting and I'll be the foundations contact for today
<Chex> me
<matsubara> ok, everyone is here
<matsubara> [TOPIC] Agenda 
<MootBot> New Topic:  Agenda
<matsubara>  * Actions from last meeting
<matsubara>  * Oops report & Critical Bugs & Broken scripts
<matsubara>  * Operations report (mthaddon/Chex/spm/mbarnett)
<matsubara>  * DBA report (stub)
<matsubara>  * Proposed items
<matsubara> [TOPIC] * Actions from last meeting
<MootBot> New Topic:  * Actions from last meeting
<matsubara>     * rockstar to investigate failure on update_branches script and reply to the email.
<matsubara> no new failures since last week, so I guess it sorted out by itself
* rockstar nods
<matsubara> [TOPIC] * Oops report & Critical Bugs & Broken scripts
<MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
<sinzui> me
<Ursinha> it's me
* sinzui did not see the rollcall
<Ursinha> so
<Ursinha> three issues to point
<Ursinha> matsubara: bug 403281 seems an old bug, and I saw a bunch of oopses yesterday caused by this problem, could you set the importance, please?
<ubottu> Launchpad bug 403281 in launchpad-foundations "public xmlrpc requests broken during read only period" [Undecided,Triaged] https://launchpad.net/bugs/403281
<Ursinha> matsubara: also, I've filed bug 531695, but not sure if that's foundations
<ubottu> Launchpad bug 531695 in libgraph-perl "libgraph-perl v0.81 is not compatible with libheap-perl v0.80" [Undecided,New] https://launchpad.net/bugs/531695
<Ursinha> it seems a rollout issue
<Ursinha> hmm, that's not right
<matsubara> hmm
<matsubara> hehe
<Ursinha> bug 531965
<ubottu> Launchpad bug 531965 in launchpad-foundations "During the rollout, database changes caused old code to oops" [Undecided,New] https://launchpad.net/bugs/531965
<Ursinha> oops :)
<matsubara> [action] matsubara to discuss with foundations bug 403281 and set importance on it
<Ursinha> matsubara: what do you say?
<MootBot> ACTION received:  matsubara to discuss with foundations bug 403281 and set importance on it
<ubottu> Launchpad bug 403281 in launchpad-foundations "public xmlrpc requests broken during read only period" [Undecided,Triaged] https://launchpad.net/bugs/403281
<Ursinha> cool
<sinzui> I think bug 531965 is a soyuz issue
<ubottu> Launchpad bug 531965 in launchpad-foundations "During the rollout, database changes caused old code to oops" [Undecided,New] https://launchpad.net/bugs/531965
<Ursinha> sinzui: but that isn't oopsing anymore
<bigjools> no it's not a soyuz issue
<matsubara> there's also bug 403281 which is either Code or foundations
<matsubara> errr
<matsubara> wrong bug number
<Ursinha> sinzui: all occurrences I could find happened during the rollout
<matsubara> I meant bug 531687 
<ubottu> Launchpad bug 531687 in launchpad-code "Accessing a merge proposal during the rollout (ie R/O mode) oopsed" [Undecided,New] https://launchpad.net/bugs/531687
<matsubara> rockstar, can you take a look and triage accordingly ^?
<rockstar> matsubara, sure
<rockstar> matsubara, is this part of the meeting really necessary?
<Ursinha> allenap: I see occurrences of https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1524C2016, but not sure this is a known issue
<ubottu> https://lp-oops.canonical.com/oops.py/?oopsid=1524C2016
<matsubara> [action] rockstar to triage bug 531687 
<MootBot> ACTION received:  rockstar to triage bug 531687
<ubottu> Launchpad bug 531687 in launchpad-code "Accessing a merge proposal during the rollout (ie R/O mode) oopsed" [Undecided,New] https://launchpad.net/bugs/531687
<allenap> Ursinha: Looking.
<rockstar> We should (and do) keep up with triaging bugs.  I'm not sure that we need to bring it up in a meeting.
<matsubara> rockstar, I think this section of the meeting is the main reason for this meeting :-)
<Ursinha> rockstar: specially after rollouts
<matsubara> may I ask why do you think it's not important?
<Ursinha> :)
<rockstar> matsubara, because you asked me to do something that someone from our team is going to do at some point today anyway.
<rockstar> matsubara, I think the ops report is the most helpful part of this meeting.
<matsubara> yeah, that part is very useful as well, I agree
<matsubara> we bring up the OOPS that we think are important so it won't fall through the cracks
<rockstar> matsubara, do we need to gather everyone together to do that?
<Ursinha> rockstar: but I recall you suggesting us to file bugs for oopses before coming to the meeting, so why exactly you think the oops section is useful?
<rockstar> Ursinha, ops wasn't a typo.  :)  Operations report
<allenap> Ursinha: That reminds me of a known issue. I don't have a bug number for it yet. If it is the same issue then it's proven very difficult to reproduce.
<matsubara> rockstar, well, we already gather everyone together for this meeting. discussing oops issues is just one side of it, along with scripts failing and critical issues
<Ursinha> allenap: that reminds me of a known issue as well, but I couldn't find the bug
<matsubara> the meeting was evolving to the point we're today. from our experience a lot of things end up falling through the cracks if the QA team don't bring them up
<matsubara> but I'm all ears for suggestion to improve the format of the meeting that would be more useful to you
<matsubara> and by you, I mean all of you
<matsubara> :-)
<matsubara> not only rockstar
<rockstar> matsubara, but I ask if we need a meeting to bring them up.  Can't you just bring them up as they happen?
<danilos> rockstar, I think OOPS section is necessary until we get to a point where every team is on top of their OOPSes *without* matsubara and Ursinha
<matsubara> +1 danilos 
<Ursinha> rockstar: I think it's nice to have a main contact to express our concerns :)
<rockstar> danilos, I agree that matsubara and Ursinha are a HUGE lifesaver.  I just wonder if it needs to be part of the meeting.
<Ursinha> I agree with danilos
<rockstar> Ursinha, oh yeah, I'm happy to be the main contact for QA questions.
<danilos> rockstar, let's discuss that at the end of the meeting; Ursinha, matsubara, anyone else interested, let's move that discussion after the regular agenda
<bigjools> I quite value the input from matsubara and Ursinha for the oopses
* rockstar sighs
<matsubara> as danilos pointed out, once the teams are taking care of OOPSes without our help, then I think this section will slowly fade away
<rockstar> bigjools, I don't disagree with you.
<sinzui> I think we have a lot of unowned or shared apps that do not have team
<bigjools> rockstar: I wasn't referring to anything you'd said actually
<rockstar> bigjools, okay.  :)
<danilos> let's go on and come back to this topic later, pleaaseee :)
<sinzui> I am tempted to fix a bug in malone, launchapd-answers, and blueprints because I am tired of reading spam attacks to find my bugs, but who would know about these attacks if we were not collectively seeing all oopses
<matsubara> all right, so Ursinha, anything else? (did I get all the action items right, specially the ones for foundations?)
<Ursinha> matsubara: nothing else in the oops section
<matsubara> [action] matsubara to discuss bug 531965 with foundations as well
<MootBot> ACTION received:  matsubara to discuss bug 531965 with foundations as well
<ubottu> Launchpad bug 531965 in launchpad-foundations "During the rollout, database changes caused old code to oops" [Undecided,New] https://launchpad.net/bugs/531965
<matsubara> scripts failing: mpcreationjobs and sendbranchmail just failed
<Ursinha> there are two critical bugs, in progress
<matsubara> rockstar, can you take care of those and reply to the list? is this something that could be caused by the rollout?
<allenap> Ursinha: I can't find out any more about that OOPS now, so I'll investigate later.
<Ursinha> thanks allenap :)
<rockstar> matsubara, sure
<matsubara> [action] rockstar to investigate failures on mpcreationjobs and sendbranchmail scripts
<MootBot> ACTION received:  rockstar to investigate failures on mpcreationjobs and sendbranchmail scripts
<Ursinha> bigjools: will you need a rc to fix bug 530566?
<ubottu> Launchpad bug 530566 in soyuz "cron.germinate still believes lpia is active" [Critical,In progress] https://launchpad.net/bugs/530566
<bigjools> Ursinha: I have one but thanks for reminding me to land that branch :)
<Ursinha> bigjools: :)
<Ursinha> matsubara: there's bug 530354 too that seems approved as well
<ubottu> Launchpad bug 530354 in launchpad-foundations "wadl generation is broken after multiversion code has landed" [Critical,In progress] https://launchpad.net/bugs/530354
<rockstar> matsubara, abentley is already figuring out what's going on with those scripts.
<matsubara> thank you rockstar 
<Ursinha> matsubara: it says "Merged", so that is Fix Committed or even Fix Released? could you check, please?
<matsubara> Ursinha, if it says merged, it's fix committed. I think it's this one: # r9069 [release-critical=thumper][r=gary][ui=none] Cache a static WADL file for every version of the web service. 
<matsubara> probably my script that closes it didn't get to it yet :-)
<Ursinha> matsubara: hehe
<Ursinha> okay
<matsubara> let's move on then
<Ursinha> thanks everyone
<matsubara> [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
<MootBot> New Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)
<matsubara> Chex, the stage is yours
<mbarnett> take it and run!
<Chex> hi everyone
<Chex> Here is the LOSA report for this week:
<Chex> - LP rollout 10.02 took 70 mins longer than scheduled. Some related bugs were:
<Chex>         ; Need more visibility into progress of upgrade.py/fti.py/security.py bug 531833
<ubottu> Launchpad bug 531833 in launchpad-foundations "Need more visibility into the progress of upgrade.py/fti.py/security.py" [High,Triaged] https://launchpad.net/bugs/531833
<Chex>         ; Read-only seemed to leave lots of "idle" and "select waiting" connections to the master and
<Chex>                 slave DBs which possibly blocked the DB upgrade bug 531834
<ubottu> Launchpad bug 531834 in launchpad-foundations "When switching to read-only mode, we're left with lots of "idle/select waiting" connections to the DBs which may be blocking the schema upgrade process" [High,Triaged] https://launchpad.net/bugs/531834
<Chex> - LP incidents of note:
<Chex>         ; Crowberry Out-Of-Memory error: https://pastebin.canonical.com/28737/ 2010-03-04 12:30 UTC
<Chex>           Does anyone have any insight into this issue??
<Chex> and thats the report. anyone have questions or comments?
<matsubara> crowberry is code hosting, right? rockstar ^
<rockstar> matsubara, I'm not sure.  I never remember the names of our boxes...
<matsubara> the pastebin indicates it's a code hosting machine
<matsubara> [action] rockstar to investigate Out-Of-Memory error: https://pastebin.canonical.com/28737/ and get back to losas about it
<MootBot> ACTION received:  rockstar to investigate Out-Of-Memory error: https://pastebin.canonical.com/28737/ and get back to losas about it
<Chex> sorry, crowberry is codehosting, yes.
* mrevell has quit (Ping timeout: 252 seconds)
<matsubara> ok, I think we can move on then.
<matsubara> thanks Chex 
<Chex> matsubara: sure
<matsubara> [TOPIC] * DBA report (stub)
<MootBot> New Topic:  * DBA report (stub)
<matsubara> stub will send the report to the list. I'll remind him.
<matsubara> [action] matsubara to remind stub about dba report
<allenap> matsubara: I think he sent it already.
<MootBot> ACTION received:  matsubara to remind stub about dba report
<matsubara> oops
<matsubara> yes, indeed he did. thanks allenap 
<matsubara> [action] cancel last action item about dba report :-)
<MootBot> ACTION received:  cancel last action item about dba report :-)
<matsubara> [TOPIC] * Proposed items
<MootBot> New Topic:  * Proposed items
<matsubara> rockstar, so would you like to discuss a better format for the oops section?
<matsubara> seems to me we have a agreement that the oops section is generally useful and once the teams start to take care of their oopses that section will be unecessary
<danilos> matsubara, we don't have agreement that it will be unnecessary :)
<danilos> matsubara, sinzui has raised an interesting point
<danilos> matsubara, there's a whole bunch of problems which don't belong in any particular team domain
<danilos> matsubara, and then there are also those which appear only for one or two teams, but might be global
<matsubara> right, so we'll continue to bring up those during this meeting
<danilos> I am hoping we'll get to a point where OOPS section will be about those
<matsubara> yep. agreed. 
<rockstar> I think we're pretty good at saying "this doesn't look like a <app> issue.  Maybe ask <other-app-dev>"
<danilos> and prerequisite for not reporting any OOPSes in a meeting is that both teams handle them themselves and that teams are good at bug triage
<rockstar> If there's a bug filed on an oops, it'll get triaged.  That should be a team's responsibility, and if the team isn't getting to it, then we need to evaluate that.
<rockstar> Code has been going out of our way to make sure we get bugs triaged.
<danilos> rockstar, well, we are still very far off zero OOPSes in normal circumstances
<Ursinha> danilos: +1
<rockstar> danilos, this is true, but that's not the issue.
<danilos> rockstar, right, I'd say we have a pretty good situation in translations (rarely more than 10 untriaged bugs), but does it hold for all teams?
<danilos> rockstar, how about launchpad-foundations which is our hold-all bag?
<rockstar> If there's an oops that Ursinha or matsubara sees, they file a bug (they are good at this).  At that point, they should assume the ball has been passed.
<rockstar> danilos, how is launchpad-foundations the "hold-all" bag?  If they have bugs that belong to code, they're hurting foundations and code by not re-assigning them.
<danilos> rockstar, sharing knowledge is useful; when I've seen some OOPSes related to authdb split in translations, I pinged bigjools because I suspected it might bite soyuz as well
<rockstar> danilos, yeah, but that doesn't need to happen in the meeting.
<danilos> rockstar, they have a gazillion bugs which are generic LP problems but not necessarily part of infrastructure, like UI features and such
<sinzui> One problem that I am thinking of was caused by our switch to storm and each application has to make their own fix. This is not a foundations issue, it is an oops that should be targeted to 3 projects
<danilos> sinzui, +1
<rockstar> sinzui, exactly.
<danilos> what I am saying is that we do have problems in some teams that need to be fixed before we can even consider dropping OOPS section from the meeting
<rockstar> Make no mistake.  matsubara and Ursinha are invaluable to Launchpad.  I just don't think they need to duplicate their efforts because I can't triage bugs.
<matsubara> danilos, +1 on the share knowledge usefulness. that's why I think this meeting (and the oops section) is still useful. we bring everyone together and talk about those issues. ideally this would all happen in the bug tracker, but reality is that sometimes some bugs end up falling through the cracks.
<Ursinha> matsubara: +1
<matsubara> and that's where Ursinha and I could help by nagging you guys endlessly :-)
<rockstar> So let's keep the oops section, but not bring up untriaged bugs.
<Ursinha> yes hehe
<danilos> rockstar, I agree, but we first need to make sure "you" are triaging your bugs; care to do the evaluation of all LP subprojects and come back with data that either confirms or rejects my feeling of what it is?
<rockstar> danilos, should QA have to babysit us to triage our bugs?  That doesn't seem fair.
<Ursinha> rockstar: I don't know if that's ideal now; sometimes we dig old triaged bugs (or partially triaged) that need to be taken care now
<danilos> rockstar, no, they shouldn't; can you guarantee all teams will have a very low number of untriaged bugs by next Thursday?
<danilos> Ursinha, rockstar is not complaining about those
<danilos> or at least not strongly :)
<rockstar> danilos, I can't guarantee that, but maybe it's something we should start pushing harder.
<Ursinha> danilos: I'm saying that mentioning bugs isn't useless, triaged or untriaged, because afaik me and matsubara only bring up that ones that need to be taken care of
<danilos> rockstar, what they do today is to raise importance of OOPS bugs in this meeting: sometimes they'll be untriaged, sometimes triaged
<Ursinha> danilos: agreeing with you
<danilos> rockstar, I agree we should start pushing harder, let's have untriaged bugs part of the OOPS section until we feel confident we've done a good push
<matsubara> danilos, so you're asking some kinda of count of untriaged bugs per team in the oops section? we could do that easily, I think.
<danilos> rockstar, we have 218 'New' bugs on launchpad-project today
<rockstar> Alright.  It's obvious that we're at an impass.  I'll bring up my personal feelings with my line manager, and see what comes of it.
<matsubara> danilos, or bring up those untriaged, but until we get those to manageable number, bringing up all of them during the meeting will be difficult and take a lot of time 
<rockstar> I guess leave the meeting as it is.
<danilos> rockstar, now I have to look up 'impass' in a dictionary :)
<rockstar> danilos, deadlock.
<danilos> rockstar, ok, thanks
* bigjools has quit (Remote host closed the connection)
<sinzui> suck to be soyuz it seems
<danilos> rockstar, matsubara: having a per-team count of untriaged bugs would be a good start
<sinzui> and I see one of the new bugs claims to have a patch!
<matsubara> [action] matsubara and/or Ursinha to add a count of untriaged bugs per team to the oops section 
<MootBot> ACTION received:  matsubara and/or Ursinha to add a count of untriaged bugs per team to the oops section
<sinzui> launchpad-foundations has a bug with a patch. I think they are hoping that jml will take the bug away from them
<jml> what
<jml> (gotta ask me first)
* mrevell (~matthew@canonical/launchpad/mrevell) has joined #launchpad-meeting
<sinzui> jml: https://bugs.edge.launchpad.net/launchpad-foundations/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&fie
* sinzui hates bug urls
<danilos> rockstar, btw, I'd be very happy if you get this moving in any way you can, so thanks for raising it!
<danilos> sinzui, we should integrate shorturl service into LP and generate/reuse those URLs with every bugs page :)
<sinzui> danilos: what? implement saved searches for users and teams?
<danilos> sinzui, kind of :)
<danilos> anyway, matsubara, I believe the topic is settled
<sinzui> We certainly would get a lot of cheers from users and even OEM
<matsubara> danilos, thanks for the feedback on this. you too rockstar and sinzui 
<matsubara> anything else before I close?
* bigjools (~quassel@canonical/launchpad/bigjools) has joined #launchpad-meeting
<jml> sinzui, me too
<matsubara> Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs. 
<jml> sinzui, anyway, I'm busy and not really paying attention. If you want me to do something, please email me something asking about it :)
<matsubara> #endmeeting