[focal] nm-online -s --timeout=10 timeout every time

[Alex Tu]

Also created bug on upstream : https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398

This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'."
And cloud-init.service is counting on this service for network status.

So this issue will finally cause MaaS deploying failed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service]
ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8
Uname: Linux 5.4.0-1002-oem x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
Date: Wed Mar 25 12:43:13 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09
IfupdownConfig: source /etc/network/interfaces.d/*.cfg
InstallationDate: Installed on 2020-03-25 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40
IpRoute:
 default via 192.168.101.1 dev eno1 proto static metric 100
 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200
 169.254.0.0/16 dev eno1 scope link metric 1000
 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100
NetDevice.bonding_masters:
 Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device

 X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME
 netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 1585111177 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.22.10 connected starting full enabled disabled disabled enabled enabled

[Alex Tu (alextu)]

It seems this issue only happens to machine which eth port be renamed as eno1.
It can not be reproduced on another machine which eth port be renamed to enp2s0.

[Sebastien Bacher (seb128)]

@Alex, could you upstream it to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/

[Alex Tu (alextu)]

sure, it's there https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398

[Lee Trager (ltrager)]

NetworkManager isn't installed in the base MAAS Focal image.

Are you using the default image from images.maas.io?

What cloud-init user-data are you sending to the install?

Have you modified the preseed file at all?

[Alex Tu (alextu)]

No, there's no desktop MaaS Focal image yet.

For auto sanity of device team and SRU verification of certification team, we convert OEM iso to MaaS compatible image by script.

It works well on bionic but failed on Focal by LP: #1868915 and LP: #1869181.

For this issue, it looks upstream accepted it as an upstream bug.

[Sebastien Bacher (seb128)]

@Alex, the issue seems rather specific and having to do with rfkill being used, is it really critical for OEM or does the status needs to be updated? Could you give more details on the concrete case you need to get resolved? (or worked around)

[Yuan-Chen Cheng (ycheng-twn)]

no activity for 2 years.