[Bug 1905990] Re: UC20 amd64 images are unnecessarily big
Launchpad Bug Tracker
1905990 at bugs.launchpad.net
Mon Dec 14 19:07:33 UTC 2020
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 at ubuntu.com> 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 Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1905990
Title:
UC20 amd64 images are unnecessarily big
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Focal:
Fix Released
Bug description:
[Impact]
To work-around a bug in ubuntu-image, we hard-coded a `--image-size 8G` in livecd-rootfs for UC20 image builds. The reason for that was that ubuntu-image, in its initial UC20 image build implementation, was skipping yet-to-be-created partitions while calculating the final image size. This was fixed in ubuntu-image 1.10, and now the workaround is no longer required.
Additionally, the HWE team asked if it would be possible for the amd64 images to be smaller than 8GB as they need them to fit on 4GB storage. Without the hard-coded image size the UC20 images are around 3.1GB in size - which would be perfect for their needs.
That being said, after some additional discussion, we decided to still
hard-code the size, but to a smaller value - same as we do for UC18
and UC16. This is to make sure there's enough writable disk space for
normal usage.
[Test case]
Build a -proposed based UC20 focal amd64 image via live-build.
Download the image, decompress it and run `parted <imagefile>`. Print
the partition table and make sure that the image is now big enough for
all the contents (so at least 3GB) but smaller than the previous hard-
coded size (8GB).
[What could go wrong]
Right now there's no real places where things could go wrong. If
anything, the size wouldn't be modified, but this is something we test
for in the test case. Image build failures in case of busted bash
syntax, but we'd see that instantly as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1905990/+subscriptions
More information about the foundations-bugs
mailing list