VMware {code} Community
micmaher0
Contributor
Contributor

Unexpected response from vCenter API

Hi All,

I am querying the API for a VPSC and getting an unexpected result. I have tried this on two VPSC systems and seen the same issue.

The API path I am querying is Software Packages and is documented here . . .

https://code.vmware.com/apis/60/vcenter-server-appliance-management#/health47softwarepackages32

According to the API specification, these are the values I should get . . .

"Get information on available software updates available in remote VUM repository. red indicates that security updates are available. orange indicates that non security updates are available. green indicates that there are no updates available. gray indicates that there was an error retreiving information on software updates"

We have not updated our VPSC since it was built in March 2018. I configured to check for automatic updates a few hours ago and it found a critical update is available. Described here . . .

https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-vcenter-server-65u2d-release-notes.html#ful...

When I query the VPSC in the API I expect to get a return status of red.

VERBOSE: GET https://VPSCl/rest/appliance/health/software-packages with 0-byte payload

VERBOSE: received -1-byte response of content type application/json

green

I can also view this result on my vCenter/VPSC host in the API explorer Swagger UI here (it also returns green)

https:/VPSC/apiexplorer/#!/health_softwarepackages_/get_appliance_health_software_packages

I want to ask, is this a bug or am making the wrong API call to check for critical patches?

Thanks,

Michael

Tags (2)
Reply
0 Kudos
2 Replies
sk84
Expert
Expert

Which version of vcsa are you using? And do you have enabled the automatic update checking in the VAMI?

Because I've found another thread about the same problem:

vCSA VAMI API through PowerCLI returns different value for updates available

According to the information in the other post, the API description is wrong. Green means that the service is healthy. But I don't know if this is still true for vcsa 6.7 update 1.

--- Regards, Sebastian VCP6.5-DCV // VCP7-CMA // vSAN 2017 Specialist Please mark this answer as 'helpful' or 'correct' if you think your question has been answered correctly.
micmaher0
Contributor
Contributor

Yes that's it, the link you sent is my problem to sk84

My version is 6.5 build 8024368

Reply
0 Kudos