It seems like the right thing to do is write 'nobootwait' or 'nofail' based on distro.uses_systemd()
** Description changed: Snapshotted instances may fail to boot due to a change in udev in 15.10. Starting with Ubuntu 15.10, "nobootwait" != "nofail". + + For reference, Ubuntu's systemd had a patch that accepted nobootwait + [1], but that was dropped in 15.10. discussed some in ubuntu-devel at + [2] + + -- + [1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu&id=8fbf6c7e671c663190eae8a63b158e686c3d41fa + [2] http://irclogs.ubuntu.com/2015/11/09/%23ubuntu-devel.html#t13:34 ** Changed in: cloud-init (Ubuntu Wily) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1514485 Title: cloud-init should use "nofail" instead of "bootwait" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
