You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
calls to this method do not return the following "identity": { "bios_uuid": "string", "instance_uuid": "string", "name": "string" }
Calls directly to the rest api @url/rest/vcenter/vm/vm-1 fails to return this info. In particular, I'm looking for that instance_uuid
I also tried client.vcenter.vm.guest.Identity.get('vm-1') to no avail. The VM is powered on.
Reproduction steps
1. Install latest SDK, or access REST API directly
2. Attempt to retrieve VM instance uuid through Get VM methods as documented
3. Attempted on vsphere 6.7.0
...
Expected behavior
As per the published documentation, the GetVm methods should return identity information, to include the instanceID
Additional context
As well, the online docs noted above globs vsphere 6.5-7.0U2, so it is not possible to tell if this is a vsphere versioning issue.
I am using full Administrator privileges
The text was updated successfully, but these errors were encountered:
Describe the bug
Per documentation, https://developer.vmware.com/apis/vsphere-automation/v7.0.0/vcenter/data-structures/VM/Get/ResponseBody/
calls to this method do not return the following
"identity": { "bios_uuid": "string", "instance_uuid": "string", "name": "string" }
Calls directly to the rest api
@url/rest/vcenter/vm/vm-1
fails to return this info. In particular, I'm looking for that instance_uuidI also tried
client.vcenter.vm.guest.Identity.get('vm-1')
to no avail. The VM is powered on.Reproduction steps
Expected behavior
As per the published documentation, the GetVm methods should return identity information, to include the instanceID
Additional context
As well, the online docs noted above globs vsphere 6.5-7.0U2, so it is not possible to tell if this is a vsphere versioning issue.
I am using full Administrator privileges
The text was updated successfully, but these errors were encountered: