Steps to replicate the issue (include links if applicable):
What happens?: The changes are not saved
What should have happened instead?: Edit should be saved
Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):
Other information (browser name/version, screenshots, etc.):
Change #1302184 had a related patch set uploaded (by Ahmon Dancy; author: Ahmon Dancy):
[operations/mediawiki-config@master] Revert "beta: Add deployment-db15 to db-labs config at weight 0"
Change #1302184 merged by jenkins-bot:
[operations/mediawiki-config@master] Revert "beta: Add deployment-db15 to db-labs config at weight 0"
I found the /usr/local/bin/wmf-beta-update-databases.py script stalled on deployment-deploy04. Doing some debugging using strace I found it blocked on a SELECT MASTER_GTID_WAIT('0-2886731158-528703649', 300); query to deployment-db14. I logged into deployment-db14 and ran show slave status\G there and I see:
Query caused different errors on master and slave. Error on master: message (format)='Cannot load from %s.%s. The table is probably corrupted' error code=1728 ; Error on slave: actual message='no error', error code=0. Default database: 'repltest'. Query: 'drop database repltest'
I created the repltest table last week while testing replication when setting up deployment-db15. I'm not sure why this made db14 unhappy but I will try refreshing it.
Change #1302202 had a related patch set uploaded (by Ahmon Dancy; author: Ahmon Dancy):
[operations/mediawiki-config@master] beta: Replace deployment-db14 with deployment-db15
Change #1302202 merged by jenkins-bot:
[operations/mediawiki-config@master] beta: Replace deployment-db14 with deployment-db15