Yep, that's what I've found; cloud-init is just waiting for its later stages to run, which are blocked by snapd.seeded.service exiting.
Yep, that's what I've found; cloud-init is just waiting for its later stages to run, which are blocked by snapd.seeded. service exiting.