Hmmm, I wonder if this is in the seeds, given we *finally* got around to using the platform seeds to build the impish image (the intention was to do this in hirsute, and they were ready but for some reason they were never activated on that release).
Ah ha! Here's the culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/tree/raspi-common Now I wonder why that was added ... https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/platform/commit/raspi- common?id=66ab1060453f5cdc8db8af901910282de20411bc Ohhh. I wonder if this is required to grow the partition on the desktop images. Those don't use cloud-init at all, instead there's a "x-systemd.growfs" tag in the fstab, but perhaps this package was required to operate that? I thought that was systemd-growfs though... Either way, it seems like something that could be added to the desktop seed specifically instead of the raspi-common seed. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: cloud-init (Ubuntu) Assignee: Dave Jones (waveform) => (unassigned) ** Changed in: cloud-init (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
