Comment 5 for bug 2038945

Would be really good to understand when this started happening, since this cycle we for instance switched to use ubuntu-image 3.0 for building the image - so I'm of course thinking if maybe the way we prepare the cloud-init configuration could be wrong or something. Or is it cloud-init itself changing behavior?