Creating an account for an imported person OOPSes
Bug #568102 reported by
Francis J. Lacoste
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Guilherme Salgado | ||
Bug Description
If you login using an SSO account for which there is already an email address registered in Launchpad but that was never activated, an OOPS like OOPS-1572M2669 is triggered.
In this particular OOPS, there was a Person that was created from a POImport that existed in Launchpad.
It seems that webapp/
Revision history for this message
| Guilherme Salgado (salgado) wrote | #1 |
| Changed in launchpad-foundations: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in launchpad-foundations: | |
| milestone: | none → 10.04 |
| Changed in launchpad-foundations: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Guilherme Salgado (salgado) |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #2 |
| Changed in launchpad-foundations: | |
| status: | In Progress → Fix Committed |
| tags: | added: qa-needstesting |
| tags: |
added: qa-untestable removed: qa-needstesting |
| Changed in launchpad-foundations: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We'll also need to change the render() method of that same view to handle accounts in the NOACCOUNT state, so this will probably be a good time to refactor that code to avoid adding yet more duplication.