Page MenuHomePhabricator

centralauth block failed with <centralauth-admin-lock-nonexistent>
Closed, ResolvedPublic


I tried to block about a minute before @M7 did it, but failed with the message: <centralauth-admin-lock-nonexistent>

Event Timeline

Matanya created this task.Jun 24 2015, 9:18 PM
Matanya raised the priority of this task from to Needs Triage.
Matanya updated the task description. (Show Details)
Matanya added a subscriber: Matanya.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 24 2015, 9:18 PM
Glaisher added a subscriber: Glaisher.

Looks like that message was added when locking was implemented but it got removed after somehow rECAUa996b1f977adfdb721c7d98fab1a37f120bc1a32

centralauth-state-mismatch should have appeared instead.

What happened here was, it only detected the conflict only after trying to update the db after even going through the pre-check of whether the account was locked. In the case of centralauth-state-mismatch, it's before attempting to update the db.

It was removed in Apparently it was only noticed that centralauth-admin-unhide-nonexistent was still in use then. I think we should change this one to also use state-mismatch message as a non-existent global account to reach adminLock() and adminUnlock() is very unlikely when compared to race conditions like this.

Change 239567 had a related patch set uploaded (by Glaisher):
Use 'centralauth-state-mismatch' message in adminLock() and adminUnlock()

Change 239567 merged by jenkins-bot:
Use 'centralauth-state-mismatch' message in adminLock() and adminUnlock()

Glaisher closed this task as Resolved.Sep 22 2015, 7:37 AM
Glaisher claimed this task.
Restricted Application added a subscriber: StudiesWorld. · View Herald TranscriptDec 18 2015, 2:48 PM
Restricted Application added a subscriber: TerraCodes. · View Herald TranscriptDec 15 2016, 4:20 PM