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

To include VMTools version info to ova template, write 'ddb.toolsVersion=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-development-kit-programming-guide/GUID-C13FE900-6B19-4082-A040-354FB1F60BCB.html
VDDK SDK: https://code.vmware.com/web/sdk/7.0/vddk

Here is an example: https://github.com/vmware/photon/blob/master/support/image-builder/ovagenerator.py#L53

Status changed to 'Confirmed' because the bug affects multiple users.

Hi,
is that a bug in open-vm-tools at all?
Or more likely in the way the .ova is built?

I start to ping some people, but if it is clear to you Yuhua/Penppeng then please let me know.

If it is in open-vm-tools what would you expect to change there?

The OVA we're providing[1] is built with this[2] binary hook in livecd-rootfs which wraps up the VMDK created using the create_vmdk[3] function. That function calls modify_vmdk_header to set the tools version; this code is unchanged from when it was added in early 2017.

[1] https://cloud-images.ubuntu.com/groovy/current/groovy-server-cloudimg-amd64.ova
[2] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-cpc/hooks.d/base/vmdk-ova-image.binary
[3] https://git.launchpad.net/livecd-rootfs/tree/live-build/functions#n229

But that function is sed'ing the file created by python3-vmdkstream so we'll look into it. The vmdk-stream-converter source package has had a minor change between focal and groovy but it doesn't explain this issue.

Okay, the vmdk lacks the version in bionic, focal, and groovy. The ddb.comment field that toolsVersion uses is missing:

# Disk Descriptor File
# Created by VMDKstream
version=1
CID=7e5b80a7
parentCID=ffffffff
createType="streamOptimized"

# Extent description
RDONLY 20971520 SPARSE "call-me-stream.vmdk"

#DDB

ddb.adapterType = "lsilogic"
# 20971520 / 63 / 255 rounded up
ddb.geometry.cylinders = "1306"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "8f15b3d0009d9a3f456ff7b28d324d2a"
ddb.virtualHWVersion = "7"^@^@^@^

So we need to fix livecd-rootfs to correctly add the tools version field to the vmdk header *and* add a check that it got there.

Thank you for the bug report. I have confirmed this issue and flagged the correct project, livecd-rootfs, for this work.

Thanks Robert for the quick confirmation, so I assume that the bionic, focal, and groovy images will be updated to include VMTools version info. We will let customer to retry once the new images are available.

Also confirmed that this affects Xenial images.

MP is up, will make revisions shortly based on feedback. Due to the release Thursday, this won't be included in the Groovy Gorilla day 1. We'll have this in shortly after release, and work work the SRU process from the H release to Groovy, Focal, Bionic, and Xenial.

hit the issue with groovy-server-cloudimg-amd64.ova daily build 23-Oct-2020

initial fix has been merged into Hirsute, and is currently in proposed. I did the following test using the deb src of release 2.697 from proposed (now superseded by 2.698)

1. downloaded dev source
2. unpacked
3. used ubuntu-oldfashioned/scripts/ubuntu-bartender to run a hirsute build

```
./ubuntu-bartender --livecd-rootfs-dir /home/jchittum/dev01/troubleshooting/various-rootfs/2.697/livecd-rootfs/ --build-provider multipass -- --series hirsute --project ubuntu-cpc --image-target vmdk
```
4. Verified via the log the new descriptor was written. The build log now prints the descriptor files. copied below
5. Verified ova and vmdk booted using Virtualbox.

Once the package moves from proposed to updates, we'll be able to produce a test hirsute image to verify the change, then work on SRUing the changes to all suites.

build log below:

+ echo 'Cat'\''ing original descriptor to console for debugging.'
Cat'ing original descriptor to console for debugging.
+ cat /tmp/tmp.LMSTXgWc8d
# Disk Descriptor File
# Created by VMDKstream
version=1
# Believe this is random
CID=7e5b80a7
# Indicates no parent
parentCID=ffffffff
createType="streamOptimized"

# Extent description
RDONLY 20971520 SPARSE "call-me-stream.vmdk"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
# 20971520 / 63 / 255 rounded up
ddb.geometry.cylinders = "1306"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
# Believe this is random
ddb.longContentID = "8f15b3d0009d9a3f456ff7b28d324d2a"
ddb.virtualHWVersion = "7"
+ echo ''
+ echo -n 'ddb.toolsVersion = "2147483647"'
+ echo 'Printing diff of original and new descriptors.'
Printing diff of original and new descriptors.
+ cat
+ diff --text /tmp/tmp.LMSTXgWc8d /tmp/tmp.K3j1jxkbgk
23c23,24
< ddb.virtualHWVersion = "7"^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
\ No newline at end of file
---
> ddb.virtualHWVersion = "7"
> ddb.toolsVersion = "2147483647"
\ No newline at end of file

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

---------------
livecd-rootfs (2.698) hirsute; urgency=medium

  * amd64: always install grub-pc with shim-signed (LP: #1901906)
  * control: install qemu-utils & snapd on riscv64.

 -- Dimitri John Ledkov <email address hidden> Thu, 29 Oct 2020 22:22:30 +0000

I will verify it. Thanks

The latest hirsute cloud image ova and vmdk include this change. These can be downloaded from:

http://cloud-images.ubuntu.com/hirsute/20201103/

My initial checks show correct headers and images boot fine using Virtualbox. I'll await confirmation from vmware-gos-Yuhua before marking complete and beginning the SRU process.

> John Chittum (jchittum) wrote on 2020-11-03: #15
> The latest hirsute cloud image ova and vmdk include this change. These can be downloaded from:

  > http://cloud-images.ubuntu.com/hirsute/20201103/

Hi John Chitum:
  I hit 404 not found when click http://cloud-images.ubuntu.com/hirsute/20201103/

Best regards
Yuhua Zou

   > Hi John Chitum:
   > I hit 404 not found when click http://cloud-images.ubuntu.com/hirsute/20201103/

Please ignore the risk. I am downloading OVA from http://cloud-images.ubuntu.com/hirsute/current for testing

Best regards
Yuhua Zou

Hello vmware-gos-Yuhua, or anyone else affected,

Accepted livecd-rootfs into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.694.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

The tools status is "Not running, version:2147483647 (Guest Managed)" after
deploy OVA without PowerOn with cloud image from http://cloud-images.ubuntu.com/hirsute/20201108/

The tools version is not correct.

After PowerOn, the tools status is "Running, version:11328 (Guest Managed)"
After PowerOn and PowerOff, the tools status is "Not running, version:11328 (Guest Managed)"

We expect the tools status is "Not running, version:11328 (Guest Managed)" after
deploy OVA without PowerOn.

Best regards
Yuhua Zou

I've confirmed the Groovy change using the following test:

1. downloaded source for proposed package
2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build
3. used Virtualbox to load the ova and vmdk
4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded
5. created a custom recipe with the proposed code from git(emulating our exact build process)
6. ran a livebuild from the uploaded recipe
7. downloaded the ova and vmdk
8. using Virtualbox, ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded.

Hi John Chittum or anyone else:
   The tools status is OK with the OVA http://cloud-images.ubuntu.com/hirsute/20201108/.
   But tools version is not correct. It seems to be random number.

   If you have any updated OVA, please let me know. I will verify it with your provided OVA.
   Thanks very much.

Best regards
Yuhua Zou

  > vmware-gos-Yuhua (yhzou)#21

clarification from vmware'dev:
  For ubuntu cloud image(with suffix .ova ), the tools status is "Not running, version:2147483647 (Guest Managed)" after deploy OVA without PowerOn.
  The magic number 2147483647 is expected. Once it's power-on, the version will be overwritten

Best regards
Yuhua Zou

Hi John Chittum or anyone else:
   Pass the test with you provided OVA http://cloud-images.ubuntu.com/hirsute/20201108/.

   Thanks very much.

Best regards
Yuhua Zou

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

---------------
livecd-rootfs (2.694.1) groovy; urgency=medium

  * livecd-rootfs SRU of change up to 2.699 from hirsute to groovy.

  = hyperv gallery image =
  [ Jinming Wu, Patrick ]
  * hyper-v hook: Fix writing of pkla file out to correct scratch
    directory for image build. LP: #1901846
  [ Dimitri John Ledkov ]
  * auto/config: seed ubuntu-desktop when building hyperv image LP: #1901846
  * auto/config: scope ubuntu:desktop-preinstalled:raspi image options LP: #1901846

  = CPC cloud images =
  [ Dimitri John Ledkov & Joshua Powers ]
  * amd64: always install grub-pc with shim-signed (LP: #1901906), and
    ensure to autoremove packages
  [ John Chittum ]
  * Ensure vmtools version entered into vmdk header (LP: #1893898)

  = RISC-V port =
  * control: install qemu-utils & snapd on riscv64. (LP: #1903034)

 -- Dimitri John Ledkov <email address hidden> Thu, 05 Nov 2020 11:54:14 +0000

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

It does not include the fix when check with groovy-server-cloudimg-amd64.ova daily build 2020-11-18. Currently this is the newest daily build on http://uec-images.ubuntu.com/groovy/current/.

I will get daily build to check a few days later.

pass test with groovy-server-cloudimg-amd64.ova daily build 2020-11-25.

Hello vmware-gos-Yuhua, or anyone else affected,

Accepted livecd-rootfs into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.525.48 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello vmware-gos-Yuhua, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.408.64 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello vmware-gos-Yuhua, or anyone else affected,

Accepted livecd-rootfs into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.664.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted livecd-rootfs (2.408.64) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

livecd-rootfs/2.408.64 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

I've confirmed the Bionic change using the following test:

1. downloaded source for proposed package
2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build
3. used Virtualbox to load the ova and vmdk
4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded
5. created a custom recipe with the proposed code from git(emulating our exact build process)
6. ran a livebuild from the uploaded recipe
7. downloaded the ova and vmdk
8. using Virtualbox, ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded.
9 checked build logs for bartender and lp to ensure that a diff was generated for the 2 headers and that ddb.toolsVersion = "2147483647" was present in the diff presented in the log (example in #12)

I've confirmed the Focal change using the following test:

1. downloaded source for proposed package
2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build
3. used Virtualbox to load the ova and vmdk
4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded
5. created a custom recipe with the proposed code from git(emulating our exact build process)
6. ran a livebuild from the uploaded recipe
7. downloaded the ova and vmdk
8. using Virtualbox, ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded.
9 checked build logs for bartender and lp to ensure that a diff was generated for the 2 headers and that ddb.toolsVersion = "2147483647" was present in the diff presented in the log (example in #12)

LP builds have been a bit slow today for images and recipes.

For Xenial, I believe I have to wait for a fix in livecd-rootfs related to a different change.

The latest daily Build OVA is on 03-Dec-2020 at http://uec-images.ubuntu.com/.
I am afraid this daily build doesn't have the fix yet.

I will test the latest daily build OVA a few days later.

Best regards
Yuhua Zou

   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.

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 <email address hidden> Fri, 27 Nov 2020 17:58:38 +0100

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

---------------
livecd-rootfs (2.525.48) bionic; urgency=medium

   [ John Chittum ]
   * Ensure vmtools version entered into vmdk header (LP: #1893898)

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

   [ Patrick Viafore ]
   * Increase Vagrant disk size from 10G to 40G (LP: #1580596)

 -- Robert C Jennings <email address hidden> Fri, 20 Nov 2020 15:08:54 -0600

check focal-server-cloudimg-amd64.ova and find the latest daily build 10-Dec-2020 at http://uec-images.ubuntu.com/ doesn't have the fix.

focal and bionic builds with this fix were not completed prior to the December holidays. Builds with the changes for focal and bionic should happen soon in 2021.

Xenial is still awaiting a fix to be committed.

Hi! The packages were released into the archive on December 15, 2020. Our last build of 2020 was on December 10. The first daily builds of 2021 should have this fix.

Hi jchitum, Powers,
   Thanks for the info.

Best regards
Yuhua Zou

Hello vmware-gos-Yuhua, or anyone else affected,

Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd-rootfs/2.408.65 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted livecd-rootfs (2.408.65) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-image/1.10+16.04ubuntu1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

The latest xenial-server-cloudimg-amd64.ova 2021-01-12 doesn't have the fix.
I will wait next available build to verify it.

Thanks
Yuhua Zou

Focal Daily serial 20210112 has the expected change and is available for download:

http://cloud-images.ubuntu.com/daily/server/focal/20210112/

Bionic Daily serial 20120112 has the expected change, and is available for download:

http://cloud-images.ubuntu.com/daily/server/bionic/20210112/

Xenial: I am qualifying livecd-rootfs now. Once livecd-rootfs is qualified and moved to -updates, the cpc build process will take the change.

I've verified a build on xenial using 2.408.65

1. downloaded source for proposed package
2. used ubuntu-old-fashioned/scripts/ubuntu-bartender to run a build
3. used Virtualbox to load the ova and vmdk
4. ensured the ova and vmdk loaded, cloud-init loaded, systemd completed with no issues, and kernel was loaded

It has the fix with latest daily build for bionic-server-cloudimg-amd64.ova and focal-server-cloudimg-amd64.ova

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

---------------
livecd-rootfs (2.408.65) xenial; urgency=medium

  [ Joshua Powers ]
  * amd64: revert install grub changes on Xenial (LP: #1901906)

livecd-rootfs (2.408.64) xenial; urgency=medium

  [ Joshua Powers ]
  * amd64: always install grub-efi-amd64-signed (LP: #1901906)

livecd-rootfs (2.408.63) xenial; urgency=medium

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

livecd-rootfs (2.408.62) xenial; urgency=medium

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

  [ Patrick Viafore ]
  * Increase Vagrant disk size from 10G to 40G (LP: #1580596)

  [ Cody Shepherd ]
  * buildd: ext4: change tar transform target to match changes in bionic+
  * buildd: Skip jasper for buildd subproject
  * buildd: Create manifests for buildd tarballs

livecd-rootfs (2.408.61) xenial; urgency=medium

  * SRU: Enable bootable-buildd hooks for Xenial (LP: #1863024)

 -- Robert C Jennings <email address hidden> Tue, 15 Dec 2020 11:11:14 -0600

With the release of livecd-rootfs 2.408.65 in Xenial, cloud_images will take the package and produce builds. I will update the ticket when our next Xenial daily build goes out built with this version

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

verified xenial-server-cloudimg-amd64.ova with build:
http://cloud-images.ubuntu.com/xenial/20210127/

This issue was fixed in:
xenial-server-cloudimg-amd64.ova daily build 2021-01-27.
bionic-server-cloudimg-amd64.ova daily build 2021-01-12
focal-server-cloudimg-amd64.ova daily build 2021-01-12
groovy-server-cloudimg-amd64.ova daily build 2020-11-25.