[13:22] <gary_poster> morning!
[13:23] <mrevell> gary_poster: Hey
[18:50] <Rinchen> me
[18:51] <sinzui> you?
[18:52] <sinzui> ewe?
[18:59] <danilos> me
[18:59] <flacoste> danilos: didn't hear the news?
[18:59] <danilos> flacoste: nope
[18:59] <flacoste> danilos: there is no Launchpad meeting anymore
[18:59] <flacoste> danilos: unless you are the translations QA contacts
[18:59] <Ursinha> flacoste, he is
[18:59] <danilos> flacoste: and where is production QA meeting happening?
[19:00] <Ursinha> danilos, it'll happen here
[19:00] <Ursinha> in a few seconds, i presume
[19:00] <danilos> Ursinha: ok, thanks
[19:00] <Rinchen> me me
[19:01] <danilos> I am not exactly sure what should I have ready for this meeting (i.e. QA status or something), so I have nothing :)
[19:01] <Rinchen> hey danilos
[19:01] <danilos> hey Joey
[19:01] <Rinchen> danilos, I need to get a status on your RC item
[19:01] <matsubara> #startmeeting
[19:01] <MootBot> Meeting started at 13:01. The chair is matsubara.
[19:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:01] <Rinchen> danilos, ping me over in -code and tell me please
[19:01] <danilos> Rinchen: it should be RCFIXED
[19:01] <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.
[19:01] <matsubara> [TOPIC] Roll Call
[19:01] <MootBot> New Topic:  Roll Call
[19:01] <Rinchen> me
[19:01] <Ursinha> me
[19:01] <sinzui> me
[19:01] <herb> me
[19:01] <matsubara> me
[19:01] <gary_poster> me
[19:02] <beuno> me
[19:02] <danilos> me
[19:02] <flacoste> me
[19:02] <matsubara> rockstar: ping?
[19:02] <rockstar> I'm here.
[19:02] <Ursinha> registry, translations, foundations, losas are here
[19:02] <rockstar> Sorry, had a pup emergency.
[19:03] <Ursinha> code is here
[19:03] <mthaddon> me
[19:03] <sinzui> Is Bugs represented?
[19:03] <Ursinha> who's missing
[19:03] <matsubara> bigjools: around?
[19:03] <Ursinha> sinzui, it should be BjornT or intellectronica
[19:03] <bigjools> I'll stand in for cprov since he's not here, but I have to leave shortly
[19:03] <Ursinha> well, soyuz is here
[19:04] <sinzui> Intellectronica is in a pub right now
[19:04]  * bigjools waves
[19:04] <bigjools> sensible man
[19:04] <Ursinha> sinzui, i've noticed that
[19:04] <matsubara> ok. let's get moving then
[19:04] <matsubara> btw, who's the dba contacts?
[19:04] <matsubara> contact, even
[19:04] <flacoste> i am
[19:04] <matsubara> all right, thanks flacoste
[19:04] <matsubara> [TOPIC] Agenda
[19:04] <MootBot> New Topic:  Agenda
[19:04] <matsubara>  * Next meeting
[19:04] <matsubara>  * Actions from last meeting
[19:04] <matsubara>  * Oops report & Critical Bugs
[19:04] <matsubara>  * Operations report (mthaddon/herb/spm)
[19:04] <matsubara>  * DBA report (DBA contact)
[19:04] <matsubara>  * Sysadmin requests (Rinchen)
[19:05] <matsubara> so, next meeting same time ok for everyone?
[19:05] <danilos> I'd prefer a few hour earlier
[19:05]  * Rinchen pokes matsubara to change the topic in mootbot
[19:05] <matsubara> oops, sorry
[19:05] <flacoste> stub would also prefer a few hours earlier
[19:05] <matsubara> [TOPIC] Next meeting
[19:05] <MootBot> New Topic:  Next meeting
[19:05] <danilos> actually, this one is really hard for me to attend to, especially since I've started coming for work earlier
[19:06] <Ursinha> matsubara, i have to take all the suggestions and find the best time
[19:06] <Rinchen> I propose doing what Ursinha just said
[19:06] <matsubara> right, so, we'll discuss the next meeting in the list
[19:06] <Ursinha> danilos, jtv told me that, and i'm considering this
[19:06] <danilos> Ursinha: ok, cool
[19:06] <matsubara> all right, moving on
[19:06] <matsubara> [TOPIC] Actions from last meeting
[19:06] <MootBot> New Topic:  Actions from last meeting
[19:06] <danilos> I remember the last time it was because of New Zealenders, and I don't see any this time around so...
[19:07] <rockstar> Well, that's not official yet.
[19:07] <Rinchen> yes, we should be able to go earlier if it's more convenient
[19:07] <matsubara> * stub to patch our fti regexp to avoid OOPSes (bug 174368) and discuss a proper fix with jtv
[19:07] <Ursinha> and considering the people's suggestions, it'll be much probably changed to earlier
[19:07] <flacoste> no progress on that
[19:07] <Ursinha> than now
[19:08] <Ursinha> flacoste, stub wasn't here in the last meeting
[19:08] <danilos> Ursinha: stub is away until Monday, afaik
[19:08] <flacoste> yes
[19:08] <flacoste> like i said: no progress on that
[19:08] <flacoste> i'll check that up with him next week
[19:08] <Ursinha> danilos, flacoste, thanks for pointing that
[19:08] <Ursinha> flacoste, thanks
[19:08] <matsubara> thanks flacoste.
[19:08] <matsubara> [TOPIC] Oops report & Critical Bugs
[19:08] <MootBot> New Topic:  Oops report & Critical Bugs
[19:09] <matsubara> Today's oops report is aboug bug 271561 and OOPS-991SMPM37, OOPS-991EB136, OOPS-992C476.
[19:09] <flacoste> is that one for us or code?
[19:10] <matsubara> flacoste: for code, but you could jump in and give the guys some help. they think it's related to Zope stuff
[19:10] <flacoste> they always do :-)
[19:10] <matsubara> :-)
[19:10] <rockstar> :)
[19:10] <Ursinha> :)
[19:10] <flacoste> the OOPS seems unrelated though
[19:10] <flacoste> i mean the oops reference is about Archive:+index
[19:11] <matsubara> btw, OOPS-992C476 is another one that seems related to zope stuff
[19:11] <flacoste> err, sorry,
[19:11] <rockstar> flacoste, I'll follow up with the rest of the team this evening, and let them know that you're willing to help
[19:11] <flacoste> fortunately, we have a zope master that joined this week
[19:11] <flacoste> everyone, meet gary_poster
[19:11] <gary_poster> heh
[19:11] <Rinchen> hi gary_poster!
[19:11] <flacoste> gary_poster, meet everybody :-)
[19:11] <matsubara> sorry, I don't have bugs for those yet as I they showed up in today's report
[19:11] <Ursinha> gary_poster, welcome :)
[19:11] <gary_poster> hi everybody
[19:11] <matsubara> rockstar, there is a double tilde in the URL in OOPS-991SMPM37. It looks quite
[19:11] <matsubara> strange. Do you know why that might be happening?
[19:11] <danilos> gary_poster: hey, welcome :)
[19:11] <bigjools> howdy gary_poster
[19:11] <gary_poster> thanks :-)
[19:11] <matsubara> hi gary_poster, welcome!
[19:12] <matsubara> I've asked salgado about OOPS-991EB136. salgado suspects it's caused by a bug
[19:12] <matsubara> in IE causing the map to not render properly. I'll test it a bit and follow up
[19:12] <matsubara> with salgado (updating the already filed bug or file a new one if necessary)
[19:12] <flacoste> matsubara: /C476 seems to be a fallout of stub db policy branch
[19:12] <flacoste> matsubara: so we will take it
[19:12] <danilos> (so that's why we didn't start this meeting with "hi, I am an alcoholic": leaving a good impression on the new guy)
[19:12] <rockstar> matsubara, I'm unclear as to what you're asking me.
[19:12] <gary_poster> :-)
[19:12] <matsubara> flacoste: all right. i'll file a bug and assign to you after the meting
[19:12] <Ursinha> haha
[19:12] <matsubara> meeting
[19:13] <flacoste> matsubara: regarding code bug: "I lean towards the scanner."
[19:13] <flacoste> that's from jml
[19:13] <matsubara> rockstar: re: https://devpad.canonical.com/~matsubara/oops.cgi/2008-09-17/SMPM37 there's a double tilde in the URL which is quite strange
[19:13] <rockstar> Yea, the scanner has been undergoing some changes recently, so it's probably an acurate guess.
[19:14] <rockstar> matsubara, someone hacking the url?
[19:14] <rockstar> Or possibly a bzr branch config problem.
[19:15] <matsubara> well, that's branch puller oops
[19:15] <rockstar> Yea, that's confusing.
[19:16] <matsubara> rockstar: I'll file a bug about it and we can try to figure out if it's a problem on our side or just broken bzr branch config
[19:16] <matsubara> we don't have a Bugs team contact, but I'd like to ask about the api timeout bug
[19:17] <matsubara> I'll have to follow that up with them later then.
[19:17] <matsubara> btw, thanks for identifying the problem on that timeout flacoste
[19:17] <flacoste> thanks goes to leonard
[19:17] <flacoste> matsubara: for the record, i think we have a similar issue in answers
[19:17] <matsubara> I'm done with OOPSes. anything else shows up in the summaries today. I'll follow up with the teams
[19:18] <Ursinha> great
[19:18] <Ursinha> well, there are four critical bugs, three fix committed, one opened
[19:18] <Ursinha> bug 269384
[19:18] <Ursinha> is a bug related to bugzilla
[19:18] <matsubara> flacoste: thanks for letting me know. can you assign one of yours to investigate if it's a problem?
[19:18] <flacoste> matsubara: you mean answers, it's not yet because it's not exposed in the API, but I know the same algorithm is used there
[19:20] <matsubara> flacoste: right. I'll open a bug task for it and add your comment there then so we won't forget
[19:20] <flacoste> matsubara: thanks
[19:20] <matsubara> btw, answers is under your jurisdiction isn't it?
[19:21] <matsubara> Ursinha: I guess will have to check with the Bugs team about that one later
[19:21] <Ursinha> matsubara, seems the best option
[19:22] <Ursinha> i'll do that when intellectronica returns from pub
[19:22] <matsubara> thanks Ursinha
[19:22] <flacoste> matsubara: i think it's registry jursidiction nows
[19:22] <Ursinha> i'll try
[19:22] <sinzui> ha ha
[19:22] <matsubara> flacoste: oh, I wasn't aware.
[19:22] <matsubara> the one man show!
[19:22] <sinzui> I am happy to take Answers
[19:22] <matsubara> sinzui: cool! thanks!
[19:22] <flacoste> matsubara: well registry team has just been formed, so it's normal
[19:22]  * sinzui was in Answer bugs looking for a dup of the fti OOPs anyway
[19:23] <matsubara> right. moving on
[19:23] <matsubara> [TOPIC] Operations report (mthaddon/herb/spm)
[19:23] <MootBot> New Topic:  Operations report (mthaddon/herb/spm)
[19:23] <herb> * 2008-09-11 - Cherry pick r6972
[19:23] <herb> * Had a couple of incidents of codebrowse needing to be restarted (2008-09-12, 2008-09-15)
[19:23] <herb> * Had a couple of incidents of app servers dying and leaving a stale PID file (2008-09-15, 2008-09-17)
[19:23] <herb> * Send a core dump of last lpnet app server death to flacoste for analysis
[19:23] <herb> * 2008-09-17 - Roll out 2.1.9
[19:24] <herb> * Have retired authserver(s) and separate restricted librarian
[19:24] <herb> * Pending DB query on LPS from jtv still needs approval (or otherwise)
[19:24] <herb> That's it from Tom, Steve and me unless there are any questions.
[19:24] <flacoste> herb: aargh, i completely forgot that one, thanks for reminding me :-/
[19:24] <herb> flacoste: no problem. :)
[19:25] <Rinchen> herb, rockstar - is the codebrowse issue still being working on by mwh?
[19:25] <rockstar> Rinchen, I know there was a production issue last night, but I think jml was working on it.
[19:25] <herb> Rinchen: I'm not aware if it is. I haven't been as tenacious about it as perhaps I should have been.
[19:25] <Rinchen> k, thanks
[19:26] <matsubara> thanks herb
[19:26] <matsubara> [TOPIC] DBA report (DBA contact)
[19:26] <MootBot> New Topic:  DBA report (DBA contact)
[19:26] <matsubara> flacoste: stage is yours
[19:26] <flacoste> that will be a short one
[19:26] <flacoste> replication scripts branch was cut-off when PQM went release-critical
[19:27] <flacoste> they'll land once stub is back and PQM re-opens
[19:27] <flacoste> which means we should see some testing of replication on demo next week
[19:27] <flacoste> EOT
[19:27] <cprov> me (apologies, I'm late, because I'm a moron !)
[19:27] <rockstar> Wow, that was short.
[19:27] <Rinchen> yay! finally testing on demo
[19:27] <herb> flacoste: how did we miss the xmlrpc session user?
[19:27] <matsubara> thanks flacoste
[19:28] <flacoste> herb: because the session was not used previously
[19:28] <herb> ah
[19:28] <flacoste> the multi-store supprot make it used on every erequest
[19:28] <flacoste> which made the xml-rpc server needed it
[19:29] <matsubara> [TOPIC] Sysadmin requests (Rinchen)
[19:29] <MootBot> New Topic:  Sysadmin requests (Rinchen)
[19:29] <herb> flacoste: thanks.
[19:29] <Rinchen> Is anyone blocked on an RT or have any that are becoming urgent?
[19:29] <flacoste> sinzui has one
[19:29] <flacoste> well, not urgent
[19:29] <flacoste> but a new one
[19:29] <flacoste> that came in late
[19:29] <sinzui> One that we want settled by next week
[19:29] <Rinchen> lay the number on me
[19:29] <flacoste> sinzui: i wanted to comment on that
[19:29] <flacoste> buyt didn't have the number
[19:30] <flacoste> i don't thin it's required for landing
[19:30] <flacoste> only for testing
[19:30] <Rinchen> ok, get that to me when you can with a due date
[19:31] <matsubara> ok. is that it?
[19:31] <matsubara> any comments before closing the meeting?
[19:31] <Rinchen> think so, back to you matsubara
[19:31] <matsubara> thanks Rinchen
[19:31] <danilos> matsubara: thanks for running this first instance of the production meeting :)
[19:31] <Rinchen> thanks matsubara. You'll be talking to Tom B about attendance ?
[19:32] <matsubara> Rinchen: Ursinha will do :-)
[19:32] <Ursinha> Rinchen, i'll do
[19:32] <matsubara> danilos: np. will sort out a better time for you dude
[19:32] <matsubara> Thank you all for attending this week's Launchpad Production Meeting. See the channel topic for the location of the logs.
[19:32] <Ursinha> sweet
[19:32] <matsubara> #endmeeting
[19:32] <MootBot> Meeting finished at 13:32.
[19:32] <danilos> thanks and good night
[19:32] <Ursinha> danilos, bye, thanks for attending
[19:33] <rockstar> Thanks!
[19:33] <Ursinha> thanks all for attending :)