Invalid credentials error or Null Pointer Exception when accessing NSX Advanced Load Balancer in VMware Cloud Director 10.6
search cancel

Invalid credentials error or Null Pointer Exception when accessing NSX Advanced Load Balancer in VMware Cloud Director 10.6

book

Article ID: 425043

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

This article provides steps to resolve an issue where accessing the NSX Advanced Load Balancer configuration within VMware Cloud Director fails with a Null Pointer Exception.

  • Administrators are unable to view or manage NSX Advanced Load Balancer settings from the VMware Cloud Director UI.
  • The operation fails with a generic error or a Null Pointer Exception (NPE) in the user interface.
  • The /opt/vmware/vcloud-director/logs/vcloud-container-debug.log on the VCD cell contains a stack trace similar to the following:

    com.vmware.vcloud.common.network.NsxAlbApiException: Invalid credentials at com.vmware.vcloud.fabric.net.nsxalb.NsxAlbRestTemplateErrorHandler.handleError(NsxAlbRestTemplateErrorHandler.java:46)

Environment

10.6

Cause

This issue occurs when the credentials for the AVI Controller stored within the VMware Cloud Director infrastructure configuration do not match the current credentials on the AVI Controller itself. This frequently happens after a password rotation or update is performed directly on the AVI Controller but not synchronised with VCD.

Resolution

To resolve this issue, you must update the AVI Controller registration in VCD with the correct credentials.

  1. Log in to the VMware Cloud Director Provider Portal as a System Administrator.
  2. Navigate to Infrastructure > Resources > NSX ALBs.
  3. Select the Controllers tab.
  4. Locate the specific Controller causing the issue and click Edit.
  5. In the Username and Password fields, enter the current valid credentials for the AVI Controller.
  6. Click Save.
  7. Wait for the task to complete and verify that the status is green/connected.
  8. Retry accessing the Load Balancer configuration to confirm the error is cleared.