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

[GCP] installer cannot detect/expose encryption keyring non-existing error

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • No
    • None
    • Installer (PB) Sprint 263, Installer (PB) Sprint 265, Installer Sprint 266, Installer Sprint 267
    • 4
    • Done
    • Bug Fix
    • Hide
      * Previously, when installing a cluster on {gcp-short}, the installation program would fail to detect if the user provided an encryption key ring that did not exist, causing the installation to fail. With this update, the installation program correctly validates the existence of user provided encryption key rings, preventing failure. (link:https://issues.redhat.com/browse/OCPBUGS-46488[OCPBUGS-46488])
      Show
      * Previously, when installing a cluster on {gcp-short}, the installation program would fail to detect if the user provided an encryption key ring that did not exist, causing the installation to fail. With this update, the installation program correctly validates the existence of user provided encryption key rings, preventing failure. (link: https://issues.redhat.com/browse/OCPBUGS-46488 [ OCPBUGS-46488 ])
    • None
    • None
    • None
    • None

      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:

          

              rh-ee-bbarbach Brent Barbachem
              rhn-support-jiwei Jianli Wei
              None
              None
              Jianli Wei Jianli Wei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: