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

PowerVS: update capi ibmcloud 9b077049

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.18
    • Installer / PowerVS
    • None
    • Important
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when you deployed a cluster on a {cap-ibm-first} zone, the load balancers were slow to create. As a consequence, the cluster failed. With this release, the {cap-ibm-first} provider no longer has to wait until all load balancers are ready and the issue is resolved.
      (link:https://issues.redhat.com/browse/OCPBUGS-43923[*OCPBUGS-43923*])
      Show
      * Previously, when you deployed a cluster on a {cap-ibm-first} zone, the load balancers were slow to create. As a consequence, the cluster failed. With this release, the {cap-ibm-first} provider no longer has to wait until all load balancers are ready and the issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-43923 [* OCPBUGS-43923 *])
    • Proposed

      Description of problem:

      Deploy a 4.18 cluster on a PowerVS zone where LoadBalancers are slow to create.
We are called with InfraReady. We then create DNS records for the LBs. However, only the public LB exists. So the cluster fails to deploy.  The internal LB does eventually complete.

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

      4.18

      How reproducible:

      Occassionally on a zone with slow LB creation.

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

                Created:
                Updated:
                Resolved: