Ubuntu 17.10 x64 image broken? (Not rebooting correctly on fresh install)

Droplet specs: 1 GB Memory / 25 GB Disk / AMS3 - Ubuntu 17.10 x64

I did a clean droplet rebuild using “Ubuntu 17.10 x64 base image” from DigitalOcean. Then I got an email with the password. I logged in via SSH, and was requested to change the password, so I entered a new pass. Then I immediately performed a reboot command via the shell, and the system doesn’t come online anymore.

I repeated this multiple times to test/confirm, but the system doesn’t get back online. The only way to access it is via DigitalOcean Console access, and then it shows only a loopback interface, no eth0 etc.

Is the default Ubuntu image of DigitalOcean broken?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

This is very odd. Unfortunately I was not able to recreate this issue in my own testing. Creating an Ubuntu 17.10 x64 droplet, logging in and completing the password update and then running a reboot resulted in the droplets I tested rebooting and coming back online as expected. Please open a support ticket so our team can take a closer look at what you’re seeing.

I got a response from ticket support. Because from a user perspective it is unexpected behavior, I post it here to help other users who have this situation:

This is the response from ticket support:

I did some testing with two Droplets - one with an SSH key and one without - but I haven’t been able to reproduce that problem, I’m afraid. The problem could be related to changing distributions when you rebuild the Droplet though. Rebuilding uses the same settings from when the Droplet was first created (CentOS, it seems, judging by your Droplet’s name), so if you’re changing distributions like this the better approach would be to create a new Droplet.

So rebuilding doesn't seem to work as expected when switching from distribution.