group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #38307
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
vmware-gos-Yuhua (yhzou) and cloud users:
The latest Xenial daily build has the required changes, serial 20210127
http://cloud-images.ubuntu.com/xenial/20210127/
The vmdk and ova were both validated in the following way:
1) downloaded vmdka and ova from http://cloud-images.ubuntu.com/xenial/20210127/
2) launch virtualbox
3) select Add and choose the vmdk
4) give unique name (xenial-jchittum-test) and ensure linux ubuntu is chosen for OS info.
5) Go to settings, and set a serial port (file) and added a working cloud_init (sets ubuntu password and imports my launchpad id)
6) boot image
7) check `cloud-init status`, `systemctl is-system-running`, `uname -a` to ensure the services are up, running, complete, and correct kernel is up
8) quit and terminate VM
9) Import .ova
10) repeat steps 4-8
Images were found to generally be working and the required change was
found in our build logs
** Changed in: cloud-images
Status: In Progress => 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:
Fix Released
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Xenial:
Fix Released
Status in livecd-rootfs source package in Bionic:
Fix Released
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