NSXAdvancedLBAdapter_623150.log.1:Caused by: org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://vasxxxxxx.edu.gov/api//cluster": PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
ERROR [pool-461879-thread-3] (10943) com.vmware.vcops.NSXAdvancedLBAdapter.getCloud - Error while fetching clouds
org.springframework.web.client.HttpServerErrorException$BadGateway: 502 Bad Gateway: "{"error": "Bad service"}<EOL><EOL>"
at org.springframework.web.client.HttpServerErrorException.create(HttpServerErrorException.java:108) ~[avisdk-21.1.4-jar-with-dependencies.jar:?]
at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:170) ~[avisdk-21.1.4-jar-with-dependencies.jar:?]
at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:122) ~[avisdk-21.1.4-jar-with-dependencies.jar:?]
at org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63) ~[avisdk-21.1.4-jar-with-dependencies.jar:?]
at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:819) ~[avisdk-21.1.4-jar-with-dependencies.jar:?]
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:777) ~[avisdk-21.1.4-jar-with-dependencies.jar:?]
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:732) ~[avisdk-21.1.4-jar-with-dependencies.jar:?]
at org.springframework.web.client.RestTemplate.getForObject(RestTemplate.java:343) ~[avisdk-21.1.4-jar-with-dependencies.jar:?]
at com.vmware.vcops.client.AviApi.getForObjectList(AviApi.java:150) ~[nsx-alb.jar:?]
at com.vmware.vcops.client.AviClient.getCloud(AviClient.java:103) ~[nsx-alb.jar:?]
at com.vmware.vcops.manager.CloudManager.collect(CloudManager.java:53) ~[nsx-alb.jar:?]
at com.vmware.vcops.dataprovider.AviDataProvider$2.run(AviDataProvider.java:179) ~[nsx-alb.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[?:?]
at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
at java.lang.Thread.run(Unknown Source) ~[?:?]
ERROR [pool-461879-thread-3] (10943) com.vmware.vcops.NSXAdvancedLBAdapter.run - Failed to initiate resource collection
java.lang.NullPointerException: null
at com.vmware.vcops.manager.CloudManager.collect(CloudManager.java:55) ~[nsx-alb.jar:?]
at com.vmware.vcops.dataprovider.AviDataProvider$2.run(AviDataProvider.java:179) ~[nsx-alb.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[?:?]
at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
at java.lang.Thread.run(Unknown Source) ~[?:?]
Aria Operations 8.X integration with NSX-ALB completes and the test is successful, but after the integration is saved, the cloud proxy status shows "No data receiving" or "Unable to Establish Connection to NSX Advanced LB Endpoint"
Deleting the certificate, and testing the integration, works, and can be saved, but the instance state still shows the same error messages.
In some cases, this issue can be resolved by taking the cluster offline, bringing it back online, and rebooting the cloud proxy VM. As it's recommended to take snapshots of the analytics node before following the steps below, verify if the issue persists after taking snapshots.
Best practices for taking snapshots is to take offline snapshots which will include a cluster restart. If the issue is resolved after a cluster/cloud proxy restart, go ahead and delete the snapshots, if it does not resolve, please proceed with the procedure below:
Note: Alternatively, you can navigate to Integrations > Data Sources, and edit the NSX management pack instance(s), click Validate Connection, and accept to pull in the new certificate.