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

[GCP] with user defined tags, sometimes "create cluster" got panic

XMLWordPrintable

    • Important
    • Yes
    • OAPE Sprint 267
    • 1
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the Installer panicked if it attempted to retrieve Google Cloud Platform (GCP) tags over an unstable network, or when it could not reach the GCP server. With this release, the issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-51211[*OCPBUGS-51211*])
      -----
      Installer panics when retrieving GCP tags over unstable network, when unable to reach the GCP server.
      Show
      * Previously, the Installer panicked if it attempted to retrieve Google Cloud Platform (GCP) tags over an unstable network, or when it could not reach the GCP server. With this release, the issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-51211 [* OCPBUGS-51211 *]) ----- Installer panics when retrieving GCP tags over unstable network, when unable to reach the GCP server.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-50919. The following is the description of the original issue:
      —
      Description of problem:

          with user defined tags, sometimes "create cluster" got panic

      Version-Release number of selected component (if applicable):

          4.18.0-rc.9 for example

      How reproducible:

          Sometimes (Easy to reproduce in PROW CI, at least today)

      Steps to Reproduce:

      1. "create install-config", and then insert interested settings (see [1])
2. activate the IAM service account which has the required permissions
3. (optional)"create manifests"
4. "create cluster"

      Actual results:

          Sometimes "create manifests" or "create cluster" got panic (see [2]). 

      Expected results:

          The installation should either succeed, or tell clear error messages. In any case, there should be no panic. 

      Additional info:

          The panic looks being caused by either PROW System flake or GCP flake, because of below reasons: 
(1) We tried manually installation locally, of 4.18.0-0.nightly-multi-2025-02-17-042334 and 4.17.0-0.nightly-multi-2025-02-15-095503, both succeeded. 
(2) As for PROW CI tests, both with 4.18.0-rc.9, the Feb. 14's installation succeeded, but today's installation got the panic issue (see [3]). 

FYI the PROW CI debug PR: https://github.com/openshift/release/pull/61698

              bhb@redhat.com Bharath B
              openshift-crt-jira-prow OpenShift Prow Bot
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: