Bug 1461572
| Summary: | warnings in output of nmcli g: no object known for /org/freedesktop/NetworkManager/Devices/279 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Lubomir Rintel <lrintel> |
| Component: | NetworkManager | Assignee: | NetworkManager Development Team <nm-team> |
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.3 | CC: | acardace, allanlewis99, atragler, bgalvani, desktop-qa-list, fge, fgiudici, jmaxwell, liali, lrintel, mboisver, rkhan, sukulkar, thaller, till, tpelka, vbenes |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1457223 | Environment: | |
| Last Closed: | 2021-03-03 11:37:41 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: | 1457223 | ||
| Bug Blocks: | |||
|
Description
Lubomir Rintel
2017-06-14 20:05:24 UTC
Marking this questionable for 7.5. This is not service affecting and hence we will attempt to address it in 7.5 if time permits. Else, we will address in 7.6. -Sushil NetworkManager server side got refactored to not use GDBusObjectManagerServer anymore. Also, the emitting of signals was reworked. See https://github.com/NetworkManager/NetworkManager/pull/74 https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=1e535789cfd8dbc94da1e4f6393d27ccc2a209fc https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=1e535789cfd8dbc94da1e4f6393d27ccc2a209fc&id=297d4985abcc7b571b8c090ee90622357fc60e16 This was supposed to fix ordering issue of signals. I think however, that I still saw such a warning afterwards. So maybe the ordering is still not entirely right. However, I think once we identify which signal is wrongly emitted before another one, it should be reasonably simple to fix. One known issue:
(process:25456): GLib-GIO-WARNING **: gdbusobjectmanagerclient.c:1588: Processing InterfaceRemoved signal for path /org/freedesktop/NetworkManager/Settings/12 but no object proxy exists
and on the bus:
‣ Type=signal Endian=l Flags=1 Version=1 Priority=0 Cookie=1558
Sender=:1.472 Path=/org/freedesktop/NetworkManager/Settings/12 Interface=org.freedesktop.NetworkManager.Settings.Connection Member=Removed
UniqueName=:1.472
MESSAGE "" {
};
‣ Type=signal Endian=l Flags=1 Version=1 Priority=0 Cookie=1559
Sender=:1.472 Path=/org/freedesktop/NetworkManager/Settings Interface=org.freedesktop.NetworkManager.Settings Member=ConnectionRemoved
UniqueName=:1.472
MESSAGE "o" {
OBJECT_PATH "/org/freedesktop/NetworkManager/Settings/12";
};
[snip]
‣ Type=signal Endian=l Flags=1 Version=1 Priority=0 Cookie=1565
Sender=:1.472 Path=/org/freedesktop Interface=org.freedesktop.DBus.ObjectManager Member=InterfacesRemoved
UniqueName=:1.472
MESSAGE "oas" {
OBJECT_PATH "/org/freedesktop/NetworkManager/Settings/12";
ARRAY "s" {
STRING "org.freedesktop.NetworkManager.Settings.Connection";
};
};
I think the signals emitted by server are correct, but it's a bug in libnm.
Mass-moving bugs RHEL <= 7.6.0 to 7.7.0. As we are past RFE deadline for 7.7.0 and we should have no new features on 7.8.0, please evaluate if it's still wanted on RHEL7 and contact PM for exception. You may also move it to RHEL8 if that's wanted. Thanks! see also bug 1648195 This is a larger issue that went unfixed for a while. The fix is probably larger. Since we no longer rebase rhel-7 to newer versions, this might be hard to fix. Fix it in rhel-8 first. Reassign. *** Bug 1648195 has been marked as a duplicate of this bug. *** in NetworkManager 1.22.0 (introduced in rhel-8.2), libnm was heavily refactored. That should avoid this issue on the surface by no longer emitting the warning. Note that the remaining problem in is that NetworkManager sometimes exposes an inconsistent state on D-Bus, which caused these warnings. That is not yet fixed. You can tell libnm-1.22 to still emit warnings about such issues by: LIBNM_CLIENT_DEBUG=warning nmcli ... Once we fix this, we can export "G_DEBUG=fatal-warnings LIBNM_CLIENT_DEBUG=error,warning" for all our CI runs. *** Bug 1655783 has been marked as a duplicate of this bug. *** 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. This is still an issue (because NM might emit signals in the wrong order): (In reply to Thomas Haller from comment #10) > in NetworkManager 1.22.0 (introduced in rhel-8.2), libnm was heavily > refactored. > > That should avoid this issue on the surface by no longer emitting the > warning. > > > Note that the remaining problem in is that NetworkManager sometimes exposes > an inconsistent state on D-Bus, which caused these warnings. That is not yet > fixed. You can tell libnm-1.22 to still emit warnings about such issues by: > > LIBNM_CLIENT_DEBUG=warning nmcli ... > > > Once we fix this, we can export "G_DEBUG=fatal-warnings > LIBNM_CLIENT_DEBUG=error,warning" for all our CI runs. |