-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18.0
Description of problem:
It is the negative testing scenario of QE test case OCP-36887, i.e. specifying non-existing encryption keyring/name for compute & control-plane, and the expectation is creating instance error due to the problem keyring. But the testing results is, the installer does not tell the error in stdout, and keeps waiting until timeout.
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2024-12-15-202509
How reproducible:
Always
Steps to Reproduce:
1. "create install-config", and then insert the interested settings (see [1]) 2. "create cluster" (see [2])
Actual results:
The installer doesn't tell the real error and quit soon, although finally it tells below error, ERROR failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to provision control-plane machines: machines are not ready: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
Expected results:
The installer should tell the keyring error and quit soon.
Additional info:
- is related to
-
OCPBUGS-52203 [GCP] with valid encryptionKey.kmsKey.keyRing, the installer always tells "failed to find key ring"
-
- POST
-
-
CORS-3682 Improve error reporting on CAPI failures
-
- To Do
-
- relates to
-
CORS-3806 4.18 installer full functional testing - GCP
-
- Closed
-
- links to
-
RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update