Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

nm-1-8 introduced a bug, that is fixed upstream in the meantime:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=9ad8010fe0c42291580e4a801ed85947ae660d38


The effect is, if you have any connections for software devices (e.g. VLAN), that don't autoactivate right away, start-up complete is wrongly blocked. Consequently, NetworkManager-wait-online.service blocks for 30 seconds before it fails with timeout.

Fixed upstream already and will be consequently fixed in RHEL-7.5.

At the moment, still unfixed in RHEL-7.4

reproducer, is to create any connection for a software device (e.g. vlan or bridge), that doesn't autoactivate. Note how NM-w-o times out due to that after 30 seconds.

If you don't have the connection for a software device (or if it actually autoconnects on start), note that NM-w-o succeeds.


Also note, that you don't need to actually use NetworkManager-wait-online.service to reproduce it.
Just restart NM, and call
  /usr/bin/nm-online -s -q --timeout=30
-- which is what NM-w-o does.

Test running on daily bases.

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