Similar behavior with c4.large instances.
In the 2025.07.14 cycle, we have cpuhotplug:cpuhotplug0{2..6} consistently
failing when running with plucky:aws version 6.14.0-1011.11 in the us-west-1
region.
I'd expect the same to be happening with noble:aws-6.14 in this cycle, as these
kernels are essentially very similar, but the tests are passing there. However,
for n:aws-6.14, they are running in the us-east-2 region.
In the 2025.06.16 cycle, cpuhotplug:cpuhotplug0{2..6} on c4.large running
plucky:aws version 6.14.0-1009.9 passed, but they ran in the us-east-2 region
too.
I'm thinking if this could have something to do with the region these
instances are launched in. Additionally, x1e.xlarge and c4.large are
both Xen-based, so could this be some intermittent hypervisor issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044334
Title:
Unable to put CPU back online on AWS x1e.xlarge instance with kernel
6.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2044334/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
