Symptoms:
- When reviewing the Cloud Director Availability On-Premises appliance configuration through the Cloud Director Availability vSphere Client Plug-In, you see a similar error:
The request can not be processed, because the HTTP method for the resource is not supported.
- In /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log on vCenter server, you see entries similar to:
[2020-07-03T01:30:52.719Z] [WARN ] http-nio-5090-exec-17 com.vmware.rest.client.AbstractRestClient The HTTP response has no body. Code = 405, reason =
[2020-07-03T01:30:52.741Z] [ERROR] http-nio-5090-exec-17 com.vmware.h4.vsphere.ui.controller.C4ProxyController Backend responded with error java.lang.reflect.InvocationTargetException: Failed to mirror replicator call: GET /config/network/dns
at com.vmware.h4.vsphere.ui.controller.C4ProxyController.mirrorReplicatorRequest(C4ProxyController.java:451)
at com.vmware.h4.vsphere.ui.controller.C4ProxyController.access$400(C4ProxyController.java:54)
at com.vmware.h4.vsphere.ui.controller.C4ProxyController$2.call(C4ProxyController.java:168)
...
Caused by: com.vmware.rest.client.exception.UnexpectedJsonResponseStatusError: Unexpected response status: 405
at com.vmware.rest.client.converters.DefaultJsonConverter.deserializeError(DefaultJsonConverter.java:55)
at com.vmware.rest.client.AbstractRestClient.convert(AbstractRestClient.java:219)
at com.vmware.rest.client.json.RestClient.exchange(RestClient.java:104)
at com.vmware.h4.vsphere.ui.controller.C4ProxyController.mirrorReplicatorRequest(C4ProxyController.java:438)
... 122 common frames omitted
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.