See http://en.wikipedia.beta.wmflabs.org/wiki/Special:Version
Specifically, MediaWiki's version says "1.26alpha (c32e5fd) 13:32, 12 August 2015" and Flow's says "1.1 (e62cb0b) 01:03, 12 August 2015". The current UTC time is 22:38, 13 August 2015, so MW core is about 33 hours behind and Flow about 46 hours.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Return super().main() when overriding AbstractSync.main() | mediawiki/tools/scap | master | +3 -3 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | bd808 | T109007 Beta cluster not updating MW code | |||
| Declined | None | T111062 Scap should abort early when Keyholder is not armed | |||
| Resolved | Krenair | T111064 Monitor keyholder on deployment-prep deployment servers |
The shared ssh-agent used for scap had not been given a key following the server restart yesteerday. Fixed with sudo -u keyholder env SSH_AUTH_SOCK=/run/keyholder/agent.sock ssh-add /etc/keyholder.d/mwdeploy_rsa. The password needed for the key can be found in deployment-puppetmaster.deployment-prep:/var/lib/git/labs/private/files/ssh/tin/mwdeploy_rsa.passphrase
Change 231442 had a related patch set uploaded (by BryanDavis):
Return super().main() when overriding AbstractSync.main()
Change 231442 merged by jenkins-bot:
Return super().main() when overriding AbstractSync.main()
That failed again for some random reason and @bd808 trick above fixed it. I am wondering whether we could autoload the key when the server start.
Added the location of the passphrase to the keyholder docs: https://wikitech.wikimedia.org/w/index.php?title=Keyholder&type=revision&diff=175639&oldid=175543