Objects in NSX UI are stuck "In Progress"

Products

• VMware NSX
• VCF Automation
• VMware vRealize Automation 8.x
• VMware Tanzu Platform - Kubernetes
• VMware vSphere Kubernetes Service

Issue/Introduction

• Objects in NSX UI are stuck "In Progress"
• An NSX Manager has no leadership in the cluster for the MANAGER role, even though it is not in Maintenance Mode.
  Inspect the output of the following command to see if one NSX Manager node UUID is not listed under the LEADER column of services under the Group Type MANAGER: get cluster status verbose
• Cluster status for MANAGER role is STABLE.
• API calls from external products such a Tanzu, VKS, or vRealize Automation/VCF Automation may experience RPC timeouts while creating or managing objects.
• ESX hosts may randomly go to "Unknown" status in NSX UI
  
• Log lines similar to the below are encountered in /var/log/proton/nsxapi.log
Leadership lease size is 0 for group ########-####-####-####-############ and service <NSX_SERVICE_NAME>
  Note: This log line may repeat on all NSX Managers for a large number of services.  The key text is highlighted.
• One or more NSX Managers' /var/log/proton/nsxapi.log may show log lines similar to:
  

  Category: SMALL :: Total weight: 0, Max capacity: 0, Current occupied weight: 0, holds leadership for services: {}
  Category: MEDIUM :: Total weight: 0, Max capacity: 0, Current occupied weight: 0, holds leadership for services: {}
  Category: LARGE :: Total weight: 0, Max capacity: 0, Current occupied weight: 0, holds leadership for services: {}

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

• VMware NSX
• vRealize Automation
• VCF Automation
• VMware Tanzu Platform - Kubernetes
• VMware vSphere Kubernetes Service (VKS)

Cause

One or more NSX Manager nodes is not participating the MANAGER role and has no leadership assigned.

Resolution

This issue is resolved in VMware NSX 4.2.3.2 and VCF NSX 9.0, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Workaround:

• Access the admin CLI of the affected NSX Manager (the one without any leadership of service for group MANAGER).
• Stop the proton service: service proton stop
  Because the NSX Manager is not participating in the MANAGER cluster group, there's no impact to stop the proton service.
• Wait 1 minute.
• Start the proton service: service proton start

Additional Information

NSX UI のオブジェクトが「進行中」のままになる