Uploaded image for project: 'OpenShift Cloud'
  1. OpenShift Cloud
  2. OCPCLOUD-2409

Impact [4.14] LB not getting External-IP

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • 3
    • False
    • None
    • False
    • OTA 246

      Impact of OCPBUGS-25483:

      Which 4.y.z to 4.y'.z' updates increase vulnerability?

      Any version of openshift prior to 4.14, upgrading into a 4.14 or later cluster is affected by this bug.

      Which types of clusters?

      Azure (not stack hub) clusters created by openshift-installer in 4.8 or earlier. For ARO, all clusters created in 4.13 or earlier.

      What is the impact? Is it serious enough to warrant removing update recommendations?

      New machines will not be added to load balancers. This could lead to a total outage of ingress over time. Resolvable only by manually adding the machines to the load balancer.

      How involved is remediation?

      Users can add vmType=standard (it defaults to vmType="") to the cloud-provider-config configmap in the openshift-config namespace.

      The remediation can be done prior to upgrade and is low complexity.

      Is this a regression?

      Yes, a default value changed in the Azure cloud provider and the behaviour changed as a result of this. Setting the vmType to standard restores the old behaviour.

            joelspeed Joel Speed
            trking W. Trevor King
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: