[Bug 1514485] Re: [SRU] cloud-init should use "nofail" instead of "bootwait"

[Ben Howard]

** Description changed:

  SRU JUSTIFICATION
  
  [IMPACT] Prior to Ubuntu 15.10, the mount option of "nobootwait" ==
  "nofail." However, with Ubuntu 15.10, this is no longer the case. As a
  result, snapshotted, stopped and restarted, or migrated Cloud instances
  may fail to boot if the ephemeral device does not match /etc/fstab.
  
  [FIX] Changed the default mount option to "nofail"
  
  [TEST]
  1. Boot Ubuntu 15.10 on Azure
  2. Upgrade cloud-init to proposed version
- 3. Confirm that "nobootwait" for the ephemeral device has been changed to "nofail"
+ 3. Run "sed -i 's/nobootwait/nofail/g' /etc/fstab"
  4. Shutdown instance
  5. Restart instance, confirm it comes up
  6. Capture restarted instance
  7. Boot captured image
  8. Confirm that capture instance came back up
  
  [ORIGINAL REPORT]
  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

-- 
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:
  [SRU] 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