journalctl on a failed laptop is showwing a lot of throttling logs from NetworkManager such as :
stat change: unavilable -> disconnected (reason 'carrier changed', sys-iface-state: 'managed')
This makes be believe that networkd and NetworkManager are attempting to grab management of the NIC multiple times throughout boot thereby rendering the network and carrier down.
I see cloud-init reflecting the 'down' carrier state of en0s31f6 in the 'init' timeframe too by
2. The second interesting configuration 'error' to be aware of is that netplan doesn't like the 644 permissions on the rendered /etc/netplan/01-network-manager-all.yaml.
** (process:2015): WARNING **: 03:18:08.594: Permissions for /etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration should NOT be accessible by others.
journalctl on a failed laptop is showwing a lot of throttling logs from NetworkManager such as :
stat change: unavilable -> disconnected (reason 'carrier changed', sys-iface-state: 'managed')
This makes be believe that networkd and NetworkManager are attempting to grab management of the NIC multiple times throughout boot thereby rendering the network and carrier down.
I see cloud-init reflecting the 'down' carrier state of en0s31f6 in the 'init' timeframe too by
Cloud-init v. 23.1.1-0ubuntu1 running 'init' at Tue, 07 Mar 2023 03:17:56 +0000. Up 62.47 seconds. +++++++ +++++++ +++++++ +Net device info+++ +++++++ +++++++ +++++++ +++++ -----+- ------+ ------- ----+-- ------- --+---- ---+--- ------- ------- --+ -----+- ------+ ------- ----+-- ------- --+---- ---+--- ------- ------- --+ -----+- ------+ ------- ----+-- ------- --+---- ---+--- ------- ------- --+
ci-info: +++++++
ci-info: +------
ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
ci-info: +------
ci-info: | enp0s31f6 | False | . | . | . | 6c:24:08:9e:54:e6 |
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . |
ci-info: | lo | True | ::1/128 | . | host | . |
ci-info: | wlp0s20f3 | False | . | . | . | 38:7a:0e:2d:d0:bb |
ci-info: +------
2. The second interesting configuration 'error' to be aware of is that netplan doesn't like the 644 permissions on the rendered /etc/netplan/ 01-network- manager- all.yaml.
** (process:2015): WARNING **: 03:18:08.594: Permissions for /etc/netplan/ 01-network- manager- all.yaml are too open. Netplan configuration should NOT be accessible by others.
Full log paste: https:/ /dpaste. com/APGZH46PN