[Labs-announce] Many instance reboots Tuesday, 2016-11-01 at 18:00 UTC

[Andrew Bogott]

This is now mostly done.

Unfortunately, there are quite a few instances with broken packages, 
full disks, etc. that I was unable to patch automatically, so I'm 
logging into them one-by-one and fixing things by hand.  I'm about 
half-way done with that, and I don't expect to have this done tonight, 
so the instances listed below should expect a reboot sometime in the 
next 24 hours or so.

I'll send another email when I'm well and truly done with this.

Instances still in need of patching:

deployment-zotero01
limn1
lsg-01
map
maps-tiles1
mediahandler-tests-static
mw-base
mw-expt
mwui
nomad
os-instance-control-01
os-instance-db-01
osmit-due
phab
phab-03
phab-tin
phabricator
phlogiston-3
pole
proofreadpage
reading-web-research
reading-web-staging-3
relforge-search
sentry-alpha
sm-puppetmaster-trusty2
sm1
snuggle-en
st-trusty
striker-deploy03
striker-uwsgi02
telnet2
toolsbeta-puppetmaster3
trusty
trusty-update
undeltest
utrs-secondary
vem
vem2
vicky
visualeditor-switch
visualeditor-test
wbdocs
wikidata-suggester
wikimania-scholarships
wm-bot
xtools-live01




On 10/26/16 3:32 PM, Andrew Bogott wrote:
> In order to address a security issue, we are patching and rebooting 
> many physical Labs hosts.  The final round of reboots will take place 
> on Tuesday, beginning at 18:00 UTC (11:00 AM San Francisco time).
>
> All virtualization hosts except for labvirt1001 will be rebooted on 
> Tuesday.  That means that all instances EXCEPT those on labvirt1001* 
> will be rebooted.  In general a reboot involves 5-20 minutes of 
> downtime for the instance; in unusual cases a second reboot may be 
> necessary.
>
> The labs operations team will manage tool queues and services, so 
> interruption to services on Tools should be minimal.
>
> Apologies in advance for the downtime.
>
> -Andrew
>
>