user oopsing when attempting to add an email address belonging to a never activated account

Bug #576757 reported by Steve McInerney
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
j.c.sackett

Bug Description

ref: https://answers.edge.launchpad.net/launchpad/+question/109891

https://lp-oops.canonical.com/oops.py/?oopsid=1587A903
https://lp-oops.canonical.com/oops.py/?oopsid=1587H939

launchpad_prod_3=# select * from emailaddress where email = 'dave@biff....';
   id | email | person | status | date_created | account
---------+------------------+--------+--------+----------------------------+---------
 1646535 | dave@biff.... | | 1 | 2007-11-15 17:59:12.775719 | 1637149
(1 row)

launchpad_prod_3=# select account.* from account, emailaddress where email = 'dave@biff.....' and account.id = emailaddress.account;
   id | date_created | creation_rationale | status | date_status_set | displayname | openid_identifier | status_comment | old_openid_identifier
---------+----------------------------+--------------------+--------+----------------------------+--------------+-------------------+----------------+-----------------------
 1637149 | 2007-11-15 17:59:12.775719 | 7 | 10 | 2007-11-15 17:59:12.775719 | Dave | ...... | | 959/dave-biff
(1 row)

We fixed in this instance by zotting the email address on this old account with '.broken' at the end.

Related branches

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

I wonder if this relates to the problem in bug 128584. I suspect a fix for one will also fix the other.

Changed in launchpad-registry:
importance: Undecided → Low
Revision history for this message
Michael Nelson (michael.nelson) wrote :

This happened again today:
{{{
11:00 < voidspace> attempting to add a new email to my launchpad account fails - is this a known issue?
11:01 < voidspace> statik: hi
11:01 < voidspace> (Error ID: OOPS-1710E559)
11:01 < ubot5> https://lp-oops.canonical.com/oops.py/?oopsid=1710E559
}}}

and

{{{
11:20 < noodles775> voidspace: re. your oops - one of the LP registry team will be interested to look at fixing the bug, but for what its worth, the exception is being raised while it is trying to tell you that the email address is already in use.
11:20 < wgrant> For which we have ShipIt to blame :(
11:21 < wgrant> I suspect.
11:21 < noodles775> wgrant: Ah, does it create email addresses where email.person is None?
11:21 -!- voidspace [~voidspace@87-194-212-65.bethere.co.uk] has quit [Read error: No route to host]
11:21 < wgrant> noodles775: ShipIt does Accounts, not Persons.
11:21 < wgrant> So, yes :(
11:22 < wgrant> And for no very good reason it still haunts the same DB as LP.
}}}

Curtis Hovey (sinzui)
tags: added: oops
Changed in launchpad-registry:
importance: Low → High
milestone: none → 10.10
j.c.sackett (jcsackett)
Changed in launchpad-registry:
assignee: nobody → j.c.sackett (jcsackett)
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
tags: added: qa-needstesting
Changed in launchpad-registry:
status: Triaged → Fix Committed
j.c.sackett (jcsackett)
tags: added: qa-ok
removed: qa-needstesting
Curtis Hovey (sinzui)
Changed in launchpad-registry:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers