Steps to Reproduce

1) Create a VPC and set an outbound rules to deny the traffic at HTTP port 80)
2) Navigate to the ROSA classic cluster creation wizard.
3) Select the region type as Single-zone and provide a KMS key value as shown below

arn:aws:kms:us-west-2:301721915996:key/1637c2bc-434a-4eb3-8931-243692ca897a

4) Select the network type as Private
5) Provide one of the subnets used for the above-created VPC and click on the Create cluster button
6) The cluster installation progress should be shown on the Overview page and the Network banner along with the list of subnets that failed the validation should be displayed

Expected Result
The Overview page should load correctly.
The network validation step should fail and the warning message should be shown
"User action required"
To allow this cluster to be fully managed, add these URLs to the allowlist of these subnet firewalls. For more information review the egress requirements or contact Red Hat support" This should be a warning message"

Actual Result

Cannot convert undefined or null to object

lamarach@lamarach-mac ~ % ocm describe cluster rosaclasskms

ID:			27qs5ku10nlvfrur7mh2te46iugc3agm
External ID:		8a9be43b-3728-49ec-bc92-2a4b90a9b127
Name:			rosaclasskms
State:			installing
API URL:
API Listening:		internal
Console URL:
Masters:		3
Infra:			2
Computes:		2
Product:		rosa
Provider:		aws
Version:
Region:			us-west-2
Multi-az:		false
CCS:			true
Subnet IDs:		[subnet-0eb2281e15eef643d]
PrivateLink:		true
STS:			true
Existing VPC:		true
Channel Group:		stable
Cluster Admin:		true
Organization:		ocm-orgAdmin UItesting
Creator:		hac-shivanthi01
Email:			lamarach+hac01@redhat.com
AccountNumber:          6344158
Created:		2023-11-30T04:34:30Z
Expiration:		2023-12-01T16:34:27Z
Shard:			https://api.hives02ue1.j5l5.p1.openshiftapps.com:6443