Comment 10 for bug 1691489

Balint,

Thanks for the reply.

With regard to slowing down boot, I'm not too concerned about that. Because in almost all properly functioning scenarios, cloud-init's generator will enable or disable cloud-init. So the slow down would be limited to scenarios where cloud-init was supposed to run, primarily on non-first boots of an instance. I agree though, it does put a bottleneck in boot.

With reard to 'swapoff -a' or 'swapon -a' or the systemd-fsck.service equivalent, I'm not opposed to that, but I don't know how it could be made to be non-racey. Do you have a solution in mind that doesn't have a race in it?

Ie, for swap:
  - cloud-init check if there is swap in use.
  - cloud-init run 'swapoff -a'
  - cloud-init do some things
  - cloud-init run 'swapon -a'

while systemd in parallel
  - enable swap for .mount entries that were generated from stale fstab

This can be mitigated some by being more granular (swapoff /dev/XXX), but still racy unless cloud-init can coordinate that with systemd. Is that possible?

Thanks again for the input.
Scott