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.
Bug 1369716 - Checkpoint/rollback improvements
Summary: Checkpoint/rollback improvements
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-24 08:36 UTC by Beniamino Galvani
Modified: 2017-08-01 09:17 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.8.0-0.2.git20170215.1d40c5f4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 09:17:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 770315 0 None None None 2016-08-24 08:36:09 UTC
Red Hat Product Errata RHSA-2017:2299 0 normal SHIPPED_LIVE Moderate: NetworkManager and libnl3 security, bug fix and enhancement update 2017-08-01 12:40:28 UTC

Description Beniamino Galvani 2016-08-24 08:36:10 UTC 
Better handle unrealized/unmanaged devices. See the upstream bugzilla for more details.

https://bugzilla.gnome.org/show_bug.cgi?id=770315
Comment 2 Beniamino Galvani 2016-09-27 09:31:09 UTC 
Merged upstream:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d27ae4a8fec0c8f21a7171e01535f8beb8e5b105
Comment 5 Beniamino Galvani 2017-03-20 14:38:44 UTC 
The rollback now restores the previous unmanaged status of a
device. For example, if you perform a checkpoint on eth0, then set
'nmcli device modify eth0 managed no', the rollback should make it
managed again.

The branch also fixes the case in which a software device is
snapshotted and then removed. The rollback now should recreate the
device.

Also, passing an empty list to the snapshot functionality is
equivalent to passing all devices (including unmanaged ones).

There are a lot possible scenarios and so testing everything is
probably difficult. Here is a list in non-increasing importance order
of what could be tested:

 - checkpoint with no timeout, manual rollback
 - checkpoint with timeout, automatic rollback
 - checkpoint/rollback of multiple devices
 - global checkpoint (all devices)
 - check that the explicitly-unmanaged status of a device is restored
   upon rollback
 - check that software devices are recreated on rollback
 - checkpoint flags [1]

[1] https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-core/nm-dbus-interface.h?id=714504faf27c74a9b26e0f1d4f8bdaff7bb24181#n807
Comment 6 errata-xmlrpc 2017-08-01 09:17:07 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/RHSA-2017:2299
Note You need to log in before you can comment on or make changes to this bug.