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.

Description of problem:
This is similar to BZ#1672371 reported for Fedora.

When binding a pin to a device, we are asked to provide the LUKS password; if the password is given incorrectly and the device is a LUKS1 device, we will end up writing metadata to an inactive LUKSMeta slot.

Afterwards, if we try again to bind and this time provide a correct password, we will still get an error when saving the metadata, which effectively prevents us from adding new bindings.

Version-Release number of selected component (if applicable):
clevis-luks-11-2.el8.x86_64

How reproducible: always


Steps to Reproduce:
1. Bind it with "sudo clevis luks bind -d /dev/luks1-device tpm2 {}" (any pin is OK here; use tang if no TPM2 is available)
2. Give a wrong password when asked for the existing LUKS password.
3. check the LUKSMeta slots

Actual results:
# luksmeta -d /dev/luks1-device show
0   active empty
1 inactive cb6e8904-81ff-40da-a84a-07ab9ab5715e
2 inactive empty
3 inactive empty
4 inactive empty
5 inactive empty
6 inactive empty
7 inactive empty


Expected results:
# luksmeta -d /dev/luks1-device show
0   active empty
1 inactive empty
2 inactive empty
3 inactive empty
4 inactive empty
5 inactive empty
6 inactive empty
7 inactive empty

AC: After providing wrong password in 'clevis luks bind' operation, the used slot will remain empty.

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 (clevis 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-2020:4701