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

[azure-stack-upi] worker nodes are not added into public lb backendpool

XMLWordPrintable

    • Critical
    • Yes
    • CLOUD Sprint 243, CLOUD Sprint 244
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * In {product-title} version 4.14 and later, there is a known issue that causes installation of Azure Stack Hub to fail. Azure Stack Hub clusters that are upgraded to 4.14 or later might encounter load balancer configuration issues as nodes scale up or down. Installing or upgrading to 4.14 in Azure Stack Hub environments is not recommended until this issue is resolved. (link:https://issues.redhat.com/browse/OCPBUGS-20213[*OCPBUGS-20213*])
      Show
      * In {product-title} version 4.14 and later, there is a known issue that causes installation of Azure Stack Hub to fail. Azure Stack Hub clusters that are upgraded to 4.14 or later might encounter load balancer configuration issues as nodes scale up or down. Installing or upgrading to 4.14 in Azure Stack Hub environments is not recommended until this issue is resolved. (link: https://issues.redhat.com/browse/OCPBUGS-20213 [* OCPBUGS-20213 *])
    • Known Issue
    • Done

      Description of problem:

      Install 4.14 UPI cluster on azure stack hub, console could not be accessed outside cluster.
      
      $ curl -L -k https://console-openshift-console.apps.jimawwt.installer.redhat.wwtatc.com -vv
      *   Trying 10.255.96.76:443...
      * connect to 10.255.96.76 port 443 failed: Connection timed out
      * Failed to connect to console-openshift-console.apps.jimawwt.installer.redhat.wwtatc.com port 443: Connection timed out
      * Closing connection 0
      curl: (28) Failed to connect to console-openshift-console.apps.jimawwt.installer.redhat.wwtatc.com port 443: Connection timed out
      
      
      Worker nodes are missing in public lb backend pool
      $ az network lb address-pool list --lb-name jimawwt-jhvtn -g jimawwt-jhvtn-rg
      [
        {
          "backendIPConfigurations": [
            {
              "id": "/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/jimawwt-jhvtn-rg/providers/Microsoft.Network/networkInterfaces/jimawwt-jhvtn-master-1-nic/ipConfigurations/pipConfig",
              "resourceGroup": "jimawwt-jhvtn-rg"
            },
            {
              "id": "/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/jimawwt-jhvtn-rg/providers/Microsoft.Network/networkInterfaces/jimawwt-jhvtn-master-0-nic/ipConfigurations/pipConfig",
              "resourceGroup": "jimawwt-jhvtn-rg"
            },
            {
              "id": "/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/jimawwt-jhvtn-rg/providers/Microsoft.Network/networkInterfaces/jimawwt-jhvtn-master-2-nic/ipConfigurations/pipConfig",
              "resourceGroup": "jimawwt-jhvtn-rg"
            }
          ],
          "etag": "W/\"7a9d24a2-ff06-4108-9aac-a277595792e3\"",
          "id": "/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/jimawwt-jhvtn-rg/providers/Microsoft.Network/loadBalancers/jimawwt-jhvtn/backendAddressPools/jimawwt-jhvtn",
          "loadBalancingRules": [
            {
              "id": "/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/jimawwt-jhvtn-rg/providers/Microsoft.Network/loadBalancers/jimawwt-jhvtn/loadBalancingRules/api-public",
              "resourceGroup": "jimawwt-jhvtn-rg"
            },
            {
              "id": "/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/jimawwt-jhvtn-rg/providers/Microsoft.Network/loadBalancers/jimawwt-jhvtn/loadBalancingRules/a1a1c7bfe78c14a41a9149d42d698824-TCP-80",
              "resourceGroup": "jimawwt-jhvtn-rg"
            },
            {
              "id": "/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/jimawwt-jhvtn-rg/providers/Microsoft.Network/loadBalancers/jimawwt-jhvtn/loadBalancingRules/a1a1c7bfe78c14a41a9149d42d698824-TCP-443",
              "resourceGroup": "jimawwt-jhvtn-rg"
            }
          ],
          "name": "jimawwt-jhvtn",
          "provisioningState": "Succeeded",
          "resourceGroup": "jimawwt-jhvtn-rg"
        }
      ]
      
      Similar bug OCPBUGS-14762 detected on Azure UPI. On installer side, we checked that public lb name and backendpool name for UPI are the same as ASH IPI. 

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

      4.14.0-0.nightly-2023-10-06-234925

      How reproducible:

      Always when installing Azure Stack UPI on 4.14

      Steps to Reproduce:

      1. Install UPI on Azure Stack Hub on 4.14
      2.
      3.
      

      Actual results:

      Worker nodes are missing in public lb backendpool

      Expected results:

      worker nodes are added into public lb backendpool and application can be accessed outside cluster

      Additional info:

      Issue is only detected on 4.14 azure stack hub UPI.
      It works on ASH IPI and 4.13/4.12 ASH UPI.

              mimccune@redhat.com Michael McCune
              jinyunma Jinyun Ma
              Zhaohua Sun Zhaohua Sun
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: