=== mthaddon_ is now known as mthaddon === mrevell is now known as mrevell-lunch === mrevell-lunch is now known as mrevell === bac` is now known as bac [15:00] #startmeeting [15:00] 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. [15:00] Meeting started at 09:00. The chair is Ursinha. [15:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [15:00] [TOPIC] Roll Call [15:00] Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us! [15:00] New Topic: Roll Call [15:00] me [15:00] me [15:00] me [15:00] me [15:00] me [15:01] rockstar, ping [15:01] me [15:01] me [15:01] is stub here? [15:01] flacoste, ping [15:01] me [15:02] yer [15:02] good :) [15:02] all here [15:02] moving on [15:02] [TOPIC] Agenda [15:02] * Actions from last meeting [15:02] * Oops report & Critical Bugs [15:02] * Operations report (mthaddon/herb/spm) [15:02] * DBA report [15:02] New Topic: Agenda === salgado is now known as salgado-lunch [15:02] [TOPIC] * Actions from last meeting [15:02] * losas and stub to fix rollout process to avoid the staging restore problems [15:02] New Topic: * Actions from last meeting [15:02] stub, herb, how was that? [15:03] Pending [15:03] stub, plans to fix that soon? [15:03] we are back to doing full restores though. [15:03] and we have a fall-back non-replicated DB in case it fails [15:04] right, so it's, let's say, under control [15:04] the in-place upgrade (without a DB restore) might still be broken though [15:04] I plan to look at it tomorrow, but have a pretty full schedule and other things more time critical preempting it. [15:04] and stub is supposed to investigate tomorrow [15:04] right [15:05] [action] stub to investigate the fix to avoid staging restore problems [15:05] ACTION received: stub to investigate the fix to avoid staging restore problems [15:05] next [15:05] [TOPIC] * Oops report & Critical Bugs [15:05] 4 oopses (soyuz, 2 bugs, code), 1 bug (registry) [15:05] New Topic: * Oops report & Critical Bugs [15:05] bigjools, https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138B2582 [15:05] https://devpad.canonical.com/~jamesh/oops.cgi/1138B2582 [15:05] bigjools, this is still happening, afaics [15:05] oo that's a new one on me [15:06] new? [15:06] in fact it's a bugs oops :) [15:06] * Ursinha looks if it's the right link [15:06] aww FAIL [15:06] sorry bigjools :) [15:07] intellectronica, let me show the bugs ones [15:07] intellectronica, this one, https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138B2582 [15:07] https://devpad.canonical.com/~jamesh/oops.cgi/1138B2582 [15:07] and https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1137F2893, not sure if it's bugs though [15:07] https://devpad.canonical.com/~jamesh/oops.cgi/1137F2893 [15:08] the last one: https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138EC328 [15:08] rockstar, are you awake enough to look an oops? :) [15:08] * rockstar grunts [15:08] rockstar, https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138CEMAIL12 [15:09] Ursinha, already filed a bug on that one, will be fixing it today. [15:09] rockstar, do you have the bug #? [15:09] Ah man, it's early! [15:09] rockstar, sorry! [15:10] rockstar, right. stick to the fix and I'll find the number [15:10] thanks :) [15:10] [action] rockstar to fix https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138CEMAIL12 [15:10] ACTION received: rockstar to fix https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138CEMAIL12 [15:10] intellectronica, are you there? [15:10] Ursinha: looking at the oopses, sorry [15:11] sinzui, bug 237722 is happening lately [15:11] Launchpad bug 237722 in launchpad-registry "Cyclical team membership allowed in +editproposedmembers" [Low,Triaged] https://launchpad.net/bugs/237722 [15:11] thanks ubottu [15:12] Ursinha: I'll have someone look into it [15:12] sinzui, thanks [15:12] [action] sinzui to have someone to fix bug 237722 [15:13] ACTION received: sinzui to have someone to fix bug 237722 [15:13] Launchpad bug 237722 in launchpad-registry "Cyclical team membership allowed in +editproposedmembers" [Low,Triaged] https://launchpad.net/bugs/237722 [15:13] just flooded intellectronica, have to wait for him :) [15:13] Ursinha: i have no idea what that publishTraverse thing is about [15:14] Ursinha: the two others i know. one is the result of changing a task's target, the other is some problem when reporting a bug with apport [15:14] intellectronica, not sure if that's foundations or bugs [15:15] intellectronica, do you want me to file bugs about those? [15:15] Ursinha, bug 326056 [15:15] Launchpad bug 326056 in launchpad-bazaar "OOPS on InvalidStateTransition when reviewing code by mail" [Low,Triaged] https://launchpad.net/bugs/326056 [15:15] Ursinha: yes, please. i'm also not sure about the publishTraverse error, but i can check and ask foundations for help if necessary [15:15] thanks rockstar :) [15:16] intellectronica, I'll file the bugs [15:16] intellectronica, and appreciate the investigation on the mysterious one [15:17] cool, thanks [15:17] [action] Ursinha to file bugs to https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138EC328 and https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138B2582 [15:17] https://devpad.canonical.com/~jamesh/oops.cgi/1138B2582 [15:17] ACTION received: Ursinha to file bugs to https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138EC328 and https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1138B2582 [15:17] https://devpad.canonical.com/~jamesh/oops.cgi/1138B2582 [15:17] [action] intellectronica to investigate https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1137F2893 [15:17] https://devpad.canonical.com/~jamesh/oops.cgi/1137F2893 [15:17] ACTION received: intellectronica to investigate https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1137F2893 [15:17] https://devpad.canonical.com/~jamesh/oops.cgi/1137F2893 [15:17] right [15:18] no critical bugs [15:18] moving on [15:18] [TOPIC] * Operations report (mthaddon/herb/spm) [15:18] New Topic: * Operations report (mthaddon/herb/spm) [15:18] 2009-02-05 - We rolled out r44 to codebrowse. [15:18] 2009-02-09 - Cherry picked r7716 to lpnet* and the scripts server. [15:18] 2009-02-12 - Earlier today cherry picked r7721 to lpnet*. [15:18] We continue to have problems with codebrowse relating to bug #156453 and bug #118625. [15:18] Launchpad bug 156453 in loggerhead "production loggerhead branch leaks memory" [Critical,Triaged] https://launchpad.net/bugs/156453 [15:18] We also continue to have problems related to #260171. [15:18] Launchpad bug 118625 in launchpad-bazaar "codebrowse sometimes hangs" [High,Triaged] https://launchpad.net/bugs/118625 [15:19] rockstar, do you know how's mwhudson work on bug 260171? [15:19] Bug 260171 on http://launchpad.net/bugs/260171 is private [15:21] All I know is that I've seen lots of reviews going through for loggerhead. That basically all he's been working on. [15:21] rockstar, nice to know [15:21] I'll ask matsubara to talk to him about it today [15:21] thanks rockstar [15:21] herb, anything else? [15:22] that's it. unless there are other questions. [15:22] questions for herb? [15:22] herb, I'll find out that bug status and will let you know [15:22] thanks Ursinha. [15:22] thanks herb [15:22] moving on [15:22] [TOPIC] * DBA report (DBA contact) [15:22] New Topic: * DBA report (DBA contact) [15:23] There is a backlog of DB patch reviews I need to process tomorrow and collate for Mark. If it isn't already, please make sure your branches appear on https://code.launchpad.net/~stub/+requestedreviews so I'm less likely to lose them :) [15:23] The Slony-I replication stopped for a while yesterday. Nagios alert triggered elmo to trigger me. I restarted the replication daemons and monitored it while it resynced. Users didn't notice, except perhaps for a performance degredation. [15:23] I don't know what the cause was, as we managed to lose the relevant logs. This was the first hiccup since we switched replication on, and everything recovered a it was supposed to, so I don't think we have anything to worry about. IS appears to have done the changes they needed to to stop us losing the logs last week, so I can now complete the processs (RT #32320 - switching to the /etc/init.d script to control the daemons rather than the h [15:23] Staging is moving to a new hope 'in a few weeks', and demo can be resurrected then too. Yay! [15:23] \o/ [15:24] c/hope/home (Freudian slip!) [15:24] awesome to hear [15:24] ahahaha [15:24] anything for stub? [15:24] stub: [15:24] stub: I cannot access ~requestedreviews [15:24] intellectronica: the publishTraverse things is caused because the user is going to +edit on the attachment and traversing to the attachement probably returns a RedirectionView [15:24] flacoste is the one who always have last minute notes :) [15:25] I get Unauthorized: (, 'container', 'launchpad.View')
[15:25] ha! [15:25] So just make sure you have a Pending review request to me personally (rather than a team) [15:25] flacoste: oh, i see [15:25] stub: okay [15:26] I'll be checking the ~launchpad and ~launchpad-reviews lists too, but better safe than slipped [15:26] And my mailbox queues [15:26] And my todo list [15:26] :-D [15:26] :) [15:26] to many places to check... [15:26] something will be lost :-) [15:26] Indeed. We need a code review system! [15:26] lol [15:26] that's mean :-) [15:27] well [15:27] anything else? [15:27] 5 [15:27] 4 [15:27] 3 [15:27] 2 [15:28] 1 [15:28] Thank you all for attending this week's Launchpad Production Meeting. See the channel topic for the location of the logs. [15:28] #endmeeting [15:28] Meeting finished at 09:28. [15:28] intellectronica: arguably, we could change RedirectionView to raise NotFound whenever publishTraverse is call, so that these kind of OOPses don't happen [15:29] flacoste: but, why can't we redirect and then traverse? [15:29] intellectronica: for that kind of behaviour you want redirectSubtree [15:29] intellectronica: which redirect to a URL and append everything after it [15:29] intellectronica: but would that work in that case? where are you redirecting? [15:30] thanks all [15:31] flacoste: no idea, i wouldn't expect this to redirect === salgado-lunch is now known as salgado === bac is now known as bac_lunch === bac_lunch is now known as bac === salgado__ is now known as salgado === salgado_ is now known as salgado-afk === bac is now known as bac_afk