open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
Bug #1893898 reported by
vmware-gos-Yuhua
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
High
|
John Chittum | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
John Chittum | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* with groovy-
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:/
[Regression Potential]
* The change affects Vagrant / VMware ova/vmdk formatted images, which all use modify_vmdk_header function.
Related branches
~jchittum/livecd-rootfs:xenial-open-vm-tools-update
- Robert C Jennings (community): Approve
- Ubuntu Core Development Team: Pending requested
-
Diff: 78 lines (+37/-13)2 files modifieddebian/changelog (+6/-0)
live-build/functions (+31/-13)
~jchittum/livecd-rootfs:bionic-open-vm-tools-backport
- Robert C Jennings (community): Approve
- Ubuntu Core Development Team: Pending requested
-
Diff: 78 lines (+37/-13)2 files modifieddebian/changelog (+6/-0)
live-build/functions (+31/-13)
~jchittum/livecd-rootfs:focal-open-vm-tools-update
- Robert C Jennings (community): Approve
- Ubuntu Core Development Team: Pending requested
-
Diff: 78 lines (+37/-13)2 files modifieddebian/changelog (+6/-0)
live-build/functions (+31/-13)
~jchittum/livecd-rootfs:ensure-vmtools-in-vmdk-header
- Robert C Jennings (community): Approve
- Ubuntu Core Development Team: Pending requested
-
Diff: 82 lines (+35/-21) (has conflicts)2 files modifieddebian/changelog (+8/-0)
live-build/functions (+27/-21)
information type: | Public → Private |
information type: | Private → Public |
Changed in livecd-rootfs (Ubuntu): | |
status: | Confirmed → In Progress |
assignee: | nobody → John Chittum (jchittum) |
Changed in cloud-images: | |
status: | Confirmed → In Progress |
assignee: | nobody → John Chittum (jchittum) |
importance: | Undecided → High |
Changed in livecd-rootfs (Ubuntu): | |
milestone: | ubuntu-20.10 → groovy-updates |
no longer affects: | open-vm-tools (Ubuntu Xenial) |
no longer affects: | open-vm-tools (Ubuntu Bionic) |
no longer affects: | open-vm-tools (Ubuntu Focal) |
no longer affects: | open-vm-tools (Ubuntu Groovy) |
Changed in livecd-rootfs (Ubuntu Groovy): | |
status: | New → In Progress |
description: | updated |
no longer affects: | open-vm-tools (Ubuntu) |
tags: |
added: verification-done removed: verification-needed |
To post a comment you must log in.
To include VMTools version info to ova template, write 'ddb.toolsVersi on=2147483647' to the VMDK file before create the template.
VDDK SDK VixDiskLib_ WriteMetadata API can be used to write "ddb.toolsVersion" metadata - https:/ /code.vmware. com/docs/ 11750/virtual- disk-developmen t-kit-programmi ng-guide/ GUID-C13FE900- 6B19-4082- A040-354FB1F60B CB.html /code.vmware. com/web/ sdk/7.0/ vddk
VDDK SDK: https:/
Here is an example: https:/ /github. com/vmware/ photon/ blob/master/ support/ image-builder/ ovagenerator. py#L53