-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.16.0
Description of problem:
Specifying N2D machine types for compute and controlPlane machines, with "confidentialCompute: Enabled", "create cluster" got the error "Confidential Instance Config is only supported for compatible cpu platforms" [1], while the real cause is missing the settings "onHostMaintenance: Terminate". That being said, the 4.16 error is mis-leading, suggest to be consistent with 4.15 [2] / 4/14 [3] error messages. FYI Confidential VM is supported on N2D machine types (see https://cloud.google.com/confidential-computing/confidential-vm/docs/supported-configurations#machine-type-cpu-zone).
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-2024-05-21-221942
How reproducible:
Always
Steps to Reproduce:
1. Please refer to [1]
Actual results:
The error message is like "Confidential Instance Config is only supported for compatible cpu platforms", which is mis-leading.
Expected results:
4.15 [2] / 4/14 [3] error messages, which look better.
Additional info:
FYI it is about QE test case OCP-60212 scenario b.
- blocks
-
OCPBUGS-35493 [gcp] with N2D instance type, unexpectedly got error "Confidential Instance Config is only supported for compatible cpu platforms"
- Closed
- is cloned by
-
OCPBUGS-35493 [gcp] with N2D instance type, unexpectedly got error "Confidential Instance Config is only supported for compatible cpu platforms"
- Closed
- links to
-
RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update