mwscript extensions/CentralAuth/maintenance/fixStuckGlobalRename.php --wiki=eswiki --logwiki=metawiki "Mega849" "Mega809"
That should work. If not, it may require using the --ignorestatus param; but let's try without it first.
As such, please run the above command as posted on terbium. Thanks.
I would prefer if someone who actually knows what is doing runs it, so it can be debugged properly. If I run it, I would just be running random commands :-)
I don't think this is blocked on Ops, as there are many devs with access to terbium who probably know a lot more about the process - so moving it to another column if that's ok!
The earliest log item I can find is from 2018-01-02T23:26:43 (Duplicate entry 'Mega809' for key 'user_name'; repeated two more times) but that's probably already a retry. I don't see anything related in the minute before that. Apparently the user got renamed, but the job failed before moving any of the data (making subsequent attempts fail when they tried to rename the user). No idea what caused it :(
Nevermind, this is not actually a rename job failure. Mega809 has an autocreate entry back from 20130801002629 so it is some kind of SUL inconsistency. Which means the rename job failed before doing anything (changing the username is the very first action), which means it should be safe to just usurp the username and restart the job.