Our daily image builds include this fix as of yesterday. I've confirmed
that it resolves the issue there.
I'll close this bug once we've published "release" images containing the
fix, which should occur with the buster update scheduled for this
weekend.
noah
On 2020-07-29 08:01:19, Bastian Blank wrote:
> On Tue, Jul 28, 2020 at 03:40:14PM -0700, Noah Meyerhans wrote:
> > 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
On Wed, Jul 29, 2020 at 08:04:54AM +0200, Bastian Blank wrote:
> | # /run/systemd/generator/systemd-growfs@-.service
> | # Automatically generated by systemd-fstab-generator
> |
> | [Unit]
> | BindsTo=%i.mount
> | After=%i.mount
> | Before=shutdown.target local-fs.target
>
> So it is an artefact
On Tue, Jul 28, 2020 at 12:33:48PM -0400, Noah Meyerhans wrote:
> Jul 28 16:14:54 debian systemd-growfs[271]: Partition size 8455699968 is not
> a multiple of the blocksize 4096, ignoring 3584 bytes
That's normal, we may fix the initramfs grow stuff to make better
decisions.
> Jul 28 16:14:54
On Tue, Jul 28, 2020 at 03:40:14PM -0700, Noah Meyerhans wrote:
> 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.
Prior to that we did not have any grow
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
8 matches
Mail list logo
