Quantcast
Channel: Active questions tagged ubuntu - Stack Overflow
Viewing all articles
Browse latest Browse all 6761

Problem with Netplan and Ubuntu 18.04 taking down our network after "netplan apply" command is run

$
0
0

We are trying to add additional IPs to our OVH server and whenever we apply the command "netplan apply" after making our yaml changes, the server completely goes offline. The network is down. This happens for about 10-15 minutes before it comes back on its own.

When i run a command to check the status of systemd-networkd i get the following:

● systemd-networkd.service - Network ServiceLoaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)Active: active (running) since Sun 2018-12-02 05:10:18 UTC; 26min agoDocs: man:systemd-networkd.service(8)Main PID: 40782 (systemd-network)Status: "Processing requests..."Tasks: 1 (limit: 8601)CGroup: /system.slice/systemd-networkd.service└─40782 /lib/systemd/systemd-networkdDec 02 05:10:18 servername systemd-networkd[40782]: eno1: Gained IPv6LLDec 02 05:10:18 servername systemd-networkd[40782]: Enumeration completedDec 02 05:10:18 servername systemd[1]: Started Network Service.Dec 02 05:10:18 servername systemd-networkd[40782]: eno2: Could not find udev device: No such deviceDec 02 05:10:18 servername systemd-networkd[40782]: eno2: FailedDec 02 05:10:18 servername systemd-networkd[40782]: Could not add new link, ignoring: No such deviceDec 02 05:10:18 servername systemd-networkd[40782]: lo: Link is not managed by usDec 02 05:10:18 servername systemd-networkd[40782]: eno1: DHCPv4 address [ip address]/24 via <my server ip address>    Dec 02 05:10:18 ns536095 systemd-networkd[40782]: eno1: ConfiguredDec 02 05:10:18 ns536095 systemd-networkd[40782]: eth0: Interface name change detected, eth0 has been renamed to eno2.    

It seems that it's trying to search for eno2 but that doesn't exist which causes the timing out and dropping of our network completely. All of our IPs are set on eno1. There is nothing for eno2 although the server does have that network card.

How can i solve this issue? Been trying to figure this out for the longest time. The yaml file is confirmed to be proper in the following format.

network:version: 2ethernets:    eno1:        dhcp4: true        addresses: [<Main IP>, <additional ip>]

any help would be greatly appreciated.


Viewing all articles
Browse latest Browse all 6761

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>