[iotg] desktop image does not expand the root partition

@Brian
Could you take a look at this issue?
The image seems not to have packages required for partition auto-expanding.

@Brian

The cloud images which preload cloud-init package support this feature.

cloud-initramfs-tools: growroot/scripts/local-bottom/growroot
cloud-init: /usr/lib/python3/dist-packages/cloudinit/config/cc_resizefs.py

ubuntu-20.04-preinstalled-desktop-amd64+intel-iot.img.xz doesn't preload cloud-init packages.
Not sure if we should preload cloud-init packages.
If we don't preload it on Intel iot image, is there any other way to enable this feature?

Oh, so actually this will be fixed if my MP for the grub.cfg upgrade issues lands: https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/410949

So yes, this is possible - we already do this for the desktop-preinstalled images for Pi.

For the record fixing this will likely require the installation of the package cloud-initramfs-growroot in addition to the livecd-rootfs changes. We'll make sure it gets added to the image.

HW used: Aaeon EHL board
CID: 202109-29496
Image used: https://cdimage.ubuntu.com/focal/daily-preinstalled/20211102.1/ (with -proposed enabled)

Following the same steps as when the issue was reported, I'm glad to tell the issue is gone and the root filesystem is now auto-expanding!

$ lsblk -e 7
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 58.2G 0 disk
├─mmcblk0p1 179:1 0 1M 0 part
├─mmcblk0p2 179:2 0 50M 0 part
└─mmcblk0p3 179:3 0 58.2G 0 part /
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk

Image: https://cdimage.ubuntu.com/focal/daily-preinstalled/20211102.1/
HW: Aaeon TGL board

Installed the image, verified with Disks utility that the data partition was properly expanded.

Rebooted the device, leaving my data drive plugged in, and the desktop booted as expected.

HW used: Aaeon EHL board
CID: 202109-29496
Image used: http://cdimage.ubuntu.com/focal/daily-preinstalled/20211108.1/ (with -proposed DISABLED)

Following the same steps as when the issue was reported, confirmed the issue is gone and the root filesystem is now auto-expanding:

$ lsblk -e 7
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 14.5G 0 disk
└─sda1 8:1 1 14.5G 0 part
mmcblk0 179:0 0 58.2G 0 disk
├─mmcblk0p1 179:1 0 1M 0 part
├─mmcblk0p2 179:2 0 50M 0 part
└─mmcblk0p3 179:3 0 58.2G 0 part /
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk

→ OK

HW used: Aaeon EHL board
CID: 202109-29496
Image used: http://cdimage.ubuntu.com/focal/daily-live/20211202.2/focal-desktop-amd64+intel-iot.iso (with -proposed DISABLED)

Installing the new ISO image onto the device, user is given the option of installing it on the whole disk, or to configure the partitioning as needed. Therefore, this original issue does not happen anymore on ISO files.

→ OK