There is definitely a "daemon-reload" happening in the same second when
the problem happens. So it is probably caused by a race condition:
Sep 5 05:55:40 MonacoSIT4 systemd[1]: Reloading.
Sep 5 05:55:40 MonacoSIT4 snapd[3467]: overlord.go:271: Acquiring state lock
file
Sep 5 05:55:40 MonacoSIT4 snapd[3467]: overlord.go:276: Acquired state lock
file
Sep 5 05:55:40 MonacoSIT4 dbus-daemon[3447]: [system] Successfully activated
service 'org.freedesktop.hostname1'
...
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <info> [1725530140.8525]
manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <info> [1725530140.8525]
manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <info> [1725530140.8526]
manager: Networking is enabled by state file
Sep 5 05:55:40 MonacoSIT4 dbus-daemon[3447]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0
pid=3448 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <info> [1725530140.8536]
settings: Loaded settings plugin: ifupdown
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-settings-plugin-ifupdown.so")
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <info> [1725530140.8536]
settings: Loaded settings plugin: keyfile (internal)
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <info> [1725530140.8536]
ifupdown: management mode: unmanaged
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <info> [1725530140.8538]
ifupdown: interfaces file /etc/network/interfaces doesn't exist
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8548]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens5f1np1.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8548]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens5f0np0.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8548]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens4f1np1.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8548]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens4f0np0.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8548]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens3f1np1.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8548]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens3f0np0.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8549]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens2f1np1.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8549]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens2f0np0.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8549]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens1f1np1.nmconnection": failed
to load connection: cannot access file: No such file or directory
Sep 5 05:55:40 MonacoSIT4 NetworkManager[3448]: <warn> [1725530140.8549]
keyfile: load:
"/run/NetworkManager/system-connections/netplan-ens1f0np0.nmconnection": failed
to load connection: cannot access file: No such file or directory
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2083129
Title:
[Lenovo Ubuntu 22.04.4 Bug] netplan static IP address assignment use
NetworkManager as renderer would be lost static ip
Status in netplan.io package in Ubuntu:
New
Status in network-manager package in Ubuntu:
Invalid
Status in netplan.io source package in Jammy:
New
Status in network-manager source package in Jammy:
Invalid
Bug description:
On Ubuntu 22.04.4, to configure a system to use static address assignment,
create a netplan configuration in the file, like
/etc/netplan/00-installer-config.yaml. After assigning the network
configuration abstraction renderer to NetworkManager not networkd in
/etc/netplan/00-installer-config.yaml, then we do warm reboot test, some of the
NIC interface lost their static ip in some reboot cycles when the rendered is
NetworkManager, but networkd as a renderer is works well, all NIC interfaces
can get their corresponding IP that configured in netplan confile file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2083129/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
