Bug 1457223

Summary: Bogus GDBusObjectManagerClient warnings
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: glib2Assignee: Colin Walters <walters>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: atragler, bgalvani, fgiudici, jkoten, lmiksik, lrintel, ovasik, rkhan, sukulkar, thaller
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1461572 (view as bug list) Environment:
Last Closed: 2021-01-15 07:37:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1460259, 1461572    

Description Vladimir Benes 2017-05-31 11:27:01 UTC
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

Comment 1 Lubomir Rintel 2017-06-14 20:06:20 UTC
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

Comment 2 Lubomir Rintel 2017-06-15 08:08:25 UTC
(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

Comment 3 Colin Walters 2017-06-16 15:13:23 UTC
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.

Comment 4 Thomas Haller 2017-06-16 15:47:19 UTC
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).

Comment 7 RHEL Program Management 2021-01-15 07:37:18 UTC
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.