Dec 30 2019
I've just had to roll back from the Buster instance to the Jessie instance after reports of data corruption. Thankfully, I'd left the old instance running so a simple proxy redirection is all that was needed to switch back.
Dec 15 2019
I've tried to migrate most stuff over to a new instance, but I've still got everything pointing at the old instance while I test that everything hasn't broken horribly. At the moment, I've done a lift-and-shift of the PHP5 code in the vague hope nothing breaks, but obviously that's not the best approach.
Dec 5 2019
Pushed, tagged, and deployed to both prod and sandbox environments.
Oof, this was a silly one.
Will look at this when I get home from work.
Oct 28 2019
-db3 is trivial, as it's shut down already and is hanging around simply because I've not checked everything was moved away from it, which I really should do soon. -mwoauth has historically been a pain every time I've had to deal with it, but realistically shouldn't be an issue either.
Apr 11 2019
Mar 15 2019
Mar 15 13:43:50 accounts-db3 systemd: Stopping LSB: Start and stop the mysql database server daemon... Mar 15 13:43:50 accounts-db3 systemd: Failed to reset devices.list on /system.slice: Invalid argument Mar 15 13:43:50 accounts-db3 mysqld: 190315 13:43:50 [Note] /usr/sbin/mysqld: Normal shutdown Mar 15 13:43:50 accounts-db3 mysqld: 190315 13:43:50 [Note] Event Scheduler: Purging the queue. 0 events Mar 15 13:43:50 accounts-db3 mysqld: 190315 13:43:50 [Note] InnoDB: FTS optimize thread exiting. Mar 15 13:43:50 accounts-db3 mysqld: 190315 13:43:50 [Note] InnoDB: Starting shutdown... Mar 15 13:43:51 accounts-db3 mysqld: 190315 13:43:51 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool Mar 15 13:43:52 accounts-db3 mysqld: 190315 13:43:52 [Note] InnoDB: Shutdown completed; log sequence number 26725902627 Mar 15 13:43:52 accounts-db3 mysqld: 190315 13:43:52 [Note] /usr/sbin/mysqld: Shutdown complete Mar 15 13:43:52 accounts-db3 mysqld: Mar 15 13:43:52 accounts-db3 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Mar 15 13:43:52 accounts-db3 mysql: Stopping MariaDB database server: mysqld. Mar 15 13:43:52 accounts-db3 systemd: Stopped LSB: Start and stop the mysql database server daemon. Mar 15 13:43:54 accounts-db3 puppet-agent: (/Stage[main]/Openstack::Clientpackages::Mitaka::Jessie/Package[mysql-client-5.5]/ensure) created
Feb 24 2019
Feb 8 2019
Nov 19 2018
Oct 22 2018
Aug 10 2018
Assuming that's the case, can @Timeshifter (or anyone else) provide a link to some on-wiki consensus for this change?
This is getting a little off-topic here.
Jun 5 2018
May 2 2018
Feb 1 2017
Jan 24 2017
Jun 19 2016
account-creation-assistance also currently has (and continues to need - T61662 ) access to the XFF data from the web proxy.