Bug 1578335

Summary: Checkpoint keeps dangling reference to deleted device
Product: Red Hat Enterprise Linux 7 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Francesco Giudici <fgiudici>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.5CC: atragler, bgalvani, fgiudici, fpokryvk, jmaxwell, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.18.0-0.3.20190408git43d9187c14.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:16:24 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: 1654714    

Description Thomas Haller 2018-05-15 10:11:41 UTC 
When we create a checkpoint, the checkpoint keeps a reference to all the devices that are part of the checkpoint. The device's path is also exposed on D-Bus via the "Devices" property.

When the device gets removed (for example, because it's a software device, or because the module is unloaded), the device otherwise disappears from NetworkManager's D-Bus API. However, the checkpoint still references the D-Bus path that no longer exists.

NetworkManager must handle this better.
Comment 2 Francesco Giudici 2019-03-15 18:17:42 UTC 
Pull request posted:
https://github.com/NetworkManager/NetworkManager/pull/316
Comment 5 errata-xmlrpc 2019-08-06 13:16:24 UTC 
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-2019:2302