ifupdown not removed during upgrade from 17.04?

Asked by Sebastian Mares on 2017-11-09

If I understand correctly, netplan is supposed to replace ifupdown and with 17.10, it should be installed by default while ifupdown not. However, after doing an upgrade from 17.04 to 17.10, I have both packages installed.

My /etc/network/interfaces contains configuration for static IPs and ifupdown-migrate gives me

eth0: method static is not supported

I also have the problem that services such as nginx or dovecot that are configured to bind to a specific IP defined in /etc/network/interfaces don't start at boot with the error in syslog that they cannot bind to the address specified. Manually starting the services after boot however works. Starting postfix that is also set to bind to a dedicated IP doesn't even work manually, it just quits after start. There is nothing written in syslog or mail.log though. Starting via systemctl gives OK but the process is not started. systemctl status tells me it exited.

Am I supposed to write a netplan config myself? Why do I have both netplan and ifupdown? Is the /etc/network/interfaces even being read? It must be because the IPs defined there are up.

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu plan Edit question
Assignee:
No assignee Edit question
Last query:
2017-11-10
Last reply:
2017-11-10
Manfred Hampl (m-hampl) said : #1

According to https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes the switch from ifupdown to netplan is only done for new installs, but not for upgraded systems.

Sebastian Mares (smares) said : #2

Wondering why everything network related is screwed up then. I also tried setting overrides for dovecot and nginx to start after network.target or network-online.target, but no luck.

Can you help with this problem?

Provide an answer of your own, or ask Sebastian Mares for more information if necessary.

To post a message you must log in.