## 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] 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 me (in for intellectronica) * flacoste (n=francis@canonical/launchpad/flacoste) has joined #launchpad-meeting me me me * Ursinha (n=ursula@canonical/launchpad/ursinha) has joined #launchpad-meeting erm me? me stub, herb, henninge? rockstar: ? me me! me me Sorry, was ill yesterday, still not at 1[[% 100% all right, everyone is here [TOPIC] Agenda New Topic: Agenda * Next meeting * Actions from last meeting * Oops report & Critical Bugs * Operations report (mthaddon/herb/spm) * DBA report (DBA contact) so next meeting, same time next week? I guess that's a yes all right [topic] * Actions from last meeting New Topic: * Actions from last meeting * rockstar to work with beuno re: critical loggerhead (bug 156453) Launchpad bug 156453 in loggerhead "production loggerhead branch leaks memory" [Critical,In progress] https://launchpad.net/bugs/156453 rockstar: any news about that one? matsubara, working on it. +1 I don't think it's something that's going to happen overnight. rockstar, is it really critical? Ursinha, well, yes. * henninge has quit (Read error: 110 (Connection timed out)) rockstar: any eta? I bet the LOSAs think it's psat Critical. * henninge_ is now known as henninge me again matsubara, until we're sure what the problem is, I can't give you an ETA. rockstar: or can you give us regular status report on the bug report itself? critical bugs shouldn't be left like nobody is looking at them * herb definitely thinks it's critical. particularly since I got a page about it right before the meeting. :) matsubara, I don't really have much to report on it. It's easy to make it leak memory, it's hard to see where it is leaking memory. rockstar, nothing, like partial reports, what are you guys thinking to do ? oh see rockstar: by looking at the report it seems that it's been stuck since 2008-11-06 matsubara, I can put "Still working on this" every once in a while. I just don't have specifics, unfortunately. right Okay, I'll do that. thanks rockstar [TOPIC] * Oops report & Critical Bugs New Topic: * Oops report & Critical Bugs * matsubara hands the mic to Ursinha ok mics make me nervous * bigjools waits for the Karaoke have two bugs and one timeout matsubara's bug: 300320 argh bug 300320 Launchpad bug 300320 in launchpad-foundations "mailman oops directory permission keep getting reset" [High,New] https://launchpad.net/bugs/300320 that's not critical but it's blocking our work so the bot isn't here I've asked herb to fix the permission hahaha ok so matsubara filed this one but we need to find out what's resetting the permission every once in a while matsubara: trying to do some debugging on that, but will reset the permissions after the meeting. matsubara, indeed, just got one of these before the meeting thanks herb. let me know any news on the report please flacoste: I'm not sure that's a foundations or registry issue, btw ok Bug 300183 is critical. I just made it critical Bug 300183 on http://launchpad.net/bugs/300183 is private matsubara: registry the other is for bugs, bug 300324 Launchpad bug 300324 in malone "Bug 297388 OOPSing because had its 0 comment deleted" [High,Triaged] https://launchpad.net/bugs/300324 * Ursinha kicks ubottu sinzui: you are aware of bug 300320? Launchpad bug 300320 in launchpad-foundations "mailman oops directory permission keep getting reset" [High,New] https://launchpad.net/bugs/300320 flacoste: I'll re-assign and coordinate with barry and sinzui then if it's a code or LP config problem. thanks it's the bug regarding that bug that had its comment 0 deleted accidentally Ursinha: I've just triaged that one. The simple fix is to delete all of bug 297388's subscribers Error: Could not parse data returned by Launchpad: HTTP Error 500: Internal Server Error (https://launchpad.net/bugs/297388/+text) and to mark it private hush, ubottu flacoste: I saw it today. I believed it related install problem that is bug 300183 Bug 300183 on http://launchpad.net/bugs/300183 is private Doing that will make it invisible, to all intents and purposes. The OOPS dir permissions are probably being reset by rsync, so the fix is to ensure permissions are set correctly on forster or to tell rsync to make everything locally world readable gmb, thanks, it's really annoying and I'm just waiting for some nice bugs guy to solve that for us Ursinha: Ultimately we want to fix bug 297411 Launchpad bug 297411 in malone "Delete a given bug" [Undecided,Triaged] https://launchpad.net/bugs/297411 hahaha you just caused an oops But it's not easy to do. * Ursinha kicks ubottu again thanks stub. gmb, I saw BjornT 's comment gmb, but for now we need something to stop this bug to oops gmb: If we only hit the red button for spam, we can do it by changing a load of constraints to ON DELETE CASCADE. it's filling the summaries with oopses Ursinha: Well, hiding it should do that. Because veeryone will get "you can't access this bug" eros. Erk. Waaaay wrong word, there. *errors gmb, hm gmb, is it the easiest thing to do? Ursinha: Yes. By far. The trouble is that the Bug table has a lot of dependencies And the dependencies also have a lot of dependencies So we have to find all the things that might depend upon the Bug record before we can DELETE it. gmb, well, but do you need that when hiding? considering hiding != deleting UPDATE Bug SET private = True WHERE id = 287411; DELETE FROM BugSubscription WHERE bug = 297411; * Notify: kiko is offline (lem.freenode.net). (yes, the first number was wrong) And that should do it. gmb, making it private will prevent privileged people to get the oops? gmb: can you add that to LaunchpadProductionStatus page and ask the Losas to run it? Good question. matsubara: Sure. gmb: But we can ignore a lot of the dependencies - if this is spam protection, those dependencies won't exist. [action] gmb to add sql to hide bug 297411 as a fix for bug 300324 ACTION received: gmb to add sql to hide bug 297411 as a fix for bug 300324 Launchpad bug 297411 in malone "Delete a given bug" [Undecided,Triaged] https://launchpad.net/bugs/297411 Launchpad bug 300324 in malone "Bug 297388 OOPSing because had its 0 comment deleted" [High,Triaged] https://launchpad.net/bugs/300324 stub: Is there a way to do a DELETE without Postgres erroring on un-deleted dependenices? another oops coming.. shit, that action is wrong [action] gmb to add sql to hide bug 297388 as a fix for bug 300324 ACTION received: gmb to add sql to hide bug 297388 as a fix for bug 300324 Ursinha: If ubottu listens to its own drivel. Error: Could not parse data returned by Launchpad: HTTP Error 500: Internal Server Error (https://launchpad.net/bugs/297388/+text) Error: Could not parse data returned by Launchpad: HTTP Error 500: Internal Server Error (https://launchpad.net/bugs/297388/+text) Damn. gmb: No, but we can put up with an oops in that case since an admin is hitting the button when they shouldn't arrrrr stub: I'm not quite sure that I'm on your wavelength here. Are you talking about a fix for the OOPS Ursinha raised or for bug 297411 in general? Launchpad bug 297411 in malone "Delete a given bug" [Undecided,Triaged] https://launchpad.net/bugs/297411 * gmb avoids another OOPS gmb: Bug deletion in general (so wrong channel I guess) Ursinha: anything else? stub: Ah right. Yes, let's talk about that elsewhere and not pollute the meeting. thanks gmb :P I think we can discuss the bug deletion bug in the mailing list or whatever. it's not a simple fix anyway matsubara, I have one timeout oops OOPS-1055EC45 I'd like someone to take a look on it few occurrences but high sql time, after the rollout ubottu, I hate you man Sorry, I don't know anything about i hate you man lol https://lp-oops.canonical.com/oops.py/?oopsid=OOPS-1055EC45 sinzui: ^ can you take a look? I have an incredible lag today yuck matsubara: could you make the left pane on that page viewport fixed (so that it is always available wherever you are on the oops)? matsubara: the oops report page i mean flacoste, good idea flacoste: yeah, got that. will do flacoste: and thanks for the suggestion :-) [action] ursinha to file a bug about OOPS-1055EC45 and coordinate with Registry to get it fixed this is all from me ACTION received: ursinha to file a bug about OOPS-1055EC45 and coordinate with Registry to get it fixed let's move on then thanks Ursinha and everyone else [topic] * Operations report (mthaddon/herb/spm) New Topic: * Operations report (mthaddon/herb/spm) matsubara: flacoste I can pass this to Edwin because I think he has day for this. 2008-11-19: Rolled out r7316 to production. - Bugs #118625 and #156453 continue to be a problem causing us to restart codebrowse on a number of ocassions this week. As we discussed earlier. Launchpad bug 118625 in launchpad-bazaar "codebrowse sometimes hangs" [High,Triaged] https://launchpad.net/bugs/118625 - We can probably mark bug #247227 as Fix Released since the app servers have been stable for several weeks now. Launchpad bug 156453 in loggerhead "production loggerhead branch leaks memory" [Critical,In progress] https://launchpad.net/bugs/156453 Bug 247227 on http://launchpad.net/bugs/247227 is private - Do we have a decision on if/when there will be a re-roll? thanks guys thanks sinzui Ursinha: add that the report ^ :-) s/the/to the/ matsubara, will do herb: I talk to kiko about it today and let you know about the re-roll I mean matsubara: ok I'll ask him to join * kiko-fud (n=kiko@canonical/launchpad/kiko) has joined #launchpad-meeting yes dears - Do we have a decision on if/when there will be a re-roll? tonight 22:00 UTC if at all I have spoken cool. thanks kiko-fud ok, great thanks herb thanks kiko-fud [topic] * DBA report (DBA contact) New Topic: * DBA report (DBA contact) thanks Ursinha, matsubara, kiko-fud et al * matsubara hands the mic to stub Our replica production database built happily, and maintaining the replica does not seem to be adding noticable load. My worries about diskspace where thankfully unfounded. We may find that chokecherry's load is too high when we start the appservers using the replica during staging rebuilds. If this turns out to be the case, we have the choice of not using the replica or moving staging somewhere else. oot stub: and the plan is to have that on production next cycle? Its just a config change - we can switch it on whenever. cool. I've got a branch prepared with the config changes and kiko knows already Ursinha: ^ got your answer for waht you asked me yesterday? :-0 :-) great thanks stub matsubara, yes :) anything else before I close? matsubara: i'll land that branch thanks matsubara and statik errr Thank you all for attending this week's Launchpad Production Meeting. See the channel topic for the location of the logs. #endmeeting and stub sorry statik