VSphere instance ID being set to hostname instead of product UUID

[Stone Preston]

On Vsphere clouds, the instance IDs of juju machines are using the hostname of the machine when they should be using the product UUID. Currently the instance id looks like this: juju-648670-0, however VSphere product IDs located in /sys/class/dmi/id/product_uuid look like 4229790e-7ec7-8685-b2e5-57e59d139d67.

On other clouds like aws this does not happen and the correct cloud specific ID is used as the instance ID (ie on aws the instance ID matches the ami info: i-0546cffafe21a9439)

[Heather Lanigan (hmlanigan)]

Hi Stone,

Please provide the use case for this. How does this impact you? It'll be helpful in fixing the issue.

[Stone Preston (stonepreston)]

kubernetes cloud providers typically use this special ID when setting the providerID field of nodes. We have some applications that may need to be able to match up juju machines to nodes based on this provider ID. on AWS the providerID and juju instance ID match up (well the providerID contains the juju instance ID, along with some other data out in front), but not on Vsphere

[Joseph Phillips (manadart)]

We currently set/get this from VirtualMachine.ManagedEntity.Name.
The ID *might* be in VirtualMachine.ManagedEntity.Guest.GuestID