RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):
NetworkManager-1.8.0-9.el7.x86_64
autofs-5.0.7-54.px5.el7.x86_64


How reproducible:
Activate NetworkManager-wait-online.service and boot.


Additional info:
 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.
https://bugzilla.redhat.com/show_bug.cgi?id=1483343

Created attachment 1356761 [details]
[PATCH] device: make carrier-wait-timeout configurable per device

I think this should be fixed now upstream:

master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2becc0a0ac82834ea96898c17ec79cd038e6db54

nm-1-10: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=eb95d6bbbb6982dac78949368fc8b2512aa906bb

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.

https://access.redhat.com/errata/RHBA-2018:0778