Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-35493

[gcp] with N2D instance type, unexpectedly got error "Confidential Instance Config is only supported for compatible cpu platforms"

XMLWordPrintable

    • Moderate
    • Yes
    • False
    • Hide

      None

      Show
      None
    • Prior to the fix, there was no validation of the values for confidential compute and on host maintenance set by the user. When confidential compute is enabled by the user, the value for on host maintenance must be set to Terminate.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-34416. The following is the description of the original issue:
      —
      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.

              rh-ee-bbarbach Brent Barbachem
              openshift-crt-jira-prow OpenShift Prow Bot
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: