New droplet from an existing snapshot misses a network interface (Centos 6 x64)

February 22, 2013 3.5k views
Re, I did a snapshot of my system, then created a new droplet using the snapshot and ended up without eth0. Running CentOS 6 x64. Could be completely unrelated, but there's a SUSE customer with a missing network interface as well: http://digitalocean.uservoice.com/forums/136585-digital-ocean/suggestions/3639542-put-a-priority-on-fixing-your-32-bit-suse-image
4 Answers
P.S. "ifconfig -a" showed eth1, so I manually configured it with IP/broadcast/mask and that worked. However, this means that I cannot use the snapshot (and I tried creating it twice) for automatic deployment.
I would get in touch with DO's support department directly. I've not had any issues with snapshots or backups missing configurations, so it could simply be a blip in the system, or it could be a more widespread failure during the restoration. Either way, they should be able to help you directly via ticket,
Thanks. Up until yesterday I have also not experienced any problems, having created and restored numerous snapshots of Centos 6. This is the first time (and, as luck would have it, a snapshot of the most configured and complete system) that the network configuration wasn't properly restored.

For those who happen to come across this issue, follows are some basic steps to configure networking:

1) run "ifconfig -a"
1a) take note of the available "eth" interface and of its HWaddr (MAC) address
2) go to "/etc/sysconfig/network-scripts" and check for "ifcfg-ethX" (where X is the interface number from 0 to n) script.
2a) it exists but the number does not match the "eth" interface that you got from step 1a), then rename it to "ifcfg-eth[proper interface number]", edit the file and replace the information inside (DEVICE, HWADDR, IPADDR, NETMASK and GATEWAY fields".
2a) if it doesn't exist, then create it with the following content:

DEVICE="eth[proper interface number]"
HWADDR=XX:XX:XX:XX:XX:XX
IPADDR=192.XX.XX.XX
BOOTPROTO=none
ONBOOT="yes"
DNS1=8.8.8.8
NETMASK=255.255.255.0
GATEWAY=192.XX.XX.XX
PREFIX=24
TYPE=Ethernet
NM_CONTROLLED="yes"

3) reboot and profit.
The OpenSUSE image does have a few issues and that's why we've taken it down for maintenance. Some of the smaller less supported distros need a few updates however CentOS and Ubuntu are the most popular and should be pretty rock solid.

The issue that you ran into is very surprising and if you open a ticket about it we can move it to engineering and dive deeper into it to see if the problem recurs.
Have another answer? Share your knowledge.