Bug 2024551

Summary: KMS resources not getting created for IBM FlashSystem storage
Product: OpenShift Container Platform Reporter: Sanjal Katiyar <skatiyar>
Component: Console Storage PluginAssignee: Sanjal Katiyar <skatiyar>
Status: CLOSED ERRATA QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.10CC: afrahman, aos-bugs, nthomas, tjeyasin
Target Milestone: ---Keywords: Regression
Target Release: 4.10.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: 2022-03-10 16:29:22 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:
Bug Depends On:    
Bug Blocks: 2025937    

Description Sanjal Katiyar 2021-11-18 10:27:56 UTC
Description of problem:
For external IBM FlashSystem storage deployment mode, when opting for KMS for encryption, corresponding resources were not getting created.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install ODF
2. Go to "Connect an external storage platform"
3. In "Security and network" wizard step, select "Enable data encryption for block and file storage". Then select "Connect to an external key management service" and complete the required details.
4. Follow along with the process and create a StorageSystem.

Actual results:
Corresponding resources like required ConfigMaps and token Secret were not getting created.

Expected results:
They should get created.

Additional info:
StorageCluster spec:
spec:
  arbiter: {}
  encryption:
    enable: true
    kms:
      enable: true

Comment 12 errata-xmlrpc 2022-03-10 16:29:22 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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056