Speaking as someone who's not very familiar with the Debian kernel
development processes I am in favor of reverting the commit until we know
for sure that the AWS Xen fleet upgrade is complete and pushing a new
release, especially if it's possible to only apply the revert to the -cloud
kernels.
Cu
Please forgive the spam from trying to figure out how to use the
bugtracking system.
I'd also like to add that reverting the aforementioned commit on the
5.10.103 kernel IS sufficient to fix the issue. We're testing AMIs with
that fix in our QA cluster now.
affects cloud.debian.org
On Fri, Mar 11, 2022 at 7:24 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1007144:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007144.
>
> This is
Package: linux-image-cloud-amd64
Severity: important
Dear Maintainer,
We recently noticed that instances using linux-image-5.10.0-11-amd64 and
newer and using Xen-based EC2 instances (such as m4.large, c4.large etc)
wouldn't join our Kubernetes clusters. We eventually figured out that
this was a
4 matches
Mail list logo
