Closed Bug 736309 Opened 14 years ago Closed 14 years ago

IntegrityError: Duplicate entry for key 'email' in browser ID signup

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kumar, Assigned: ashort)

Details

This is similar to bug 731639 but different in that a Django user with the same email existed when the user tried to register with browser ID. https://arecibo-phx.mozilla.org/view/1741948/
Hi John. Sorry! We are close to solving your registration problem. We solved the last bug but now we're hitting something new. It's tricky because none of us were able to reproduce it.
Assignee: nobody → kumar.mcmillan
Priority: -- → P2
Target Milestone: --- → 6.4.7
Assignee: kumar.mcmillan → ashort
After discussing with kumar we're reaching the conclusion that fixing the bad data in the db that's resulted from lack of transactional updates is probably a better choice than writing workarounds for it. The specific problem in this case is that a row exists in `auth_user` for this email but the `user_userprofile` row doesn't refer to it (or any other); when zamboni tries to create a new `auth_user` the conflict occurs.
Target Milestone: 6.4.7 → 6.4.8
Target Milestone: 6.4.8 → 6.4.9
Further investigation indicates there's a few different failure modes occurring. Here's a handy table to keep track of what can happen depending on DB state and whether browserid is in use: >| | BrowserID | Password | >|---------------------+---------------------------------------------------+----------------------------| >| Both exist unlinked | 'NoneType' has no attribute 'backend' | Link created on login | >| no auth_user | 'NoneType' has no attribute 'backend' | auth_user created on login | >| no user | Duplicate entry 'foo@example.com' for key 'email' | login failure no traceback |
Target Milestone: 6.4.9 → 6.5.0
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.