[Bug 1930738] Re: network configuration failed on reboot

Dan Streetman 1930738 at bugs.launchpad.net
Fri Jul 23 13:22:34 UTC 2021


** Description changed:

+ [impact]
+ 
+ number of statically defined addresses for an interface in systemd-
+ networkd is limited
+ 
+ [test case]
+ 
+ Note: this only occurs in a container; this is not reproducable in a VM
+ or bare metal.
+ 
+ Configure netplan with the attached yaml file (TBD: attach)
+ 
+ enable debug for systemd-networkd
+ 
+ reboot the system and check the journalctl output to see if any errors
+ were reported for systemd-networkd, e.g.:
+ 
+ $ journalctl -b -u systemd-networkd | grep 'could not set'
+ Jul 23 13:16:52 lp1930738-b systemd-networkd[189]: eth0: could not set address: Connection timed out
+ ...
+ 
+ Note that a restart of systemd-networkd may successfully complete
+ setting up all addresses, so the journal should be checked for errors
+ instead of only checking for configured addresses
+ 
+ [regression potential]
+ 
+ possible failure to correctly apply all statically defined interfaces
+ 
+ [scope]
+ 
+ this is needed in f and b
+ 
+ this is fixed upstream with commits
+ 628f08b66d43d1947b03419409d817d28eb47321 and PR 16982 which are included
+ in v246 and later, so this is fixed in h and later
+ 
+ [original description]
+ 
  This issue was reported at
  https://github.com/systemd/systemd/issues/17012
  
  **Used distribution**
-  > Ubuntu 20.04.1 LTS
- 
+  > Ubuntu 20.04.1 LTS
  
  **systemd version the issue has been seen with**
  > 245.4-4ubuntu3.2
  
  **Issue details**
  I configured 255 IPv4 address (including primary IP) using netplan but when the server restart, it time out on configuring the interface.  If I limit total IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.
  
  Below are my configurations and error logs.
  
  **/etc/netplan/10-ens3.yaml**
  ```
  network:
-   version: 2
-   renderer: networkd
-   ethernets:
-     ens3:
-       dhcp4: no
-       addresses:
-         - 140.XX.XX.XX/23
-         - 103.XXX.XX.1/24
-         - 103.XXX.XX.2/24
-         - CONTINUED IP ADDRESS UPTO BELOW ...
-         - 103.XXX.XX.254/24
-       gateway4: 140.XX.XX.X
-       nameservers:
-         addresses: [1.1.1.1, 1.0.0.1]
-       routes:
-         - to: 169.254.0.0/16
-           via: 140.XX.XX.X
-           metric: 100
+   version: 2
+   renderer: networkd
+   ethernets:
+     ens3:
+       dhcp4: no
+       addresses:
+         - 140.XX.XX.XX/23
+         - 103.XXX.XX.1/24
+         - 103.XXX.XX.2/24
+         - CONTINUED IP ADDRESS UPTO BELOW ...
+         - 103.XXX.XX.254/24
+       gateway4: 140.XX.XX.X
+       nameservers:
+         addresses: [1.1.1.1, 1.0.0.1]
+       routes:
+         - to: 169.254.0.0/16
+           via: 140.XX.XX.X
+           metric: 100
  ```
  The above config works if I run `netplan apply` but when I reboot, it does not work.
  
  **networkctl**
  ```
- IDX LINK TYPE     OPERATIONAL SETUP    
-   1 lo   loopback carrier     unmanaged
-   2 ens3 ether    routable    failed   
+ IDX LINK TYPE     OPERATIONAL SETUP
+   1 lo   loopback carrier     unmanaged
+   2 ens3 ether    routable    failed
  
  2 links listed.
  ```
  
  **/etc/systemd/system/systemd-networkd.service.d/override.conf**
  ```
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  ```
  
  **systemctl status systemd-networkd.service**
  ```
  ● systemd-networkd.service - Network Service
-      Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled-runtime; vendor preset: enabled)
-     Drop-In: /etc/systemd/system/systemd-networkd.service.d
-              └─override.conf
-      Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
-        Docs: man:systemd-networkd.service(8)
-    Main PID: 346 (systemd-network)
-      Status: "Processing requests..."
-       Tasks: 1 (limit: 1074)
-      Memory: 3.8M
-      CGroup: /system.slice/systemd-networkd.service
-              └─346 /lib/systemd/systemd-networkd
+      Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled-runtime; vendor preset: enabled)
+     Drop-In: /etc/systemd/system/systemd-networkd.service.d
+              └─override.conf
+      Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
+        Docs: man:systemd-networkd.service(8)
+    Main PID: 346 (systemd-network)
+      Status: "Processing requests..."
+       Tasks: 1 (limit: 1074)
+      Memory: 3.8M
+      CGroup: /system.slice/systemd-networkd.service
+              └─346 /lib/systemd/systemd-networkd
  
  Sep 10 19:47:03 test-server systemd-networkd[346]: NDISC: Sent Router Solicitation, next solicitation in 7s
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: No RA received before link confirmation timeout
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Invoking callback for 'timeout' event.
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Sent Router Solicitation, next solicitation in 15s
  Sep 10 19:47:23 test-server systemd-networkd[346]: Assertion 'm->sealed' failed at src/libsystemd/sd-netlink/netlink-message.c:582, function netlink_message_read_internal(). Ignoring.
  Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Could not set address: Connection timed out
  Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Failed
  Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: State changed: configuring -> failed
  Sep 10 19:47:23 test-server systemd-networkd[346]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
  Sep 10 19:47:23 test-server systemd-networkd[346]: NDISC: Stopping IPv6 Router Solicitation client
  ```

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu Bionic)
       Status: New => In Progress

** Changed in: systemd (Ubuntu Focal)
       Status: New => In Progress

** Changed in: systemd (Ubuntu)
       Status: Incomplete => Fix Released

** Changed in: systemd (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: systemd (Ubuntu Bionic)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Focal)
     Assignee: (unassigned) => Dan Streetman (ddstreet)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930738

Title:
  network configuration failed on reboot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  number of statically defined addresses for an interface in systemd-
  networkd is limited

  [test case]

  Note: this only occurs in a container; this is not reproducable in a
  VM or bare metal.

  Configure netplan with the attached yaml file (TBD: attach)

  enable debug for systemd-networkd

  reboot the system and check the journalctl output to see if any errors
  were reported for systemd-networkd, e.g.:

  $ journalctl -b -u systemd-networkd | grep 'could not set'
  Jul 23 13:16:52 lp1930738-b systemd-networkd[189]: eth0: could not set address: Connection timed out
  ...

  Note that a restart of systemd-networkd may successfully complete
  setting up all addresses, so the journal should be checked for errors
  instead of only checking for configured addresses

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  this is needed in f and b

  this is fixed upstream with commits
  628f08b66d43d1947b03419409d817d28eb47321 and PR 16982 which are
  included in v246 and later, so this is fixed in h and later

  [original description]

  This issue was reported at
  https://github.com/systemd/systemd/issues/17012

  **Used distribution**
   > Ubuntu 20.04.1 LTS

  **systemd version the issue has been seen with**
  > 245.4-4ubuntu3.2

  **Issue details**
  I configured 255 IPv4 address (including primary IP) using netplan but when the server restart, it time out on configuring the interface.  If I limit total IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.

  Below are my configurations and error logs.

  **/etc/netplan/10-ens3.yaml**
  ```
  network:
    version: 2
    renderer: networkd
    ethernets:
      ens3:
        dhcp4: no
        addresses:
          - 140.XX.XX.XX/23
          - 103.XXX.XX.1/24
          - 103.XXX.XX.2/24
          - CONTINUED IP ADDRESS UPTO BELOW ...
          - 103.XXX.XX.254/24
        gateway4: 140.XX.XX.X
        nameservers:
          addresses: [1.1.1.1, 1.0.0.1]
        routes:
          - to: 169.254.0.0/16
            via: 140.XX.XX.X
            metric: 100
  ```
  The above config works if I run `netplan apply` but when I reboot, it does not work.

  **networkctl**
  ```
  IDX LINK TYPE     OPERATIONAL SETUP
    1 lo   loopback carrier     unmanaged
    2 ens3 ether    routable    failed

  2 links listed.
  ```

  **/etc/systemd/system/systemd-networkd.service.d/override.conf**
  ```
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  ```

  **systemctl status systemd-networkd.service**
  ```
  ● systemd-networkd.service - Network Service
       Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled-runtime; vendor preset: enabled)
      Drop-In: /etc/systemd/system/systemd-networkd.service.d
               └─override.conf
       Active: active (running) since Thu 2020-09-10 19:46:58 UTC; 1min 36s ago
         Docs: man:systemd-networkd.service(8)
     Main PID: 346 (systemd-network)
       Status: "Processing requests..."
        Tasks: 1 (limit: 1074)
       Memory: 3.8M
       CGroup: /system.slice/systemd-networkd.service
               └─346 /lib/systemd/systemd-networkd

  Sep 10 19:47:03 test-server systemd-networkd[346]: NDISC: Sent Router Solicitation, next solicitation in 7s
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: No RA received before link confirmation timeout
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Invoking callback for 'timeout' event.
  Sep 10 19:47:11 test-server systemd-networkd[346]: NDISC: Sent Router Solicitation, next solicitation in 15s
  Sep 10 19:47:23 test-server systemd-networkd[346]: Assertion 'm->sealed' failed at src/libsystemd/sd-netlink/netlink-message.c:582, function netlink_message_read_internal(). Ignoring.
  Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Could not set address: Connection timed out
  Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: Failed
  Sep 10 19:47:23 test-server systemd-networkd[346]: ens3: State changed: configuring -> failed
  Sep 10 19:47:23 test-server systemd-networkd[346]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
  Sep 10 19:47:23 test-server systemd-networkd[346]: NDISC: Stopping IPv6 Router Solicitation client
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+subscriptions




More information about the foundations-bugs mailing list