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

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-rootfs/+merge/394142

** Merge proposal linked:
   https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-rootfs/+merge/394144

** Merge proposal linked:
   https://code.launchpad.net/~jchittum/livecd-rootfs/+git/livecd-rootfs/+merge/394145

-- 
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:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in livecd-rootfs source package in Focal:
  New
Status in livecd-rootfs source package in Groovy:
  Fix Committed

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