#format irc #startmeeting 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 Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us! Meeting started at 10:02. The chair is Ursinha. Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] New Topic: Roll Call me me ich me me * flacoste (n=francis@canonical/launchpad/flacoste) has joined #launchpad-meeting me me herb, intellectronica, hi :) who's missing? stub is missing, but he can join later * mthaddon (n=mthaddon@adsl-70-137-141-190.dsl.snfc21.sbcglobal.net) has joined #launchpad-meeting intellectronica is missing too let's move on [TOPIC] Agenda * Actions from last meeting * Oops report & Critical Bugs * Operations report (mthaddon/herb/spm) * DBA report (stub) New Topic: Agenda [TOPIC] * Actions from last meeting * Ursinha to talk to intellectronica about bug 357316 * Ursinha to talk to henninge about bug 302449 * rockstar to confirm that bzr fix for bug 360791 was applied to LP's bzr tree. * cprov to request CP of fix for bug 370513 New Topic: * Actions from last meeting Launchpad bug 357316 in malone "hwdb +submit failing with KeyError OOPS" [Undecided,Triaged] https://launchpad.net/bugs/357316 Launchpad bug 302449 in rosetta "Uploading a file with the same name triggers a database constraint." [Medium,Triaged] https://launchpad.net/bugs/302449 I suck and failed mine Launchpad bug 360791 in bzr/1.14 "bzr pull/branch shows "Error received from smart server: ('NoSuchRevision',)"" [Critical,In progress] https://launchpad.net/bugs/360791 Launchpad bug 370513 in soyuz "failure to accept PPA uploads" [Critical,Fix committed] https://launchpad.net/bugs/370513 [action] Ursinha to talk to intellectronica about bug 357316 ACTION received: Ursinha to talk to intellectronica about bug 357316 henninge, hi :) I think danilo was onto that ... I don't know if the fix has been cherry picked into production... henninge, can you just confirm that, please? it's set as medium, do we use that status? Ursinha: in rosetta we do ;) rockstar, hm, can you check that too? Code team does, for things of medium importance. as does Soyuz rockstar: it was cherry picked on 2009-05-09 I rarely see medium statuses :) that's why I'm asking thanks herb herb: cool, thanks. [action] henninge to check with danilo the status of bug 302449 ACTION received: henninge to check with danilo the status of bug 302449 Launchpad bug 302449 in rosetta "Uploading a file with the same name triggers a database constraint." [Medium,Triaged] https://launchpad.net/bugs/302449 cool moving on then [TOPIC] * Oops report & Critical Bugs there's only one worth mentioning, that is the one causing the InterfaceError oopses, we're still having lots and lots of occurrences (bugs 374909 and 376207), seems to be worked on by jamesh, is that correct flacoste? New Topic: * Oops report & Critical Bugs Launchpad bug 374909 in storm "InterfaceError: connection already closed should be converted into DisconnectionError" [High,Triaged] https://launchpad.net/bugs/374909 Launchpad bug 376207 in launchpad-foundations "LaunchpadOpenIDStore doesn't support database disconnection" [High,In progress] https://launchpad.net/bugs/376207 so, jamesh is working on 374909 and the other one also right but stuart has an easy fix for the later, that I'll likely asked to be cherrypicked we can deploy jamesh proper fix during next roll-out flacoste, hm, good flacoste, about the cp, when do you think it can be done? i didn't look at the branch 374909 is still cropping up from time to time, btw. though it's much gooder(tm) than it was last week. but once i approved it, as soon as the LOSA can take care of it flacoste, right. okay i don't think i'll ask a C-P of the INterfaceError (storm fix being worked on by jamesh) flacoste: why? well, because that's not a root-cause so with the other fix in place, we shouldn't see it ok that fix is more prophylactic flacoste, who's investigating the root cause? if you are talking about why we are getting disconnection errors in the first place nobody, really but we have a fix for the places where we should be trapping those and recovering yes, the disconnection errors we have no ideas at why it's happening there is nothing in the DB logs about them this is creepy the fix you say you have is inside the fixes for one of those bugs? yes great so, you'll ask a cp for the second bug exactly [action] flacoste to ask a cp for fix for bug 376207 after reviewing it ACTION received: flacoste to ask a cp for fix for bug 376207 after reviewing it Launchpad bug 376207 in launchpad-foundations "LaunchpadOpenIDStore doesn't support database disconnection" [High,In progress] https://launchpad.net/bugs/376207 awesome we have one critical bug, being worked on so, unless anyone has anything to point, moving to the next section! good [TOPIC] * Operations report (mthaddon/herb/spm) New Topic: * Operations report (mthaddon/herb/spm) 2009-05-07 - Cherry pick r8906 to the scripts server and r122 of storm to lpnet* & edge* 2009-05-09 - Cherry pick r4006 of bzr to the codehosting server and r123 of storm to lpnet* & edge* 2009-05-09 - Cherry pick r8348, r8312 to the PPA server and r8376 to lpnet* 2009-05-10 - mailman didn't have access the necessary access to the DB server, but it was only noticed after restarting for log rotation. mailing lists were unavailable for approximately 7 hours. We still seem to be encountering bug #156453 and bug #118626, but the situation is much improved since the rollout. flacoste: cprov requested a rollout of the current production tree to cesium. Apparently there was a critical fix that was included in while in RC, but we didn't re-roll to cesium. Can you (dis)approve that? Launchpad bug 156453 in loggerhead "production loggerhead branch leaks memory" [Critical,In progress] https://launchpad.net/bugs/156453 Launchpad bug 118626 in bzr-email "plugin documentation does not make interaction with checkouts clear" [Medium,Confirmed] https://launchpad.net/bugs/118626 herb: it's already approved by kiko herb: i think kiko did? but otherwise, i can look into it right bigjools: missed it. thanks any other questions to herb? okay [TOPIC] * DBA report (stub) New Topic: * DBA report (stub) herb: I was under the impression that the loggerhead stuff was WAY better than "much improved" stub sent it to the list rockstar: we're still restarting a couple of times a week. which is much improved over a couple of times a day. rockstar: order of magnitude. flacoste, to lp list? I can't seem to find it herb: okay. Is it memory restarts, or hanging restarts The ex-master database (launchpad_prod on hackberry) is bloated and started exceeding its free space map settings. Nothing really to worry about - it might cause bloat to spiral but I suspect not in this case. The losas can bounce it after shutting down the systems using it as a slave, and I've suggested using it as the standalone replica for read-only mode launchpad during the rollout because we then rebuild it (The memory restarts shouldn't be happening anymore) afterwards and it will be all nice and freshly packed. Nothing major do do with database patches this cycle. rockstar's bugbranch and specbranch column pruning needs to be cleared with Mark still. thanks flacoste flacoste: yeah, and there are other branches dependent on that one. rockstar: The memory situation seems ok (ie. not death spiraling). seems to be hangs at this point. rockstar: we still see it ~1.5GB resident, but doesn't seem to grow beyond that. herb: well, "death spiraling" to be is different than the memory issues. herb: it's going to be *kinda* memory intensive just because of what it's serving. rockstar: understood rockstar: as I said, much improved. 1.2 - 1.5G is much better than 3.7G herb: and we know the cause of the hangs, we just don't know how to fix it. rockstar: good news, bad news, eh? herb: yeah, something like that. okay. anyone else want to say something? 5 4 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