[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova

[John Chittum]

image builds are only built after the SRU process is complete and
livecd-rootfs is in the updates pocket. This wiki page will help explain
the SRU process in more detail:

https://wiki.ubuntu.com/StableReleaseUpdates

   My verification is being done by building images against the livecd-
rootfs project in proposed. After verification by all the bugs affecting
a version of a package, a minimum 7 day wait period for community
testing against proposed, the package will move to updates

   Once the package has been accepted into updates, the CPC pipeline
will pick up the accepted version of livecd-rootfs, and create daily
images.

   I'll update this ticket once we have confirmed daily builds for the
suites that are still affected.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1893898

Title:
  open-vm-tools status is toolsNotInstalled after deploy cloud image
  groovy-server-cloudimg-amd64.ova

Status in cloud-images:
  In Progress
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Groovy:
  Fix Released

Bug description:

  [Impact]

   * with groovy-server-cloudimg-amd64.ova daily build, when only deploy OVA and don't power on VM, the VMTools status is "toolsNotInstalled"
  But in fact, we have installed open-vm-tools.

  [Test Case]

   * build vmdk image and verify that buildlog now mentions emitting
  ddb.toolsVersion = "2147483647" field for the image. See
  https://bugs.launchpad.net/ubuntu/+source/open-vm-
  tools/+bug/1893898/comments/12

  [Regression Potential]

   * The change affects Vagrant / VMware ova/vmdk formatted images,
  which all use modify_vmdk_header function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions