User unable to create account

Asked by Andrew Johnson

A user whose LP account was created automatically when we imported our bug database (because he had reported bugs in our original bug tracker) is unable to create a new account or get a new password sent to him. The existing LP account is dirk-zimoch which has his correct email address. He just gets the following rather unhelpful message:

Oops!

Sorry, something just went wrong in Launchpad Login Service.

We’ve recorded what happened, and we’ll fix it as soon as possible.
Apologies for the inconvenience.

(Error ID: None)

Question information

Language:
English Edit question
Status:
Solved
For:
Canonical SSO provider Edit question
Assignee:
No assignee Edit question
Solved by:
Stuart Metcalfe
Solved:
Last query:
Last reply:
Revision history for this message
Stuart Metcalfe (stuartmetcalfe) said :
#1

This is causing an error because there isn't a corresponding password for the user's account. Ideally he would be able to use the 'forgot password' route to create one but that's not currently working. This is a known issue which bug #553966 fixes and should be deployed to production within the week.

Revision history for this message
Andrew Johnson (anj) said :
#2

Thanks, I'll close this question once he's able to login.

Revision history for this message
Andrew Johnson (anj) said :
#3

I have a different user reporting a similar problem, except his response contains
    (Error ID: 1601carambola11)

Is this the same issue, and if so is there an ETA for the deployment?

Revision history for this message
Stuart Metcalfe (stuartmetcalfe) said :
#4

Yes, that is the same error. Production deployment of the fix is expected some time on Monday, 24th May.

Revision history for this message
Andrew Johnson (anj) said :
#5

My second user tried to use the password recovery process to login today, and still got the same failure after typing in hew new password twice.

Revision history for this message
Best Stuart Metcalfe (stuartmetcalfe) said :
#6

Apologies. There was a delay in the deployment. The latest release is now live so please try again and, if you continue to see the same error, please note the oops number (if there is one).

Revision history for this message
Andrew Johnson (anj) said :
#7

Thanks Stuart Metcalfe, that solved my question.