So in addition to a kernel fix, we will first need to release a cloud-init that will handle the endian-ness of instance IDs changing underneath it.
This is because the kernel is already out in the wild, so we will have some instances that have booted with the new UUID and the kernel fix will also trigger the behaviour seen in this bug.
So in addition to a kernel fix, we will first need to release a cloud-init that will handle the endian-ness of instance IDs changing underneath it.
This is because the kernel is already out in the wild, so we will have some instances that have booted with the new UUID and the kernel fix will also trigger the behaviour seen in this bug.