Question
eth0 not getting configured correctly after upgrade.
- Posted on September 15, 2023
- DigitalOcean DropletsNetworkingUbuntu 16.04Ubuntu 18.04Ubuntu 20.04
Asked by admin
I recently upgraded an old droplet from 16.04 ->18.04 ->20.04. The first upgrade went fine but something broke networking after the second update. The droplet no-longer sets its IPV4 address/gateway correctly after a reboot. If I manually configured it using the recovery console everything works fine but it’s obviously broken again on next reboot.
In other words I need to run the following commands before I can use the droplet.
ifconfig eth0 <ipv4 address> netmask 255.255.240.0 up
ip route add default via <gateway>
I thought it might be an issue with cloud-init since I think that is meant to handle configuring the droplet and there was an exception logged in /var/log/cloud-init.log:
2023-09-15 23:16:30,093 - util.py[DEBUG]: Getting data from <class 'cloudinit.sources.DataSourceDigitalOcean.DataSourceDigitalOcean'> failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 1018, in find_source
if s.update_metadata_if_supported(
File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 904, in update_metadata_if_supported
result = self.get_data()
File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceDigitalOcean.py", line 48, in get_data
(is_do, droplet_id) = self._get_sysinfo()
File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceDigitalOcean.py", line 45, in _get_sysinfo
return do_helper.read_sysinfo()
File "/usr/lib/python3/dist-packages/cloudinit/sources/helpers/digitalocean.py", line 194, in read_sysinfo
vendor_name = util.read_dmi_data("system-manufacturer")
AttributeError: module 'cloudinit.util' has no attribute 'read_dmi_data'
2023-09-15 23:16:30,096 - main.py[DEBUG]: No local datasource found
I tried upgrading cloud-init to the latest version but that didn’t seem to do anything. Didn’t even resolve the error message.
Any ideas? Should I just cut my loses and copy the data over to a new droplet?
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!
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.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Get started for free
Enter your email to get $200 in credit for your first 60 days with DigitalOcean.
New accounts only. By submitting your email you agree to our Privacy Policy.
Heya,
I think it’s possible it is related to cloud-init, yes.
First, try reconfiguring it:
It’s possible that there’s stale data or configurations present from the older version of the OS. You can clean these up:
Then reboot the droplet to see if it resolves the networking issue.
If that doesn’t worrk, we can try something else.
DigitalOcean uses a specific cloud-init configuration for its droplets. Check the
/etc/netplan/directory for any.yamlconfiguration files and make sure they are correct. It should look something like:If you make any changes, apply them using:
Then, reboot to see if this resolves the issue.
If none of that work, I’ll recommend contacting DigitalOcean Support. They should be able to assist you with the network issue.