-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
Steps to Reproduce
1. Launch the OCM UI staging environment
2. Create a VPC but do not configure it for ROSA
3. Navigate to the ROSA hypershift cluster creation wizard and enter valid details
4. From the dropdown select the VPC created in Step 2
5. Navigate to the Review screen and click on the Create Cluster button
Expected Result
The cluster creation should not succeed and the inflight error messages should be shown
Actual Result
The inflight error messages do not appear and the cluster is in a Ready state.
The network warning messages should remain even after the cluster installation process is finished and the installation status should be clear to the user.
lamarach@lamarach-mac ~ % ocm get /api/clusters_mgmt/v1/clusters/26d71gbv8ua6jb0o4b7knvi3n9gcgorh/inflight_checks { "kind": "InflightCheckList", "href": "/api/clusters_mgmt/v1/clusters/26d71gbv8ua6jb0o4b7knvi3n9gcgorh/inflight_checks", "page": 1, "size": 1, "total": 1, "items": [ { "kind": "InflightCheck", "id": "2661c9d7-1111-465b-9908-55055f7b98b9", "href": "/api/clusters_mgmt/v1/clusters/26d71gbv8ua6jb0o4b7knvi3n9gcgorh/inflight_checks/2661c9d7-1111-465b-9908-55055f7b98b9", "name": "egress", "state": "failed", "details": { "documentation_link": "https://docs.openshift.com/rosa/rosa_planning/rosa-aws-prereqs.html#osd-aws-privatelink-firewall-prerequisites", "subnet-08446174cf90ee815": { "osdnv_logs": "printing out debug logs from the execution:\n - Using configured timeout of 3s for each egress request\n - Gathering description of instance type t3.micro from EC2\n - base64-encoded generated userdata script:\n---\nI2Nsb3VkLWNvbmZpZwpyZXBvX3VwZGF0ZTogdHJ1ZQp3cml0ZV9maWxlczoKICAtIHBhdGg6IC9ydW4tY29udGFpbmVyLnNoCiAgICBwZXJtaXNzaW9uczogNzU1CiAgICBjb250dlcm9mZgogIG1lc3NhZ2U6IEF1dG8tdGVybWluYXRpbmcgaW5zdGFuY2UgZHVlIHRvIHRpbWVvdXQKICB0aW1lb3V0OiAzMDAK\n---\n - Creating a Security group\n - Waiting for the Security Group to exist: sg-01f2e71a2af0f2cb7\n - Scraping console output and waiting for user data script to complete...\n - EC2 console consoleOutput contains data, but end of userdata script not seen, continuing to wait...\n - base64-encoded console logs:\n---\nWyAgICAwLjAwMDAwMF0gTGludXggdmVyc2lvbiA0LjE4LjAtNDc3LjEzLjEuZWw4XzgueDg2XzY0IChtb2NrYnVpbGRAeDg2LXZtLTA4LmJ1aWxkLmVuZy5ib3MucmVkaGF0LmNvbSkY2UgRGF0YVNvdXJjZUVjMkxvY2FsLiAgVXAgMjkuODYgc2Vjb25kcw0K\n---\n - egress failures found\n\nprinting out failures:\n - egressURL error: ocm-quay-production-s3.s3.amazonaws.com:443\n - egressURL error: http-inputs-osdsecuritylogs.splunkcloud.com:443\n - egressURL error: registry.access.redhat.com:443\n - egressURL error: registry.redhat.io:443\n - egressURL error: tagging.us-east-1.amazonaws.com:443\n - egressURL error: quay.io:443\n - egressURL error: ec2.us-west-2.amazonaws.com:443\n - egressURL error: mirror.openshift.com:443\n - egressURL error: inputs1.osdsecuritylogs.splunkcloud.com:9997\n - egressURL error: console.redhat.com:80\n - egressURL error: infogw.api.openshift.com:443\n - egressURL error: quayio-production-s3.s3.amazonaws.com:443\n - egressURL error: sts.us-west-2.amazonaws.com:443\n - egressURL error: ec2.amazonaws.com:443\n - egressURL error: cart-rhcos-ci.s3.amazonaws.com:443\n - egressURL error: iam.amazonaws.com:443\n - egressURL error: observatorium.api.openshift.com:443\n - egressURL error: route53.amazonaws.com:443\n - egressURL error: sts.amazonaws.com:443\n - egressURL error: elasticloadbalancing.us-west-2.amazonaws.com:443\n - egressURL error: events.us-west-2.amazonaws.com:443\n - egressURL error: cloud.redhat.com:443\n - egressURL error: pull.q1w2.quay.rhcloud.com:443\n - egressURL error: console.redhat.com:443\n\nprinting out exceptions preventing the verifier from running the specific test:\nprinting out errors faced during the execution:\n", "egress_url_errors-0": "egressURL error: ocm-quay-production-s3.s3.amazonaws.com:443", "egress_url_errors-1": "egressURL error: http-inputs-osdsecuritylogs.splunkcloud.com:443", "egress_url_errors-2": "egressURL error: registry.access.redhat.com:443", "egress_url_errors-3": "egressURL error: registry.redhat.io:443", "egress_url_errors-4": "egressURL error: tagging.us-east-1.amazonaws.com:443", "egress_url_errors-5": "egressURL error: quay.io:443", "egress_url_errors-6": "egressURL error: ec2.us-west-2.amazonaws.com:443", "egress_url_errors-7": "egressURL error: mirror.openshift.com:443", "egress_url_errors-8": "egressURL error: inputs1.osdsecuritylogs.splunkcloud.com:9997", "egress_url_errors-9": "egressURL error: console.redhat.com:80", "egress_url_errors-10": "egressURL error: infogw.api.openshift.com:443", "egress_url_errors-11": "egressURL error: quayio-production-s3.s3.amazonaws.com:443", "egress_url_errors-12": "egressURL error: sts.us-west-2.amazonaws.com:443", "egress_url_errors-13": "egressURL error: ec2.amazonaws.com:443", "egress_url_errors-14": "egressURL error: cart-rhcos-ci.s3.amazonaws.com:443", "egress_url_errors-15": "egressURL error: iam.amazonaws.com:443", "egress_url_errors-16": "egressURL error: observatorium.api.openshift.com:443", "egress_url_errors-17": "egressURL error: route53.amazonaws.com:443", "egress_url_errors-18": "egressURL error: sts.amazonaws.com:443", "egress_url_errors-19": "egressURL error: elasticloadbalancing.us-west-2.amazonaws.com:443", "egress_url_errors-20": "egressURL error: events.us-west-2.amazonaws.com:443", "egress_url_errors-21": "egressURL error: cloud.redhat.com:443", "egress_url_errors-22": "egressURL error: pull.q1w2.quay.rhcloud.com:443", "egress_url_errors-23": "egressURL error: console.redhat.com:443" } }, "started_at": "2023-09-21T22:15:17.927972Z", "ended_at": "2023-09-21T22:18:07.914684Z", "restarts": 0 }
- is related to
-
OCMUI-36 Show cluster installation "In-Flight" network verification failures for OSD and ROSA
- Closed
- mentioned on