← Back to team overview

group.of.nepali.translators team mailing list archive

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

 

This bug was fixed in the package livecd-rootfs - 2.664.10

---------------
livecd-rootfs (2.664.10) focal; urgency=medium

  * Do not hard-code the UC20 amd64 image size to 8GB as now ubuntu-image
    should be able to properly calculate the needed size itself.
  * But per discussion, we might want to keep the UC20 images a bit bigger than
    what's defined via the gadget/rootfs contents, to make sure writable is
    comfortably big enough. Use the same hard-coded value as for UC16 and UC18.
    (LP: #1905990)

livecd-rootfs (2.664.9) focal; urgency=medium

   [ John Chittum]
   * Backport Ensure toolsVersion set in vmdk header (LP: #1893898)

   [ Dimitri John Ledkov & Joshua Powers ]
   * amd64: always install grub-pc with shim-signed (LP: #1901906), and
     ensure to autoremove packages

 -- Łukasz 'sil2100' Zemczak <lukasz.zemczak@xxxxxxxxxx>  Fri, 27 Nov
2020 17:58:38 +0100

** Changed in: livecd-rootfs (Ubuntu Focal)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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 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 Released
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