Bug 1832394
| Summary: | rear silently fails to create usable backup with LUKS2 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Chris Cheney <ccheney> | ||||||
| Component: | rear | Assignee: | Vitezslav Crhonek <vcrhonek> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | David Jež <djez> | ||||||
| Severity: | high | Docs Contact: | Prerana Sharma <presharm> | ||||||
| Priority: | high | ||||||||
| Version: | --- | CC: | djez, efedin, lmanasko, ovasik, pcahyna, pkhedeka | ||||||
| Target Milestone: | rc | Keywords: | Triaged | ||||||
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | rear-2.4-18.el8 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
.`ReaR` utility now restores system using `LUKS2` encrypted partition
Previously, when at least one `LUKS2` encrypted partition was present on the system to backup with Relax-and-Recover (`Rear`) utility, the user was not informed that ReaR does not support `LUKS2` encrypted partition. Consequently, the `ReaR` utility was unable to recreate the original state of the system during the restore phase.
With this update, support of basic `LUKS2` configuration, error checking, and improved output has been added to the `ReaR` utility. The `ReaR` utility now restores systems using basic `LUKS2` encrypted partitions or notifies users in the opposite case.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-05-18 16:03:02 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Chris Cheney
2020-05-06 16:23:57 UTC
From a quick look at the issue, it seems that ReaR backs up the data properly, and then fails to recreate the disk layout during restore, right? I.e. data are not lost and could be in principle restored in another way. (I am not trying to say that the issue does not matter, just trying to understand the impact and cause and possible workarounds.) Improved version of patch from PR#2381 is available in PR#2493.
https://github.com/rear/rear/pull/2493
It doesn't report error when creating backup but just warns user that usage
of unsupported version of LUKS was detected. ReaR then adds commented out
"crypt" entry to disklayout.conf and finishes the backup as usual.
During the recover phase, user can edit disklayout.conf, uncomment "crypt"
entry and provide correct values there. I was able to successfully complete
the system recovery in this manner.
Created attachment 1721409 [details]
backported upstream code
Upstream has merged initial support of LUKS2 from PR#2504:
https://github.com/rear/rear/pull/2504
Created attachment 1733293 [details]
proposed fix
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 (rear bug fix and enhancement update), 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-2021:1910 |