Last modified: 2014-07-22 08:30:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69485, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67485 - db error on beta labs "centralauth.renameuser_status' doesn't exist"
db error on beta labs "centralauth.renameuser_status' doesn't exist"
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
deployment-prep (beta) (Other open bugs)
unspecified
All All
: Normal major
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-03 18:06 UTC by Chris McMahon
Modified: 2014-07-22 08:30 UTC (History)
11 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris McMahon 2014-07-03 18:06:46 UTC
Seen at http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Sandbox
Comment 1 Tomasz W. Kozlowski 2014-07-03 18:12:19 UTC
Also affecting http://commons.wikimedia.beta.wmflabs.org/

    A database query error has occurred. This may indicate a bug in the software.
    
    Function: GlobalRenameUserStatus::getNames
    Error: 1146 Table 'centralauth.renameuser_status' doesn't exist (10.68.16.193)
Comment 2 Chris Steipp 2014-07-04 18:49:25 UTC
Was this resolved? It looks like the rename patch hasn't been reverted, but I'm authenticating to beta just fine (and the rename patch checks that table on logins).

Either the test ran during the merge and when update.php runs, or update.php wasn't run on beta for some reason?
Comment 3 Antoine "hashar" Musso (WMF) 2014-07-04 19:03:52 UTC
The database update only run once per hour, so I guess the patch introducing the new table has been introduced in between and original reported unluckily hit beta while the databases were up to date.
Comment 4 Greg Grossmeier 2014-07-07 17:21:18 UTC
So, obvious question: The schema change this represents has been made/will be made before the complaining code goes to production, right?
Comment 5 Kunal Mehta (Legoktm) 2014-07-07 18:31:44 UTC
So, about 5-10 minutes after I merged the patch into master, The DJ came on IRC and reported that the table was misssing, so I created it manually. I'm not sure why people were still seeing errors after that, maybe it got cached?

(In reply to Antoine "hashar" Musso from comment #3)
> The database update only run once per hour, so I guess the patch introducing
> the new table has been introduced in between and original reported unluckily
> hit beta while the databases were up to date.

CentralAuth doesn't support update.php because it's on a different database.

(In reply to Greg Grossmeier from comment #4)
> So, obvious question: The schema change this represents has been made/will
> be made before the complaining code goes to production, right?

Yeah, that was taken care of a while ago. It was bug 66446.
Comment 6 Antoine "hashar" Musso (WMF) 2014-07-22 08:30:16 UTC
Thank you Kunal =)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links