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.

+++ This bug was initially created as a clone of Bug #1856263 +++

See the log at https://bugzilla.redhat.com/show_bug.cgi?id=1856263#c7 .


what happens is that a profile with ipv4.method=manual gets activatated. Initially the device has no carrier, and NM quickly indicates "startup complete". Only 2 seconds later, the device gets carrier.

what should happen is that during activation, we should also have a pending-action while the device has no carrier.

this happens due to [2].

In the respective case ([1]) we have a profile "ens3" (75856aad-c9b9-41d7-b8fc-433c6372f521) with manual IPv4 address configuration (and ipv6.method=ignore).

Such a profile can activate already before the device has carrier. With [2], once the profile is activated and has only "carrier-wait" action pending, the device is considered ready.

  
[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/aae6846d20b4557d5642c2ed291a1b1a8c300b15
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1856263#c7



So, it behaves as implemented.

@bgalvani, do you think this is desired behavior? I tend to think yes because a profile with manual addresses doesn't need carrier, so why would it block startup-complete any longer?

This seems the intended behavior. NetworkManager-wait-online guarantees that network is configured and that services dependent on network can start. Services don't care about carrier state, they usually only need an address to bind to.

ok, thus closing as NOTABUG.