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 1868100 - [RFE] Add Clevis Support
Summary: [RFE] Add Clevis Support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: stratisd
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.4
Assignee: mulhern
QA Contact: guazhang@redhat.com
bilhar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-11 16:59 UTC by Dennis Keefe
Modified: 2021-09-06 15:17 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Stratis now supports binding encrypted pools to a supplementary Clevis encryption policy With this enhancement, you can now bind encrypted Stratis pools to Network Bound Disk Encryption (NBDE) using a Tang server, or to the Trusted Platform Module (TPM) 2.0. Binding an encrypted Stratis pool to NBDE or TPM 2.0 facilitates automatic unlocking of pools. As a result, you can access your Stratis pools without having to provide the kernel keyring description after each system reboot. Note that binding a Stratis pool to a supplementary Clevis encryption policy does not remove the primary kernel keyring encryption.
Clone Of:
Environment:
Last Closed: 2021-05-18 15:58:21 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dennis Keefe 2020-08-11 16:59:41 UTC
Support Clevis as an additional method for decryption.  This support will allow
NBDE to automate the decryption of Stratis devices, which form pools of storage. 
GitHub issue: https://github.com/stratis-storage/project/issues/192

Comment 3 guazhang@redhat.com 2020-10-09 02:34:33 UTC
Hello

How to test the new feature and Could you share some test steps or guide here?

I see you have set ITM to 10 weeks which include our test time ? 

I need 1-2 weeks to test the new feature.

Comment 4 Dennis Keefe 2020-10-22 13:51:10 UTC
(In reply to guazhang from comment #3)
> Hello
> 
> How to test the new feature and Could you share some test steps or guide
> here?
> 
> I see you have set ITM to 10 weeks which include our test time ? 
> 
> I need 1-2 weeks to test the new feature.

We will have test information for you after the feature has been completed.

Comment 6 guazhang@redhat.com 2021-01-06 03:34:21 UTC
Hi,

Test pass with stratis-2.3 and add automation to cover the bug.

Comment 14 errata-xmlrpc 2021-05-18 15:58:21 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 (stratis-cli 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:1901


Note You need to log in before you can comment on or make changes to this bug.