All reboots are now complete. Let us know if you see any new, unusual
behavior.
Tools users: non-continuous jobs were most likely killed by the
reboots. You will need to re-run things by hand if such services are
not managed by cron.
-Andrew
On 1/20/16 5:31 PM, Andrew Bogott wrote:
On 1/20/16 12:06 PM, Andrew Bogott wrote:
In response to a new kernel exploit revealed today, I will be
upgrading and rebooting all labs VMs today. We'll be running a
dist-upgrade on all reachable labs instances, then rebooting the virt
hosts (which will, in turn, reboot the associated labs vms.) Total
downtime for any given instance should only be 5-10 minutes, but you
will need to restart services and such after the restart.
Update -- getting staged for reboot is taking much longer than
expected. The reboots will most likely happen tomorrow 2016-12-21, at
around 17:00 UTC.
We'll do our best to ensure that tools survive the reboots -- more on
that as the day develops.
-Andrew
_______________________________________________
Labs-announce mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/labs-announce
_______________________________________________
Labs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/labs-l
