I did an image bisect on Canonical's GCE jammy images and found that the behavior started between 20240207 and 20240207a, which have a manifest diff of:
$ diff 20240207-manifest.txt 20240207a-manifest.txt 356,362c356,362 < linux-gcp 6.2.0.1019.21~22.04.1 < linux-gcp-6.2-headers-6.2.0-1019 6.2.0-1019.21~22.04.1 < linux-headers-6.2.0-1019-gcp 6.2.0-1019.21~22.04.1 < linux-headers-gcp 6.2.0.1019.21~22.04.1 < linux-image-6.2.0-1019-gcp 6.2.0-1019.21~22.04.1 < linux-image-gcp 6.2.0.1019.21~22.04.1 < linux-modules-6.2.0-1019-gcp 6.2.0-1019.21~22.04.1 --- > linux-gcp 6.5.0.1013.13~22.04.1 > linux-gcp-6.5-headers-6.5.0-1013 6.5.0-1013.13~22.04.1 > linux-headers-6.5.0-1013-gcp 6.5.0-1013.13~22.04.1 > linux-headers-gcp 6.5.0.1013.13~22.04.1 > linux-image-6.5.0-1013-gcp 6.5.0-1013.13~22.04.1 > linux-image-gcp 6.5.0.1013.13~22.04.1 > linux-modules-6.5.0-1013-gcp 6.5.0-1013.13~22.04.1 575c575 < snap:lxd 5.0/stable/ubuntu-22.04 26741 --- > snap:lxd 5.0/stable/ubuntu-22.04 26881 I have not done a full bisect of focal and noble images but the current focal image (with kernel 5.15.0-1062-gcp, image serial 20240614) and the current noble image (with kernel 6.8.0-1010-gcp, image serial 20240717) are both affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073620 Title: http timeout from lxd container using n4-highcpu-2 gce instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2073620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
