[
https://issues.apache.org/jira/browse/CLOUDSTACK-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav resolved CLOUDSTACK-275.
------------------------------------
Resolution: Won't Fix
This is expected as the old entities were still using internal ids and not
uuids, but new entities will have uuids. So, you client/scripts should just
assume in response a string which can looks like uuids or long ints but the
client/scripts should use the returned fields as string to query further.
ApiServer should handle the translation.
> hostid not always a UUID
> ------------------------
>
> Key: CLOUDSTACK-275
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-275
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: pre-4.0.0
> Reporter: Kenneth Bell
> Assignee: Rohit Yadav
> Priority: Minor
> Fix For: 4.1.0
>
> Attachments: api.xml
>
>
> The hostid field in virtualmachines is not always a valid UUID. For
> Destroyed and Expunging VMs the hostid can be '0', instead of a 'null' UUID,
> or not-present.
> See attached (api.xml) for an example.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
