Unable to Deploy NSX Advanced Load Balancer in 5.2.
Article ID: 378048
Updated On:
Products
Issue/Introduction
While trying to deploy NSX Advanced load balancer from the SDDC manager, we get the error - " NSX Advanced Load Balancer version 22.1.6-23390967 image is not compatible with NSX_T_MANAGER 4.2.0.1.0-24210154 and VCENTER 8.0.3.00100-24091160."
Environment
VMware Cloud Foundation 5.2
Cause
SDDC manager is configured with the proxy and fails to update the VVS Compatibility Data, since the URL vvs.esp.vmware.com is not being allowed.
lcm.log:
2024-09-19T07:45:34.646+0000 INFO [vcf_lcm,66ebd663d3a2ed7be19a1ca3077e1b59,99e1] [c.v.e.s.l.s.i.BundleDownloadPostHandler,vac-scheduler-1] Downloading patchAndInstallBundles []
2024-09-19T07:45:35.055+0000 INFO [vcf_lcm,c655b7c49f214920,954c] [c.v.v.l.r.a.c.v.s.DepotSettingsController,http-nio-127.0.0.1-7400-exec-8] Fetching depot settings
2024-09-19T07:45:35.730+0000 INFO [vcf_lcm,66ebd69faba783b5890de0e613e8e61e,4b13] [c.v.v.c.c.i.v.r.client.VvsApiClient,vac-scheduler-1] vvs uri with query params: https://vvs.esp.vmware.com/v1/products/bundles/type/vcf-lcm-v2-bundle?format=json
2024-09-19T07:45:36.746+0000 WARN [vcf_lcm,66ebd69faba783b5890de0e613e8e61e,f097] [o.a.h.c.h.impl.classic.ConnectExec,vac-scheduler-1] ex-0000001347 Negotiate{FAILED } authentication error: Invalid name provided (Mechanism level: KrbException: Cannot locate default realm)
2024-09-19T07:45:36.794+0000 ERROR [vcf_lcm,66ebd69faba783b5890de0e613e8e61e,4b13] [c.v.e.s.l.c.s.VmwareCompatibilityDataDownloadScheduler,vac-scheduler-1] VVS Compatibility Data update failed
com.vmware.vcf.compatibility.controllers.internal.vvs.exception.VvsException: The VVS api call to https://vvs.esp.vmware.com/v1/products/bundles/type/vcf-lcm-v2-bundle?format=json failed. Response: CONNECT refused by proxy: HTTP/1.1 407 Proxy Authentication Required
at com.vmware.vcf.compatibility.controllers.internal.vvs.rest.client.VvsApiClient.getBundlesFromApi(VvsApiClient.java:146)
at com.vmware.vcf.compatibility.controllers.internal.vvs.rest.client.VvsApiClient.getAllProductBundleDetails(VvsApiClient.java:88)
at com.vmware.vcf.compatibility.controllers.internal.vvs.VvsCompatibilityController.getCompatibilityDataFromRemote(VvsCompatibilityController.java:490)
at com.vmware.vcf.compatibility.validator.internal.CompatibilityControllerAggregator.getCompatibilityDataFromRemote(CompatibilityControllerAggregator.java:1314)
at com.vmware.vcf.compatibility.validator.internal.CompatibilityControllerAggregator.getCompatibilityDataFromRemote(CompatibilityControllerAggregator.java:1302)
at com.vmware.vcf.compatibility.validator.internal.service.CompatibilityValidatorServiceImpl.getCompatibilityDataFromRemote(CompatibilityValidatorServiceImpl.java:292)
Resolution
If proxy is configured in the environment, then we need to ensure that the URL to fetch the VVS Compatibility data, must be allowed -
In other similar cases if you see the error CONNECT refused by proxy in the logs, follow the KB - Public URL list for SDDC Manager to ensure you have allowed the required URLs for online functionality in an VCF environment.
Feedback
