add support for ovf transport com.vmware.guestInfo

Bug #1807466 reported by Scott Moser
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released
Scott Moser

Bug Description

cloud-init OVF datasource currently supports the OVF "ISO" transport (attached cdrom).
It should be updated to also support the com.vmware.guestInfo transport.

In this transport the ovf environment file can be read with:
 vmtoolsd "--cmd=info-get guestinfo.ovfEnv"

Things to note:
a.) I recently modified ds-identify to invoke the vmtoolsd command above
in order to check the presense of the transport. It seemed to work
fine, running even before open-vm-tools.service or vgauth.service was
up. See for those changes.
I think this can be made acceptable if do so only when on vmware.

b.) You can deploy a VM like this using OVFtool and the official Ubuntu OVA files. You simply need to modify the .ovf file inside the .ova to contain
   <VirtualHardwareSection ovf:transport="iso com.vmware.guestInfo">
Having both listed will "attach" both when deployed.

c.) after doing this and getting the changes into released ubuntu
we should change the official OVA on to have
the com.vmware.guestInfo listed as a supported transport.

Example ovftool command to deploy:
  ovftool --datastore=SpindleDisks1 \
     --name=sm-tmpl-ref \
     modified-bionic-server-cloudimg-amd64.ovf \
     "vi://<email address hidden>:$PASSWORD@"

Related branches

Scott Moser (smoser)
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Scott Moser (smoser)
Revision history for this message
Server Team CI bot (server-team-bot) wrote :

This bug is fixed with commit f55bb17d to cloud-init on branch master.
To view that commit see the following URL:

Changed in cloud-init:
status: Confirmed → Fix Committed
Revision history for this message
Dan Watkins (oddbloke) wrote :

Added the cloud-images project to capture the image changes that will be required to make this available as a transport by default.

Revision history for this message
Chad Smith (chad.smith) wrote : Fixed in cloud-init version 19.1.

This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.