[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2023-06-09 Thread Nick Rosbrook 
According to the reporter, this issue was not observed in Ubuntu 21.04
forward. I do not think there is a strong case for addressing this in
focal or bionic.

** Changed in: systemd (Ubuntu Bionic)
   Status: Incomplete => Won't Fix

** Changed in: systemd (Ubuntu Focal)
   Status: Incomplete => Won't Fix

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Invalid
Status in systemd source package in Bionic:
  Won't Fix
Status in systemd source package in Focal:
  Won't Fix

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 (10-test.yaml)

  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  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

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [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 etherroutablefailed

  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-08-18 Thread Ubuntu Foundations Team Bug Bot 
The attachment "sd-netlink-make-timeout-message-sealed.patch" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Focal:
  Incomplete

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 (10-test.yaml)

  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  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

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [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 etherroutablefailed

  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-08-18 Thread Frank Villaro 
** Patch added: "sd-netlink-make-timeout-message-sealed.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+attachment/5518731/+files/sd-netlink-make-timeout-message-sealed.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Focal:
  Incomplete

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 (10-test.yaml)

  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  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

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [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 etherroutablefailed

  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:

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-08-04 Thread Dan Streetman 
** Changed in: systemd (Ubuntu Focal)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Focal:
  Incomplete

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 (10-test.yaml)

  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  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

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [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 etherroutablefailed

  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-08-03 Thread Frank Villaro 
Hi, Sorry for the late reply I didn't receive the notifications.

This problem happens on a "bare" environment: it's a simple server (IPv6
RA + v4 DHCP) with some IPv6 ranges assigned to the `lo` interface.

Don't hesitate if you need more info, although we don't reproduce the
bug anymore due to our backport

Cheers !

** Attachment added: "some logs"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+attachment/5515576/+files/logs1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Focal:
  Incomplete

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 (10-test.yaml)

  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  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

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [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 etherroutablefailed

  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-27 Thread Dan Streetman 
> There are more details regarding this issue and may be commit refs at 
> https://github.com/systemd/systemd/issues/17012

I'm aware of that as noted in my updates to the description, but that
doesn't actually fix this inside unprivileged containers, which is the
only place I can reproduce this.

Please provide a full journal log from a boot on your VPS that
reproduces this

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Focal:
  Incomplete

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 (10-test.yaml)

  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  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

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [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 etherroutablefailed

  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-27 Thread Deepika Maharjan 
I got this issue on a VPS from cloud provider. For me, this issue occurs
every time I restart the VPS. To access the server after restart, I
execute `netplan apply` command using web console/KVM.

Furthermore, this issue does not occurs in Ubuntu 21.04

There are more details regarding this issue and may be commit refs at
https://github.com/systemd/systemd/issues/17012

** Bug watch added: github.com/systemd/systemd/issues #17012
   https://github.com/systemd/systemd/issues/17012

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Focal:
  Incomplete

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 (10-test.yaml)

  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  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

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [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 etherroutablefailed

  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-27 Thread Dan Streetman 
** Attachment added: "10-test.yaml"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1930738/+attachment/5514117/+files/10-test.yaml

** 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)
+ Configure netplan with the attached yaml file (10-test.yaml)
  
  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked
  
  [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
  
  [other info]
  
  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't see
  any clear bug-related reason to change that behavior.
  
  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629
  
  [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 etherroutablefailed
  
  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-27 Thread Dan Streetman 
Deepika, Frank, is this happening for you inside an unprivileged
container, or some other environment?

I'm able to reproduce this in a container, but it appears still broken
with upstream systemd, so I'm confused by Frank's comment 2.  Also, it
isn't intermittent at all for me, so maybe you're seeing some other
problem.

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Focal:
  Incomplete

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 (10-test.yaml)

  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 systemd may be able to actually correctly set all addresses,
  but fails to communicate with netlink to determine the addresses are
  set, so just checking the output of 'ip a' is not enough, the systemd-
  networkd debug log should be checked

  [regression potential]

  possible failure to correctly apply all statically defined interfaces

  [scope]

  TBD, not fully fixed upstream

  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

  [other info]

  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't
  see any clear bug-related reason to change that behavior.

  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629

  [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 etherroutablefailed

  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-27 Thread Dan Streetman 
** 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
+ Note that systemd may be able to actually correctly set all addresses,
+ but fails to communicate with netlink to determine the addresses are
+ set, so just checking the output of 'ip a' is not enough, the systemd-
+ networkd debug log should be checked
  
  [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
  
  [other info]
  
  I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
  that changes the udev-related behavior of networkd-manager inside a
  container, which is not appropriate for SRU for this bug, as I don't see
  any clear bug-related reason to change that behavior.
  
  Additionally this requires the typo fix from commit
  4934ba2121d76229659939e19ab7d70a89446629
  
  [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 etherroutablefailed
  
  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-23 Thread Dan Streetman 
** 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
+ 
+ [other info]
+ 
+ I elided upstream commit d31f33e3c9f6ea3bdc873ee52f4398edbec74527 as
+ that changes the udev-related behavior of networkd-manager inside a
+ container, which is not appropriate for SRU for this bug, as I don't see
+ any clear bug-related reason to change that behavior.
+ 
+ Additionally this requires the typo fix from commit
+ 4934ba2121d76229659939e19ab7d70a89446629
  
  [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 etherroutablefailed
  
  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
  ```

** Changed in: systemd (Ubuntu Bionic)

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-23 Thread Dan Streetman 
** 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 etherroutablefailed   
+ IDX LINK TYPE OPERATIONAL SETUP
+   1 lo   loopback carrier unmanaged
+   2 ens3 etherroutablefailed
  
  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

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-21 Thread Deepika Maharjan 
From fresh installation of ubuntu, I simply configured one main and 255
IPv4 address from /24 subnet as mentioned on original post in
/etc/netplan/10-ens3.yaml and this issue occurs. Even tried Ubuntu
20.04.2 LTS, same issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete

Bug 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 etherroutablefailed   

  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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-21 Thread Dan Streetman 
can you provide steps to reproduce the problem?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete

Bug 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 etherroutablefailed   

  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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-07-20 Thread Frank Villaro 
Hi,

In our case a backport of the specific commit fixed the issue. I really
do think that this is (a rather difficult to reproduce) problem, which
the above commit fixes.

Cheers

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete

Bug 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 etherroutablefailed   

  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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1930738] Re: network configuration failed on reboot

2021-06-30 Thread Dan Streetman 
i can't reproduce this, and your log output looks like you have are
having problems with your ipv6 configuration, not ipv4. you'll need to
attach the full journal log if you still have this problem

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  Incomplete

Bug 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 etherroutablefailed   

  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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp