The xenial verification has failed as once again the package names are not correct. I have an MP up [1] which reverts back to the original behavior. Xenial's behavior around shim is not the same as later releases. This work is not something scheduled till next year.
Bionic [2] and Focal [3] are sru verification passed as images are building, no longer including extra packages, and are launching successfully. The build logs linked you can search for "chroot mountpoint apt-get install -qqy grub-pc shim-signed" to verify the new version is getting shipped.
The xenial verification has failed as once again the package names are not correct. I have an MP up [1] which reverts back to the original behavior. Xenial's behavior around shim is not the same as later releases. This work is not something scheduled till next year.
Bionic [2] and Focal [3] are sru verification passed as images are building, no longer including extra packages, and are launching successfully. The build logs linked you can search for "chroot mountpoint apt-get install -qqy grub-pc shim-signed" to verify the new version is getting shipped.
[1] https:/ /code.launchpad .net/~powersj/ livecd- rootfs/ +git/livecd- rootfs- 1/+merge/ 394910 /i510533839. restricted. launchpadlibrar ian.net/ 510533839/ buildlog_ ubuntu_ bionic_ amd64_amd64- disk-image_ qcow2_squashfs_ tarball_ vagrant_ vmdk_azure_ azure-pro_ azure-pro- fips_dimension- data_hyperv- gcs_wsl_ maas_softlayer_ cpc_BUILDING. txt.gz? token=HPgBwmkbz tJpx1ZSZbwW0Ln2 XvmF0Clh /i510437212. restricted. launchpadlibrar ian.net/ 510437212/ buildlog_ ubuntu_ focal_amd64_ amd64-disk- image_kvm_ qcow2_squashfs_ tarball_ vagrant_ vmdk_azure_ azure-pro_ hyperv- gcs_wsl_ maas_softlayer_ cpc_BUILDING. txt.gz? token=pxHwRfRH0 CVNcL6Rj6fhcltm q1SQDtDH
[2] https:/
[3] https:/