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

PowerVS: Query the CAPI provider for the timeouts needed during provisioning

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.17.0
    • Installer / PowerVS
    • None
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required
    • Done

      Description of problem:

      Query the CAPI provider for the timeouts needed during provisioning. This is optional to support.
      
      The current default of 15 minutes is sufficient for normal CAPI installations. However, given how the current PowerVS CAPI provider waits for some resources to be created before creating the load balancers, it is possible that the LBs will not create before the 15 minute timeout. An issue was created to track this [1].
      
      [1] kubernetes-sigs/cluster-api-provider-ibmcloud#1837
      
      

            [OCPBUGS-35430] PowerVS: Query the CAPI provider for the timeouts needed during provisioning

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Important: OpenShift Container Platform 4.17.1 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2024:7922

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Important: OpenShift Container Platform 4.17.1 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:7922

            Swapnil Bobade added a comment - - edited

            Able to deploy 4.17.0-rc.6 IPI cluster on wdc06 successfully without loadBalancer timeout

            DEBUG Time elapsed per stage:
            DEBUG    Network-infrastructure Provisioning: 27m56s
            DEBUG Post-network, pre-machine Provisioning: 24s
            DEBUG                   Machine Provisioning: 10m15s
            DEBUG       Infrastructure Post-provisioning: 1m7s
            DEBUG                     Bootstrap Complete: 28m40s
            DEBUG                                    API: 8m32s
            DEBUG                      Bootstrap Destroy: 7s
            DEBUG            Cluster Operators Available: 22m23s
            DEBUG               Cluster Operators Stable: 53s
            INFO Time elapsed: 1h32m44s
            

            Unable to attach install logs. Logs uploaded to drive and adding the link here -

             

            https://drive.google.com/file/d/1dIb6N6_q6eN74YkJTtCSevcf8KSt55NX/view?usp=drive_link

            Swapnil Bobade added a comment - - edited Able to deploy 4.17.0-rc.6 IPI cluster on wdc06 successfully without loadBalancer timeout DEBUG Time elapsed per stage: DEBUG    Network-infrastructure Provisioning: 27m56s DEBUG Post-network, pre-machine Provisioning: 24s DEBUG                   Machine Provisioning: 10m15s DEBUG       Infrastructure Post-provisioning: 1m7s DEBUG                     Bootstrap Complete: 28m40s DEBUG                                    API: 8m32s DEBUG                      Bootstrap Destroy: 7s DEBUG            Cluster Operators Available: 22m23s DEBUG               Cluster Operators Stable: 53s INFO Time elapsed: 1h32m44s Unable to attach install logs. Logs uploaded to drive and adding the link here -   https://drive.google.com/file/d/1dIb6N6_q6eN74YkJTtCSevcf8KSt55NX/view?usp=drive_link

            Hi mturek.coreos,

            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 mturek.coreos , 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.

              mturek.coreos Michael Turek
              hamzy_redhat Mark Hamzy
              Julie Mathew Julie Mathew (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: