Bug 1781187
Summary: | [RFE]Support LUKS + Clevis/Tang configuration from gluster-ansible roles | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Gobinda Das <godas> | |
Component: | gluster-ansible | Assignee: | Gobinda Das <godas> | |
Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | unspecified | CC: | asakthiv, bugs, pprakash, puebele, rhs-bugs, sabose, sasundar | |
Target Milestone: | --- | Keywords: | FutureFeature, ZStream | |
Target Release: | RHGS 3.5.z Batch Update 2 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | gluster-ansible-infra-1.0.4-6.el8rhgs | Doc Type: | If docs needed, set a value | |
Doc Text: |
Previously, host root disk was encrypted using clevis, during the reboot of host the user was required to manually enter passphrase to unlock root disk. In this release, tang server is configured to automate the reboot process without manual entry of passphrase.This feature supports root disk encryption with auto unlock and also Gluster disks encryption with automatic mount after reboot, on Red Hat Hyperconverged Infrastructure for Virtualization deployments.
|
Story Points: | --- | |
Clone Of: | 1781184 | |||
: | 1826283 (view as bug list) | Environment: |
rhhiv, rhel8
|
|
Last Closed: | 2020-06-16 05:57:29 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1781184, 1826283 |
Description
Gobinda Das
2019-12-09 13:54:19 UTC
*** Bug 1781189 has been marked as a duplicate of this bug. *** verified with gluster-ansible-infra-1.0.4-6 Playbook and inventory file are available by which NBDE setup is accomplished 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/RHEA-2020:2575 |