## 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 Meeting started at 09:00. The chair is matsubara. Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] me 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 so, who's here today? me * stub1 (n=stub@modemcable178.77-70-69.static.videotron.ca) has joined #launchpad-meeting * flacoste (n=francis@canonical/launchpad/flacoste) has joined #launchpad-meeting me, sort of me me me rockstar, any chance of you being around? me matsubara, guess he's with the people in the future right now, isn't he? yeah, let's move on then [TOPIC] Agenda New Topic: Agenda * Actions from last meeting * Oops report & Critical Bugs * Operations report (mthaddon/herb/spm) * DBA report (stub) [TOPIC] * Actions from last meeting New Topic: * Actions from last meeting * matsubara to chase stub about staging restore problems * stub, great news! with the new hardware we won't have the staging restore problems anymore? * The staging restore problems should no longer be a problem. * ursinha and matsubara to check OSAs incident log and LP errors list to help identify cause of OOPS-1152EA162 * Filed bug 335172 * rockstar to investigate OOPS-1152XMLP1 * bac to file bugs for OOPS-1153E919, OOPS-1153A1135, OOPS-1153D667 Launchpad bug 335172 in launchpad-foundations "Connection reaper killed connection due to a SoftRequestTimeout" [Undecided,New] https://launchpad.net/bugs/335172 https://devpad.canonical.com/~jamesh/oops.cgi/1153E919 https://devpad.canonical.com/~jamesh/oops.cgi/1153A1135 https://devpad.canonical.com/~jamesh/oops.cgi/1153D667 [action] matsubara to chase rockstar about OOPS-1152XMLP1 ACTION received: matsubara to chase rockstar about OOPS-1152XMLP1 matsubara, that checking was done in the last meeting Ursinha, did it? do we have a bug reported? matsubara, we discussed the issue last meeting, have to check the logs sinzui, do you know if we have bugs for the 3 oopses bac was supposed to file bugs for? There are two bugs filed matsubara, one of them was not a bug, but a one time case matsubara: They appear to be the same and salgado has a fix for bug 337811 Launchpad bug 337811 in launchpad-foundations "OOPS when trying to login with a not registered email" [High,In progress] https://launchpad.net/bugs/337811 so bac didn't open a bug for it, and I kept watching for more oopses, that didn't happen anymore [action] Ursinha to chase status of fix for OOPS-1152XMLP1 ACTION received: Ursinha to chase status of fix for OOPS-1152XMLP1 matsubara, that checking was done in the last meeting matsubara, I'm talking about the checking the incident log s/the checking/checking/ not about the rockstar oops Ursinha, right. now it makes sense [action] matsubara to cancel last Ursinha action item ACTION received: matsubara to cancel last Ursinha action item :-) :) so, all 3 -registry oopses were taken care of thanks everyone [TOPIC] * Oops report & Critical Bugs New Topic: * Oops report & Critical Bugs Ursinha, stage is yours right Three issues: bugs, code and foundations intellectronica, https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1160ED105, oops when trying to access bug 161762 rockstar, https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1159EA69 flacoste, bug 338228 Error: Could not parse data returned by Launchpad: HTTP Error 500: Internal Server Error (https://launchpad.net/bugs/161762/+text) Launchpad bug 338228 in launchpad-foundations "OOPS when trying to login using openid from a page that contains spaces in the URL" [Undecided,New] https://launchpad.net/bugs/338228 matsubara, [action] Ursinha to talk to rockstar about https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1159EA69 that OOPS is definitely confirmed! :-) Ursinha: i commented on that bug, it's caused by a missing index related to a query change matsubara, lol why can't i see this oops? intellectronica, the oops or the bug? [action] Ursinha to talk to rockstar about https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1159EA69 ACTION received: Ursinha to talk to rockstar about https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1159EA69 flacoste, on bug 338228? Launchpad bug 338228 in launchpad-foundations "OOPS when trying to login using openid from a page that contains spaces in the URL" [Undecided,New] https://launchpad.net/bugs/338228 Ursinha: both Ursinha: no, on the oauth one flacoste, I saw that Ursinha: ah, stupid me, that bug is _causing_ the oops :-/ intellectronica, yes :) Ursinha: i don't know what to make of that one, URL with space is kind of a bad idea, i'm pretty sure they are invalid intellectronica, the oops is not synced yet Ursinha, do you have an older OOPS for the same issue? flacoste, there's a page of wiki canonical that mpt tried to edit that has spaces on its name Ursinha: is there a but about this, or shall i file one? I don't know what is the cause of that Ursinha: sure, but to me it's a bug in Moin, it should use %20 in place of the space when talking to us [action] ursinha to file a bug about OOPS-1160ED105 and assign to intellectronica ACTION received: ursinha to file a bug about OOPS-1160ED105 and assign to intellectronica flacoste, it does, at least that's what the oops shows really not when i looked intellectronica, no, I'll file one about it openid.return_to: http://wiki.ubuntu.com/Artwork/Incoming/Jaunty/Kxx Wallpaper?action=login&login=1&oidstage=1&stage=openid&janrain_nonce=2009-03-04T04%3A16%3A43ZVhIsZr see the space there Ursinha: thanks! intellectronica, https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1159H236 https://devpad.canonical.com/~jamesh/oops.cgi/1159H236 flacoste, it's true, the "Referrer" field is the one that shows the %20 intellectronica, np, I'll let you know the number flacoste, so it's a moin bug? Ursinha: i think so i'll ask jamesh what he thinks of this flacoste, thanks that's all from me, matsubara ok. thanks Ursinha we have one critical bug 337942 Bug 337942 on http://launchpad.net/bugs/337942 is private which is from lp-bzr yes [action] matsubara to chase the code guys about bug 337942 ACTION received: matsubara to chase the code guys about bug 337942 Bug 337942 on http://launchpad.net/bugs/337942 is private Bug 337942 on http://launchpad.net/bugs/337942 is private ok, I think that's it. let's move on [TOPIC] * Operations report (mthaddon/herb/spm) New Topic: * Operations report (mthaddon/herb/spm) 2009-02-27 - Rolled out 7767 lpnet, edge and the scripts server. Bug #156453 and bug #118625 continue to cause daily problems. Bug #260171 is still causing problems a couple of times a week. Bug #45419 has been a pain point recently for LOSAs handling questions. Launchpad bug 156453 in loggerhead "production loggerhead branch leaks memory" [Critical,Triaged] https://launchpad.net/bugs/156453 Launchpad bug 118625 in launchpad-bazaar "codebrowse sometimes hangs" [High,Triaged] https://launchpad.net/bugs/118625 Bug 260171 on http://launchpad.net/bugs/260171 is private Launchpad bug 45419 in launchpad-foundations "Launchpad needs a way of easily flagging spam" [High,Triaged] https://launchpad.net/bugs/45419 the usual suspects indeed. it'd be nice if they were less usual yep but that's it from the LOSAs unless there are any questions. herb, do you know if the oopses are being synced to devpad? Ursinha: which oopses? herb, the prod oopses Ursinha: yes herb, I generated some this morning and they seem not to be available yet ok. I will check after the meeting thanks herb all right. thanks herb [TOPIC] * DBA report (stub) New Topic: * DBA report (stub) I'm on a sprint so haven't been monitoring things closely. I think everything is generally ok :) I'm pruning old OAuth nonces right now, as code changes stopped an index being used which slowed things down Other than that, nothing to report. ok. thanks stub1 anything else before I close? 3 2 1 Thank you all for attending this week's Launchpad Production Meeting. See the channel topic for the location of the logs. #endmeeting Meeting finished at 09:25.