Actually, the problem seems to have been caused by
https://salsa.debian.org/cloud-team/debian-cloud-images/-/merge_requests/192/
Prior to that MR, we weren't using systemd-growfs at all.
I've confirmed impact on amd64 instances as well as the arm64 instances
on which originally observed it. It
Having done a bit of testing, this definitely seems to be a regression.
I've launched 63 instances of the 10.3 AMI in us-east-1
(ami-031d1abcdcbbfbd8f) and 63 of the current 10.4 AMI
(ami-0bb15d03913335eae) on a variety of 6g arm64 instance types. Exacly
zero of the 10.3 launches ended up in
Package: cloud.debian.org
Severity: important
User: cloud.debian@packages.debian.org
Usertags: aws image
Testing the current buster releases for [mcr]6gd.* instance type support
reveals an issue that leads the instances to boot to "degraded" state in
systemd. The failing unit is