Bug 1882216

Summary: [Doc RFE] Document how to encrypt a storage class.
Product: [Red Hat Storage] Red Hat OpenShift Container Storage Reporter: Anjana Suparna Sriram <asriram>
Component: documentationAssignee: Laura Bailey <lbailey>
Status: CLOSED CURRENTRELEASE QA Contact: Oded <oviner>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.6CC: ebenahar, nberry, ocs-bugs, oviner
Target Milestone: ---Keywords: Documentation, FutureFeature
Target Release: OCS 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-25 14:54:56 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:    
Bug Blocks: 1880905    
Attachments:
Description Flags
Warning minimal cluster deployment none

Comment 9 Oded 2020-10-26 09:50:57 UTC 
"Figure 1.6. Create Storage Cluster page" not updated.

The warning "A minimal cluster deployment will be performed." does not appear.
*attached screenshot
Comment 10 Oded 2020-10-26 09:55:17 UTC 
Created attachment 1724129 [details]
Warning minimal cluster deployment
Comment 12 Neha Berry 2020-10-27 10:06:25 UTC 
(In reply to Oded from comment #9)
> "Figure 1.6. Create Storage Cluster page" not updated.
> 
> The warning "A minimal cluster deployment will be performed." does not
> appear.
> *attached screenshot

@oviner the screenshot in the doc for encryption, does not need the minimal deployment warning scenario. They are unrelated.

for you, your CPU count was 12 per node and due to https://bugzilla.redhat.com/show_bug.cgi?id=1886541 , your cluster shows the minimal deployment warning. Ideally, 12 CPU per node should not throw the warning (will be resolved when attached bug is fixed)
Comment 14 Red Hat Bugzilla 2023-09-15 00:48:43 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days