deploy1001 and deploy2001 are going to be replaced with new hardware as part of regular hardware refresh due to age
- deploy1002 setup T265653
- deploy2002 setup T264633
Since we are migrating all servers to Buster, it makes sense to directly install Buster.
- install buster on deploy1002
- install buster on deploy2002
- apply deployment server role on deploy1002
- temp remove deploy1002 from scap dsh groups to avoid errors for deployers
- fix: E: Package 'mysql-client' has no installation candidate (/Profile::Mediawiki::Deployment::Server/File[/usr/local/sbin/fix-staging-perms]: Dependency Package[mysql-client] has failures: true)
- fix scap bootstrap issue / run scap deploy --init (worked around with rsync/puppet, scap-sync-master and scap pull)
(/usr/bin/scap deploy --init fails when running on non-active servers)
- apply deployment server role on deploy2002
- re-add both servers to scap DSH groups
- sync repo data over from old servers to new servers
- schedule and announce switchover date
- actually switch active server in puppet, check the other servers have the "warning MOTD" to tell devs what is and what isn't the right server