Page MenuHomePhabricator

eowikisource DB error caused problems with completion of a user rename on en.wikipedia
Closed, ResolvedPublic

Description

Author: seashanty

Description:
While fulfilling a CHU request at Wikipedia:Changing username/Simple (on en.wiki), I changed the username User:Avadakedavara to User:RaisRulez. This routine CHU/simple received an error message "This wiki has a problem...(Cannot contact the database server: Unknown database 'eowikisource' (10.0.6.49))".

Although the eowikisource issue has been resolved, the CHUs that took place on en.wiki during that time frame are not resolved.

The CHU process successfully changed the User:Avadakedavara contributions into User:RaisRulez contributions, and deleted the User:Avadakedavara account. However, the information on User:Avadakedavara and User talk:Avadakedavara was not transferred, and remain on those pages.

More importantly, User:Avadakedavara's transfer to User:RaisRulez was successful on en.wiki, but did not take place on the user's commonswiki and enwikiversity accounts.

The event still has not shown up on the User rename log.

This same issue and problems occurred when I changed User:Annhoang to User:YellowFlag. In this case, User:Annhoang transfer to User:YellowFlag was successful on en.wiki, but did not take place on the user's enwikiquote account.


Version: unspecified
Severity: normal

Details

Reference
bz26877

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 11:20 PM
bzimport set Reference to bz26877.
bzimport added a subscriber: Unknown Object (MLST).

bugs wrote:

Possibly related: bug 26136

From your report, seems the rename was incomplete by:
a) Not moving the user pages (not a big deal, can be done manually)
b) Not logging the action into the rename log.

Why would an enwiki rename "take place" on commonswiki or enwikiversity?

seashanty wrote:

disregard the rename on other wikis.

Isn't this yet another CentralAuth temporary DB problem?
Local renames do various checks on the centralauth database so perhaps something failed there?

(In reply to comment #1)

Possibly related: bug 26136

Oh, right, if I remember correctly the centralauth DB has been an inconsistent state for a while before the eo.source creation was completed, and this caused errors in the most unexpected places. I'd call this fixed then.