[Completion, Sun Aug 26 23:53:05 DST 2018]
All servers affected have been returned to service, with the majority having been rebooted without issue by 11:08.
The maintenance has concluded successfully, for the servers our update platform could reach. Servers that could not be reached by our update platform or servers that were listed as 'excluded' previously will have their updates scheduled separately, as needed.
[Update, Sun Aug 26 21:30:31 DST 2018]
We are now beginning this maintenance, and fully managed Centos 6+ servers (aside from those previously listed as excluded, and customer ID 2086) will be rebooted 5 at a time, starting now.
We'll keep you updated throughout the maintenance, and individual server owners will be updated as appropriate.
Date: Sunday, August 26, 2018
Time: 9:30PM - 11:30PM
Purpose of Work:
We will be updating kernels for, and rebooting all Centos 6 and Centos 7 servers under our management, excluding hypervisors, highly available clustered applications, and servers owned by customers with the following billing IDs:
This is to protect against the follow remote DOS exploit, that leverages vulnerabilities in the Linux kernel to deny services with any appropriately modified TCP packet: https://access.redhat.com/articles/3553061
Impact Of Work:
Customers whose servers are being updated may notice 2-8 minutes of downtime, typically. We will be monitoring for any server that takes longer than this to boot up and regain services.
Servers will be updated and rebooted 5 at a time.
We will let you know if the maintenance ends ahead of schedule, or else update you regarding the status of this maintenance at the end of the scheduled window, with further information being forwarded to specific customers, if required.
If you would prefer to schedule your server reboot to occur at a specific alternate time, and have confirmed that you have one of more Fully-Managed Centos 6 or 7 servers ( that do not meet the previously specified exclusion criteria ), please reach out to email@example.com, or submit a ticket via our helpdesk, and specify your desired alternate update time before the scheduled update time.