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:
I see a bunch of warnings if there are operations ongoing and nmcli g is called.

I created a bunch of vlans and deleted the afterwards:
for i in {1..255}; do ip link add link eth1 name vlan.$i type vlan id $i; ip link set dev vlan.$i up; ip add add 30.0.0.$i/24 dev vlan.$i;done
and
for i in {1..255}; do ip link del vlan.$i;done

and during the delete I called nmcli g

with this output:
<snip>
(process:1700): GLib-GIO-WARNING **: gdbusobjectmanagerclient.c:1585: Processing InterfaceRemoved signal for path /org/freedesktop/NetworkManager/IP4Config/330 but no object proxy exists

(process:1700): GLib-GIO-WARNING **: gdbusobjectmanagerclient.c:1585: Processing InterfaceRemoved signal for path /org/freedesktop/NetworkManager/IP6Config/330 but no object proxy exists

(process:1700): libnm-WARNING **: no object known for /org/freedesktop/NetworkManager/Devices/279


(process:1700): libnm-WARNING **: no object known for /org/freedesktop/NetworkManager/Devices/302
<snip>

Version-Release number of selected component (if applicable):
1.8.0-4

The latter two are non-trivial to fix (will clone another bug), but should be disabled in RHEL builds.

The former two are a glib bug -- reassigning.

Proposed patches upstream:

https://bugzilla.gnome.org/show_bug.cgi?id=783707
https://bugzilla.gnome.org/show_bug.cgi?id=783705

(In reply to Lubomir Rintel from comment #1)
> The latter two are non-trivial to fix (will clone another bug), but should
> be disabled in RHEL builds.
> 
> The former two are a glib bug -- reassigning.
> 
> Proposed patches upstream:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=783707
> https://bugzilla.gnome.org/show_bug.cgi?id=783705

Wrong links -- sorry! The correct ones:

https://bugzilla.gnome.org/show_bug.cgi?id=783795
https://bugzilla.gnome.org/show_bug.cgi?id=783796

Is this really a Regression?  I mean sure it'd be nice to fix but at this point I don't think it should block 7.4.

In my opinion, async initialization of GDBusObjectManagerClient is broken (but no regression). See https://bugzilla.gnome.org/show_bug.cgi?id=783795#c1 .

I think NM should just not use it for the moment (bug 1450075).

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.