Bug 1910483

Summary: Storage cluster creation failed with 'Cannot read property "protocol" of null ' on adding& then cancelling Encryption
Product: OpenShift Container Platform Reporter: Neha Berry <nberry>
Component: Console Storage PluginAssignee: gowtham <gshanmug>
Status: CLOSED ERRATA QA Contact: Neha Berry <nberry>
Severity: high Docs Contact:
Priority: medium    
Version: 4.7CC: afrahman, anbehl, aos-bugs, nthomas, ocs-bugs
Target Milestone: ---   
Target Release: 4.7.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-12-01 13:35: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:
Embargoed:
Attachments:
Description Flags
screencast of the flow depicting the issue none

Description Neha Berry 2020-12-24 07:13:57 UTC
Created attachment 1741671 [details]
screencast of the flow depicting the issue

Description of problem:
==============================
Installed OCP 4.7 on an AWS  and installed OCS 4.7 operator on top of it. While Creating storage cluster, did the following:

1. Select Capacity and Nodes - selected the 3 nodes

2. Configure -> Clicked on Enable Encryption

 a) Added dummy entries for Connection settings -> Connect to an external key management service -> KMS Vault details. (Attached screenshot)

 b) click Next

3. In review and Create Page, 

 a) clicked on Back Button to go back to configure page. 

 b) un-clicked Enable Encryption completely. Did not un-click on "Connect to an external key management service" 

 c) Clicked Next

4. In In review and Create Page, clicked Create with Enable Encryption un-selected. 

Actual results:
===================

The Create storage cluster failed with the error message
>> Cannot read property "protocol" of null

Clicked Cancel

Expected Results
====================
Since the Encryption is now un-clicked it should not affect Storage cluster creation

Workaround:
==================
following 2 workarounds worked in creating a cluster
--------------------------------------------------
1. Clicked Cancel and in next try did not even enable encryption

2. Clicked cancel, again followed all the above steps, then came back to Configure page and un-clicked "
Connect to an external key management service" and "
Enable Encryption" both. Clicked Next and Create and Installation worked.





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


$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2020-12-21-131655   True        False  

OCS = ocs-operator.v4.7.0-207.ci

How reproducible:
=====================
Always


Steps to Reproduce:
====================
Stated in Description

Comment 2 gowtham 2020-12-31 11:48:48 UTC
PR: https://github.com/openshift/console/pull/7688

Comment 3 gowtham 2021-02-01 06:47:23 UTC
This issue is fixed in version 4.7.0-fc.2


I did some mistake in linking this bug with upstream PR, So the status of this bug is not modified to ON_QA automatically

Comment 7 errata-xmlrpc 2021-12-01 13:35: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 (OpenShift Container Platform 4.7.38 bug fix 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:4802