OPERATIONAL DEFECT DATABASE
...
...
Customer may report an issue where "GetAppliance" API call failed to execute and below error can be seen in the API response.API: curl --location --request GET 'https://hcx_mgr_IP/hybridity/api/interconnect/appliances' \ Response: <?xml version='1.0' encoding='UTF-8'?> <com.vmware.vchs.hybridity.api.common.model.ErrorResponse> <errors> <com.vmware.vchs.hybridity.api.common.model.Error> <code>E_INVALID_SCHEMA</code> <message>JSONObject["networks"] not found.</message> </com.vmware.vchs.hybridity.api.common.model.Error> </errors> </com.vmware.vchs.hybridity.api.common.model.ErrorResponse>
This resource is to inform all about HCX GetAppliance API failure and how to recover that.
This behavior could be seen in the below circumstances: For the environments where SM/Fleet Appliances got deployed partially and got failed to cleanup in the backend.SM/Fleet Appliances got deployed successfully but the appliances got forcefully removed/deleted by user from vCenter UI.
This issue will be ONLY observed in GetAppliance API call executed through HCX API explorer or POSTMAN application. Note: This will also be observed through PowerCLI "get-hcxappliance" cmdlet. The SM/Appliances status will remain accessible through UI.
None
Please open a service request with VMware support team for further assistance.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
