When Running OpenShift 4 on Azure - Error syncing Load Balancer: failed to parse the VMAS ID

Solution In Progress - Updated -

Environment

  • Red Hat OpenShift Container Platform
    • 4.7
  • Azure Red Hat OpenShift
    • 4.7

Issue

  • Not able to create azure cloud native load-balancer service in the Openshift cluster. The load-balancer service creation gets stuck(in pending state) and does not assigning public IP address.

Resolution

  • Red Hat is aware of this issue and it is currently being tracked in BZ-2013004

  • A current workaround is to delete the machine that failed from openshift, Machineset will recreate the deleted machine successfully and the problem should resolve automatically.

$ oc delete machine <machine-name>

Root Cause

  • A bug where Openshift running on Azure fails to procure new Machines and is then not able to create any new Load Balanace service for applications in the Cluster

Diagnostic Steps

  • Error message on the service
$ oc describe service
Events:
  Type     Reason                  Age                  From                Message
  ----     ------                  ----                 ----                -------
  Normal   EnsuringLoadBalancer    83s (x6 over 4m10s)  service-controller  Ensuring load balancer
  Warning  SyncLoadBalancerFailed  78s (x6 over 4m5s)   service-controller  Error syncing load balancer: failed to ensure load balancer: EnsureBackendPoolDeleted: failed to parse the VMAS ID : getAvailabilitySetNameByID: failed to parse the VMAS ID

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments