Rebase to Amazon Linux upstream version 5.10.217-205.860.amzn2.
Description of changes:
Added 6 new patches. All are around hibernate/reboot logic, and ensure that the kernel refuses to resume from hibernate if the hardware configuration appears to change. Apparently Windows does not enforce this, and therefore Linux has also not enforced this behavior, because on real laptops this "appears to change" happens in cases where it is perfectly safe to resume from hibernate. On a virtual machine, though, the specified behavior (clean reboot, do not resume) is more desirable, since many hypervisors use these mechanisms to force reboot rather then resume.
Testing done:
Validate basic functionality through sonobuoy quick test:
> kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-192-168-46-39.us-west-2.compute.internal Ready <none> 2m51s v1.23.17-eks-ea94ec3 192.168.46.39 35.93.33.93 Bottlerocket OS 1.21.0 (aws-k8s-1.23) 5.10.217 containerd://1.6.31+bottlerocket
> sonobuoy run --mode=quick --wait
[...]
21:52:08 e2e global complete passed Passed: 1, Failed: 0, Remaining: 0
21:52:08 systemd-logs ip-192-168-46-39.us-west-2.compute.internal complete passed
21:52:08 Sonobuoy plugins have completed. Preparing results for download.
21:52:28 Sonobuoy has completed. Use `sonobuoy retrieve` to get results.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.
Rebase to Amazon Linux upstream version 5.10.217-205.860.amzn2.
Description of changes:
Added 6 new patches. All are around hibernate/reboot logic, and ensure that the kernel refuses to resume from hibernate if the hardware configuration appears to change. Apparently Windows does not enforce this, and therefore Linux has also not enforced this behavior, because on real laptops this "appears to change" happens in cases where it is perfectly safe to resume from hibernate. On a virtual machine, though, the specified behavior (clean reboot, do not resume) is more desirable, since many hypervisors use these mechanisms to force reboot rather then resume.
Testing done:
Validate basic functionality through sonobuoy quick test:
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.