Bytemark Cloud: Imaging Machines with an SSH Key

Expected resolution: 2 Jun 2017, 13:16 UTC
Return to issues
Issue status: Resolved Date:

2 Jun 2017
12:48 UTC

Posted by:

Timothy Frew

Our developers have been working hard to fix this issue and that has now been rolled out to our live system. You can now continue to image new machines and supply an SSH key during this process.

Thank you for your patience with this matter, should you continue to experience any problems then please do contact our support team.

Issue status: Resolved Date:

2 Jun 2017
12:48 UTC

Posted by:

Patrick Cherry

This problem has now been fixed, and confirmed working.

This error occurred following an upgrade to our appliance server, moving its process supervision from sysvinit to systemd. Rolling back to sysvinit supervision has resolved this problem whilst we work on a longer term fix.

Issue status: Investigating Date:

31 May 2017
15:20 UTC

Posted by:

Timothy Frew

Cloud services are currently live and working well, Imaging new machines works well apart from if you provide an SSH key. If you desperately need to image a machine using an SSH key, we would advise copying your public key to the server post installation. You can do this by using ssh-copy-id admin/root@server.group.user.uk0.bigv.io then disable password login via SSH config.

We'll update this post, as and when we have more information.

Return to issues

Issue still not addressed? Please contact support.