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.

Bug 1743399

Summary: 'cryptsetup reencrypt" and "cryptsetup-reencrypt" are two distinct utilities yet both give old CRYPTSETUP-REENCRYPT(8) man page
Product: Red Hat Enterprise Linux 8 Reporter: Corey Marthaler <cmarthal>
Component: cryptsetupAssignee: Ondrej Kozina <okozina>
Status: CLOSED ERRATA QA Contact: guazhang <guazhang>
Severity: low Docs Contact:
Priority: high    
Version: 8.1CC: agk, guazhang, jbrassow, mbroz, okozina, prajnoha
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cryptsetup-2.2.2-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:54:37 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: 1757783    
Bug Blocks:    

Description Corey Marthaler 2019-08-19 20:09:59 UTC
Description of problem:

# cryptsetup reencrypt
[root@hayes-01 ~]# man cryptsetup reencrypt
CRYPTSETUP-REENCRYPT(8)                                                                      Maintenance Commands                                                                      CRYPTSETUP-REENCRYPT(8)

NAME
       cryptsetup-reencrypt - tool for offline LUKS device re-encryption

SYNOPSIS
       cryptsetup-reencrypt <options> <device>



# cryptsetup-reencrypt
[root@hayes-01 ~]# man cryptsetup-reencrypt
CRYPTSETUP-REENCRYPT(8)                                                                      Maintenance Commands                                                                      CRYPTSETUP-REENCRYPT(8)

NAME
       cryptsetup-reencrypt - tool for offline LUKS device re-encryption

SYNOPSIS
       cryptsetup-reencrypt <options> <device>




Version-Release number of selected component (if applicable):
cryptsetup-2.2.0-1.el8    BUILT: Fri Aug 16 01:22:41 CDT 2019
cryptsetup-libs-2.2.0-1.el8    BUILT: Fri Aug 16 01:22:41 CDT 2019
cryptsetup-reencrypt-2.2.0-1.el8    BUILT: Fri Aug 16 01:22:41 CDT 2019

Comment 1 Ondrej Kozina 2019-08-20 11:00:45 UTC
Hmm, this never occurred to me. I'd like to solve this problem by removing cryptsetup-reencrypt in future releases (while moving LUKS1 reencryption in cryptsetup as well). But for now I think we should perhaps just add remark that "If looking for LUKS2 online reencryption, please read man cryptsetup" or similar?

Comment 3 Ondrej Kozina 2019-11-18 11:31:19 UTC
There's following hint in cryptsetup-reencrypt manual page since cryptsetup v2.2.2:

>> NOTE: If you're looking for LUKS2 online reencryption manual please read cryptsetup(8) man page instead (see reencrypt action). This page is for legacy offline reencryption utility only.

I don't think we can do anything else about it unless we fully merge cryptsetup-reencnrypt code in cryptsetup later (no sooner than 2.4.0 upstream release)

Comment 5 guazhang@redhat.com 2019-11-25 07:39:15 UTC
Hello

It seem the cryptsetup-2.2.2-1.el8 don't update the man page, May I move to verified for the fixed version ?


#man cryptsetup-reencrypt
CRYPTSETUP-REENCRYPT(8)                         Maintenance Commands                         CRYPTSETUP-REENCRYPT(8)

NAME
       cryptsetup-reencrypt - tool for offline LUKS device re-encryption

SYNOPSIS
       cryptsetup-reencrypt <options> <device>



#man cryptsetup reencrypt

CRYPTSETUP-REENCRYPT(8)                         Maintenance Commands                         CRYPTSETUP-REENCRYPT(8)

NAME
       cryptsetup-reencrypt - tool for offline LUKS device re-encryption

SYNOPSIS
       cryptsetup-reencrypt <options> <device>

Comment 6 Ondrej Kozina 2019-11-25 10:50:39 UTC
That note is man page for cryptsetup-reencrypt (installed separately from basic cryptsetup). Let me check...

Comment 7 Ondrej Kozina 2019-11-25 11:15:30 UTC
yup. It's there.

man cryptsetup-reencrypt | grep "NOTE:.*LUKS2 online"

Comment 8 guazhang@redhat.com 2019-11-25 11:29:41 UTC
Hello

# man cryptsetup-reencrypt | grep "NOTE:.*LUKS2 online"
       NOTE: If you're looking for LUKS2 online reencryption manual please read cryptsetup(8) man page instead  (see

# man cryptsetup reencrypt | grep "NOTE:.*LUKS2 online"
       NOTE: If you're looking for LUKS2 online reencryption manual please read cryptsetup(8) man page instead  (see

so move to verified

thanks
guazhang

Comment 10 errata-xmlrpc 2020-04-28 16:54:37 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-2020:1848