-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.16.0, 4.17.0
Description of problem:
without specifying "kmsKeyServiceAccount" for controlPlane leads to creating bootstrap and control-plane machines failure
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-multi-2024-06-12-211551
How reproducible:
Always
Steps to Reproduce:
1. "create install-config" and then insert disk encryption settings, but not set "kmsKeyServiceAccount" for controlPlane (see [2]) 2. "create cluster" (see [3])
Actual results:
"create cluster" failed with below error: ERROR failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to create control-plane manifest: GCPMachine.infrastructure.cluster.x-k8s.io "jiwei-0613d-capi-84z69-bootstrap" is invalid: spec.rootDiskEncryptionKey.kmsKeyServiceAccount: Invalid value: "": spec.rootDiskEncryptionKey.kmsKeyServiceAccount in body should match '[-_[A-Za-z0-9]+@[-_[A-Za-z0-9]+.iam.gserviceaccount.com
Expected results:
Installation should succeed.
Additional info:
FYI the QE test case: OCP-61160 - [IPI-on-GCP] install cluster with different custom managed keys for control-plane and compute nodes https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-61160
- blocks
-
OCPBUGS-35531 [GCP CAPI install] the optional "kmsKeyServiceAccount" is demanded for controlPlane unexpectedly
- Closed
- is cloned by
-
OCPBUGS-35531 [GCP CAPI install] the optional "kmsKeyServiceAccount" is demanded for controlPlane unexpectedly
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update