Launchpad itself

race condition with list creation and team contact addresses

Bug #386689 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Low
Unassigned

Bug Description

This causes list creation to OOPS:
create two teams A and B
1) in A, request a mailing list but don't approve it
2) in B, set the 'contact address' as '<email address hidden>'.
3) activate the mailing list through the admin interface

2) will error, but leaves an email address and account record in the DB
causing the mailing list configure script to OOPS

 affects launchpad

--

See original description
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 386689] [NEW] race condition with list creation and team contact addresses

Note that this isn't trivial to reproduce on staging. Some minor
ordering may have been recorded incorrectly, or staging may be different
in deployment in some way that matters.

One thing is to be sure to use the .staging... in the list mail address
when testing on staging.

-Rob

description: updated
Barry Warsaw (barry)
tags: added: mailing-lists oops
affects: launchpad → launchpad-registry
Changed in launchpad-registry:
assignee: nobody → Barry Warsaw (barry)
importance: Undecided → High
status: New → Triaged
milestone: none → 2.2.6
Barry Warsaw (barry)
Changed in launchpad-registry:
milestone: 2.2.6 → 2.2.7
Revision history for this message
Barry Warsaw (barry) wrote :

Tried as I might, I haven't been able to reproduce this on staging or lp.dev. Rob, if you can reproduce it, can you paste the traceback you get?

Changed in launchpad-registry:
milestone: 2.2.7 → none
status: Triaged → Incomplete
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 386689] Re: race condition with list creation and team contact addresses

On Tue, 2009-06-23 at 23:37 +0000, Barry Warsaw wrote:
> Tried as I might, I haven't been able to reproduce this on staging or
> lp.dev. Rob, if you can reproduce it, can you paste the traceback you
> get?

I only managed to cause it on production. I can test there if you really
like ;)

The bad rows created previously are still in the prod db in the alias
and emailaddress tables.

-Rob

Revision history for this message
Robert Collins (lifeless) wrote :

Oh, and for the traceback, it was found by spm via the OOPS system..

Revision history for this message
Barry Warsaw (barry) wrote :

Do you have the OOPS #? I don't think it's a good idea to create these on production. ;)

Revision history for this message
Robert Collins (lifeless) wrote :

On Wed, 2009-06-24 at 13:45 +0000, Barry Warsaw wrote:
> Do you have the OOPS #? I don't think it's a good idea to create these
> on production. ;)

No; uhm its likely inIRCbacklogs for when this bug was filed, or in OOPS
of the same day. I'll spend some time looking for it.

-Rob

Revision history for this message
Barry Warsaw (barry) wrote :

<lifeless> barry: OOPS-1260XMLP76
<lifeless> barry: OOPS-1260XMLP77

Changed in launchpad-registry:
status: Incomplete → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

We need to continue to understand this bug, but I am lowering its priority since we have had only one report of this problem.

Changed in launchpad-registry:
importance: High → Low
Curtis Hovey (sinzui)
Changed in launchpad-registry:
assignee: Barry Warsaw (barry) → nobody
Revision history for this message
Curtis Hovey (sinzui) wrote :

This is now invalid since the mailing list is now created in the approved state.

Changed in launchpad-registry:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.