Control issue affecting York heads

Expected resolution: 23 Aug 2016, 20:00 UTC
Return to issues
Issue status: Resolved Date:

23 Aug 2016
18:22 UTC

Posted by:

Paul Cammish

All Cloud Servers should have returned to normal.

Issue status: Investigating Date:

23 Aug 2016
17:24 UTC

Posted by:

Paul Cammish

Cloud Servers on heads 52, 54, 55 & 58 should now be fine again, and control has been regained without any reboots.

Head57 however required a reboot of the head itself to rectify the problem, which meant all the Cloud Servers on it also needed to be rebooted as they could not be migrated. All of these servers are all in the process of rebooting now, so should be up shortly if not already.

All Cloud Servers should be controllable again as normal.

Issue status: Investigating Date:

23 Aug 2016
16:46 UTC

Posted by:

Paul Cammish

Some York heads (52, 53, 54, 55, 57 & 58) have become disconnected from the brain controller and are currently failing to reconnect.

This isn't affecting the VMs themselves, but it does mean that the affected VMs are not controllable from the panel - start, stop or VNC console notably affected.


Update: The guests on head53 were rebooted as an unintentional side effect of the ongoing work to get it to communicate with the brain. All affected Cloud Servers should now be back up, and working normally.

Cloud Servers on heads 52, 54, 55, 57 & 58 are still up and running normally, although are not currently controllable, so cannot be restarted/changed via the control panel at present.

Issue status: Investigating Date:

23 Aug 2016
16:15 UTC

Posted by:

Bytemark Engineer

Some York heads (52, 53, 54, 55, 57 & 58) have become disconnected from the brain controller and are currently failing to reconnect.

This isn't affecting the VMs themselves, but it does mean that the affected VMs are not controllable from the panel - start, stop or VNC console notably affected.

Return to issues

Issue still not addressed? Please contact support.