Description of problem:
NetworkManager-wait-online.service is occasionally completing (aka Started) before network connectivity is established, thus allowing systemd to reach the network-online.target before connectivity has been established.
Customer use autofs and LDAP heavily and depend on the network connectivity being established before those services are brought up. When network connectivity is not up and autofs is started, the host is unable to properly boot.
Version-Release number of selected component (if applicable):
Activate NetworkManager-wait-online.service and boot.
if customer override the NetworkManager-wait-online.service to execute `ExecStart=/usr/bin/nm-online --timeout 30` instead of `ExecStart=/usr/bin/nm-online -s --timeout 30`, the issue no longer occurs.
We have a bug open on upstream with same issue.
Created attachment 1356761 [details]
[PATCH] device: make carrier-wait-timeout configurable per device
I think this should be fixed now upstream:
working well in CI now
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.