User accounts disabled - "$name does not use Launchpad"

Bug #246524 reported by Matthew Revell
10
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Curtis Hovey

Bug Description

Two people have reported that their accounts have been disabled, despite their being active users of Launchpad. Both people say they did nothing unusual nor did they ask to close their account.

The message reported on each account overview page is, "$name does not use Launchpad".

Herb took a look at one user's account (~sdocio) and said nothing in the database looked unusual. The other user account is ~khalderon.

Marking as critical as I assume it affects more than just two users.

Changed in launchpad:
importance: Undecided → Critical
Revision history for this message
Stuart Bishop (stub) wrote :

They both had an Account.status of 30 (deactivated by user). I think this status was brought across from the Person.account_status, but that we used to ignore the Person.account_status and now we don't.

I've reset these two accounts to Account.status = 20 so they should be able to login now.

Revision history for this message
Matthew Revell (matthew.revell) wrote :

Thanks Stub.

So, is this separate from a normal account deactivation? If so, can we find out how many people are affected by this?

Revision history for this message
Stuart Bishop (stub) wrote :

There are about 1500 users with deactivated accounts. I have no way of knowing how many of these desire their accounts to be deactivated or not.

It should be possible for users to reactivate accounts using the password recovery workflow.

Revision history for this message
Guilherme Salgado (salgado) wrote :

The only place we set the account's status to DEACTIVATED is when the user clicks the 'Deactivate your account' link. At that time the user is also asked to provide a comment explaining why he wants the account closed and, once done, the account can't be used to login anymore.

Going through the password reset workflow will allow the user to login, but won't change the account's status, so the account would not be completely functional. I'm pretty sure all these users have chosen to deactivate their accounts, but we can see that a bunch (233) of them [1] have already gone through the reset password workflow in an attempt to reactivate them.

The two users mentioned above seem to have done that, and one of them (khalderon) even left a comment when deactivating his account:

 status | status_comment | password
--------+-----------------------------------------------------+----------------------------------------------------------
     30 | I have no time to spend with this page. Bye for now | XXXX

 status | status_comment | password
--------+----------------+----------------------------------------------------------
     30 | | XXXXXX

[1] select account.id, password, status_comment from account left outer join accountpassword on accountpassword.account = account.id where status = 30 and password is not null;

Revision history for this message
Curtis Hovey (sinzui) wrote :

Oh good. This relates to, and answers, Bug 246320 that I filed yesterday. I'll take this bug since I looked into it yesterday. As I understand this, we want reset password to change account status 30 to 20.

Curtis Hovey (sinzui)
Changed in launchpad:
assignee: nobody → sinzui-is
milestone: none → 1.99
status: New → Confirmed
Revision history for this message
Curtis Hovey (sinzui) wrote :

I have a branch for this in review. I do not think this fix is comprehensive though. My branch fixes the reset password scenario. I suspect claiming a profile may also be broken.

Changed in launchpad:
status: Confirmed → In Progress
Revision history for this message
Curtis Hovey (sinzui) wrote :

Fixed in RF 6657.

Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Curtis Hovey (sinzui) wrote :

Fix released in launchpad 1.99.

Changed in launchpad:
status: Fix Committed → Fix Released
Curtis Hovey (sinzui)
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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