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

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

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

      None

      Show
      None
    • Installer panics when retrieving GCP tags over unstable network, when unable to reach the GCP server.
    • Bug Fix
    • In Progress

      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

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

            Jianli Wei added a comment -

            Manually update the status into verified, as Bharath had helped providing the release note text/type. Thanks! 

            Jianli Wei added a comment - Manually update the status into verified, as Bharath had helped providing the release note text/type. Thanks! 

            Hi bhb@redhat.com,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi bhb@redhat.com , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            Jianli Wei added a comment -

            I reviewed the PR https://github.com/openshift/installer/pull/9495 which looks good to me. As there's no network unstable issue today, add the label "pre-merge".

            Jianli Wei added a comment - I reviewed the PR https://github.com/openshift/installer/pull/9495 which looks good to me. As there's no network unstable issue today, add the label "pre-merge".

            Jianli Wei added a comment -

            Jianli Wei added a comment - gpei@redhat.com FYI Bharath was the DEV/Assignee of the epic CORS-2783 Apply user defined tags to all resources created by OpenShift (GCP) GA

            Gaoyun Pei added a comment -

            rhn-support-jiweido you actually want to assign it to rh-ee-bbarbach?

            Gaoyun Pei added a comment - rhn-support-jiwei do you actually want to assign it to rh-ee-bbarbach ?

            Jianli Wei added a comment -

            Jianli Wei added a comment - cc beth.white  

            Jianli Wei added a comment -

            Jianli Wei added a comment - cc yunjiang-1 jialiu@redhat.com  

            Gaoyun Pei added a comment -

            Reject it as a Release Blocker for it's not always reproducible, we do have successful installation jobs locally or in Prow with the same payload. It seems to only happen when the Prow system network is unstable.

            Gaoyun Pei added a comment - Reject it as a Release Blocker for it's not always reproducible, we do have successful installation jobs locally or in Prow with the same payload. It seems to only happen when the Prow system network is unstable.

              bhb@redhat.com Bharath B
              rhn-support-jiwei Jianli Wei
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: