-
Bug
-
Resolution: Done
-
Critical
-
4.13
-
Yes
-
Sprint 234, Sprint 235
-
2
-
Approved
-
False
-
-
N/A
-
Bug Fix
-
Done
Description of problem:
Installer get stuck at the beginning of installation if BYO private hosted zone is configured in install-config, from the CI logs, installer has no actions in 2 hours. Errors: level=info msg=Credentials loaded from the "default" profile in file "/var/run/secrets/ci.openshift.io/cluster-profile/.awscred" 185 {"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:164","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 2h0m0s timeout","severity":"error","time":"2023-03-05T16:44:27Z"}
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-2023-03-23-000343
How reproducible:
Always
Steps to Reproduce:
1. Create an install-config.yaml, and config byo private hosted zone 2. Create the cluster
Actual results:
installer showed the following message and then get stuck, the cluster can not be created. level=info msg=Credentials loaded from the "default" profile in file "/var/run/secrets/ci.openshift.io/cluster-profile/.awscred"
Expected results:
create cluster successfully
Additional info:
- clones
-
OCPBUGS-10767 [AWS] installer get stuck if BYO private hosted zone is configured
- Closed
- is blocked by
-
OCPBUGS-10767 [AWS] installer get stuck if BYO private hosted zone is configured
- Closed
- links to