Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Document URL:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Storage_Administration_Guide/index.html#snapper-undochange
Section Number and Name:
13.5. Reverse Changes in Between Snapshots
Describe the issue:
"NOTE: PLACE HOLDER DIAGRAM" Not what we want in the published document.
Also the warning in incomplete:
"Important
This will not revert the snapper volume back to its original state and does not provide data consistency. Any file modification that occurs outside of the specified range (for example, after snapshot 2) will remain unchanged after reverting back (for example, to the state of snapshot 1). For example, should the undochange be run to undo the creation of a user, any files owned by that user may still remain.
There is also no mechanism to ensure file consistency as a snapshot is made, so any inconsistencies that already exist can be transfered back to the snapshot when the undochange command is used. "
The upstream snapper documentation is pretty specific that you should *not* use snapper to try to "undochange" the root filesystem. (i.e. "snapper -c root create --command "yum update" followed later by a "snapper -c root undochange y..x" is likely to result in catastrophic failure... i.e. is not supported).
Upstream snapper SuSe snapper has the "rollback" command (which we appear to not include) which handles this usecase.
This limitation needs to be very clear.
Finally, the snapper section is *very* heavy on btrfs examples which are not yet supported. Should probably have all the examples use lvm since that is what is supported.
Suggestions for improvement:
See above
Additional information: