Page MenuHomePhabricator

GlobalRenameQueue: after rename, Special:CentralAuth gives an exception of type "Exception"
Closed, InvalidPublic


After renaming a user, I am unable to open CentralAuth on the user's former name. See

Event Timeline

Elfix raised the priority of this task from to Needs Triage.
Elfix updated the task description. (Show Details)
Elfix added a subscriber: Elfix.
Elfix claimed this task.

Hm, a few hours later, I can now access this page. Guess it was nothing.

Depending on how large the rename is, the database can be inconsistent during the process:

  1. Update user.user_name, officially changing the name of the user locally
  2. Update logging, image, and other tables. This can take some time depending on how active the user is
  3. Update centralauth's localnames.ln_name row, which is what Special:CentralAuth uses.

If 2 takes a long time and 3 hasn't happened yet, it's likely that Special:CentralAuth will throw an exception for the old name.