Netplan does not allow greater that 8 nics to be configured

Bug #1748958 reported by Andrew Welham
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nplan (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

there is no crash or app report available
when you try to configure more than 8 nics netplan gives the following error and only configures the first 8

DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:device enp0s17 operstate is up, not replugging
DEBUG:netplan triggering .link rules for enp0s17
DEBUG:device enp0s8 operstate is up, not replugging
DEBUG:netplan triggering .link rules for enp0s8
DEBUG:device enp0s18 operstate is up, not replugging
DEBUG:netplan triggering .link rules for enp0s18
DEBUG:device enp0s16 operstate is up, not replugging
DEBUG:netplan triggering .link rules for enp0s16
DEBUG:device enp0s9 operstate is up, not replugging
DEBUG:netplan triggering .link rules for enp0s9
DEBUG:device lo operstate is unknown, not replugging
DEBUG:netplan triggering .link rules for lo
DEBUG:device enp0s10 operstate is up, not replugging
DEBUG:netplan triggering .link rules for enp0s10
DEBUG:device enp0s3 operstate is up, not replugging
DEBUG:netplan triggering .link rules for enp0s3
DEBUG:replug enp2s0: unbinding 0000:02:00.0 from /sys/bus/pci/drivers/e1000
DEBUG:replug enp2s0: rebinding 0000:02:00.0 to /sys/bus/pci/drivers/e1000
DEBUG:device enp0s19 operstate is up, not replugging

looking in the drivers directory you can see ni9 is on a different address
# ls -als /sys/bus/pci/drivers/e1000
total 0
0 drwxr-xr-x 2 root root 0 Jan 27 13:12 .
0 drwxr-xr-x 27 root root 0 Jan 27 13:02 ..
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:00:03.0 -> ../../../../devices/pci0000:00/0000:00:03.0
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:00:08.0 -> ../../../../devices/pci0000:00/0000:00:08.0
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:00:09.0 -> ../../../../devices/pci0000:00/0000:00:09.0
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:00:0a.0 -> ../../../../devices/pci0000:00/0000:00:0a.0
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:00:10.0 -> ../../../../devices/pci0000:00/0000:00:10.0
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:00:11.0 -> ../../../../devices/pci0000:00/0000:00:11.0
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:00:12.0 -> ../../../../devices/pci0000:00/0000:00:12.0
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:00:13.0 -> ../../../../devices/pci0000:00/0000:00:13.0
0 lrwxrwxrwx 1 root root 0 Jan 27 13:11 0000:02:00.0 -> ../../../../devices/pci0000:00/0000:00:19.0/0000:02:00.0

This has been found in ALpha 1 & 2 for desktop and Alpha 2 for server.
if the 9th nic is bought up manually using ifconfig it works

my netlan config file
# This file describes the network interfaces available on your system# For more information, see netplan(5).
network:
 version: 2
 renderer: networkd
 ethernets:
   enp0s3:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.0.3/24]
     gateway4: 192.168.0.1
     nameservers:
         addresses: [dnsserver1,dnsserver2]
   enp0s8:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.1.3/24]
     gateway4: 192.168.1.1
     nameservers:
         addresses: [dnsserver1,dnsserver2]
   enp0s9:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.2.3/24]
     nameservers:
         addresses: [dnsserver1,dnsserver2]
   enp0s10:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.3.3/24]
     nameservers:
         addresses: [dnsserver1,dnsserver2]
   enp0s16:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.4.3/24]
     nameservers:
         addresses: [dnsserver1,dnsserver2]
   enp0s17:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.5.3/24]
     nameservers:
         addresses: [dnsserver1,dnsserver2]
   enp0s18:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.6.3/24]
     nameservers:
         addresses: [dnsserver1,dnsserver2]
   enp0s19:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.7.3/24]
     nameservers:
         addresses: [dnsserver1,dnsserver2]
   enp2s0:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.8.3/24]
     nameservers:
         addresses: [dnsserver1,dnsserver2]

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

There's no reason for anything in netplan to care what the device is numbered '9'; and it's not even the last interface configured in the yaml file. This smells like a systemd bug.

Could you please attach the file that netplan generates in /run/systemd/network, as well as /var/log/syslog to see if systemd-networkd reports any error?

Thanks!

Changed in nplan (Ubuntu):
status: New → Incomplete
Revision history for this message
Andrew Welham (andreww-ubuntu) wrote :
Download full text (84.1 KiB)

I had rebuild my test vm since then, so I have included the new yaml file, it appears as before to the enp2 interfaces.
Looking at the files in /run/systemd/network directory all look good. However there as a delayed boot while setting up the interfaces

I've attached a syslog whihc was cleared just before reboot

01-netcfg.yaml

network:
 version: 2
 renderer: networkd
 ethernets:
   enp0s3:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.0.150/24]
     nameservers:
         addresses: [192.168.0.3,192.168.0.15]
   enp0s8:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.1.150/24]
     nameservers:
         addresses: [192.168.1.2,192.168.1.3]
   enp0s9:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.2.150/24]
     nameservers:
         addresses: [192.168.2.2,192.168.2.3]
   enp0s10:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.3.150/24]
     nameservers:
         addresses: [192.168.3.2,192.168.3.3]
   enp0s16:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.4.150/24]
     nameservers:
         addresses: [192.168.4.2,192.168.4.3]
   enp0s17:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.5.150/24]
     nameservers:
         addresses: [192.168.5.2,192.168.5.3]
   enp0s18:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.6.150/24,192.168.7.2/24]
     nameservers:
         addresses: [192.168.6.2,192.168.7.3,192.168.6.3,192.168.7.2]
   enp0s19:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.253.150/24]
     gateway4: 192.168.253.1
     nameservers:
         addresses: [192.168.253.3,192.168.253.3]
   enp2s0:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.9.150/24]
     gateway4: 192.168.9.1
     nameservers:
         addresses: [192.168.253.3,192.168.253.1]
   enp2s1:
     dhcp4: no
     dhcp6: no
     addresses: [192.168.10.150/24]
     gateway4: 192.168.10.1
     nameservers:
         addresses: [192.168.253.3,192.168.253.3]

::::::::::::::
10-netplan-enp0s10.network
::::::::::::::
[Match]
Name=enp0s10

[Network]
Address=192.168.3.150/24
DNS=192.168.3.2
DNS=192.168.3.3
::::::::::::::
10-netplan-enp0s16.network
::::::::::::::
[Match]
Name=enp0s16

[Network]
Address=192.168.4.150/24
DNS=192.168.4.2
DNS=192.168.4.3
::::::::::::::
10-netplan-enp0s17.network
::::::::::::::
[Match]
Name=enp0s17

[Network]
Address=192.168.5.150/24
DNS=192.168.5.2
DNS=192.168.5.3
::::::::::::::
10-netplan-enp0s18.network
::::::::::::::
[Match]
Name=enp0s18

[Network]
Address=192.168.6.150/24
Address=192.168.7.2/24
DNS=192.168.6.2
DNS=192.168.7.3
DNS=192.168.6.3
DNS=192.168.7.2
::::::::::::::
10-netplan-enp0s19.network
::::::::::::::
[Match]
Name=enp0s19

[Network]
Address=192.168.253.150/24
Gateway=192.168.253.1
DNS=192.168.253.3
DNS=192.168.253.3
::::::::::::::
10-netplan-enp0s3.network
::::::::::::::
[Match]
Name=enp0s3

[Network]
Address=192.168.0.150/24
DNS=192.168.0.3
DNS=192.168.0.15
::::::::::::::
10-netplan-enp0s8.network
::::::::::::::
[Match]
Name=enp0s8

[Network]
Address=192.168.1.150/24
DNS=192.168.1.2
DNS=192.168.1.3
::::::::::::::
10-netplan-enp0s9.network
::::::::::::::
[Match]
Name=enp0s9

[Network]
Address=192.168.2.150/24
DNS=192.168.2.2
DNS=192.168.2.3
::::::::::::::
1...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nplan (Ubuntu) because there has been no activity for 60 days.]

Changed in nplan (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.