Editing Compute Manager fails with error "Field level validation errors: {value 0 of property reverse_proxy_https_port has violated the minimum valid value 1}"

Products

• VMware NSX

Issue/Introduction

• NSX Manager has been deployed in vCenter using the embedded deployment option with the non-embedded OVF.
• Updating the Compute Manager thumbprint or enabling the "Create Service Account" option fails with error similar to:

• Registering the Compute Manager from the NSX manager UI fails with error similar to:  

   "Compute Manager VcLink registration failed because of Unknown error in processing request for CM vcenter###.####.####### with id #####-######-#####-#################." 

• In /var/log/syslog on the NSX Manager you see errors similar to:
  

  2022-12-20T08:50:10.390Z nsx-mgr-01 NSX 9270 - [nsx@6876 comp="nsx-manager" level="WARNING" reqId="########-####-####-####-############" subcomp="manager" username="admin"] API result did not pass validationField level validation errors: {value 0 of property results[0].reverse_proxy_https_port has violated the minimum valid value 1}, {value of property results[0].access_level_for_oidc is not one of the allowed values [FULL, LIMITED]}

Environment

VMware NSX

Cause

This issue occurs when the Unified OVA is used to deploy NSX Manager rather than using the Embedded Unified OVF. 

Check Install NSX Manager from vSphere Client for more information on deploying NSX Manager in vCenter as a plugin. In particular, reference the section related to the OVF and which one to use:

If you enter a URL to download the OVF file, ensure the URL points to a secure HTTPS server. For example, https://<OVF-URL>. There is a separate OVF file available for NSX Manager deployed from vSphere Client. You must select a OVF file name using the following convention: nsx-embedded-unified-appliance-<releaseversion.buildversion>.ovf. Do not use the nsx-unified-appliance-<releaseversion.buildversion>.ova file.

Resolution

This is a known issue impacting VMware NSX. If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.

Additional Information

If you are contacting Broadcom support about this issue, please provide the following:

• NSX Manager log bundles
• Text of any error messages seen in NSX GUI or command lines pertinent to the investigation

Handling Log Bundles for offline review with Broadcom support:

• Collect Support Bundles (NSX) 
• Uploading files to cases on the Broadcom Support Portal
• Creating and managing Broadcom support cases