Accessed https://qaprodauth.console.redhat.com/openshift/create/osd?features=

, 

1. An empty error message shown under the key ring field while enabling the encrypt persistent volumes with custom keys for OSD. 
2. The option Advance Encryption , options Use default KMS Keys & Use custom KMS keys are missing.

Steps to reproduce:

1. Access https://qaprodauth.console.redhat.com/openshift/create/osd?features= {"osd-wizard-v2":"true"}
2. Choose an OSD CCS cluster with GCP cloud options.
3. Click "Next" and reach  "Cluster Settings" > "Details" page.
4. Click on  "Encrypt persistent volumes with customer keys"
5. View the behavior.
6. Compare encryption fields from the OSD wizard vs OSD wizard V2 

Actual results:
In step 4, An empty error message is shown under the key ring field while enabling the encrypt persistent volumes with custom keys for OSD.

In step 6, The fields and layouts are mismatching while comparing encryption fields from OSD cluster wizard v2 and current layout. The option Advanced Encryption , options Use default KMS Keys & Use custom KMS keys are missing.

Expected results:

In step 4, There should not be an empty error message shown under the key ring field while enabling the encrypt persistent volumes with custom keys for OSD.

In step 6, The fields and layouts should be matching while comparing encryption fields from OSD cluster wizard v2 and current model.