Merge ~ffledgling/cloud-init:doc-fix into cloud-init:master
Status: | Merged |
---|---|
Merged at revision: | 39fb5a0240597112af8162c6c3365288450a7a77 |
Proposed branch: | ~ffledgling/cloud-init:doc-fix |
Merge into: | cloud-init:master |
Diff against target: |
76 lines (+9/-9) 3 files modified
doc/examples/cloud-config-gluster.txt (+2/-2) doc/examples/cloud-config-mount-points.txt (+4/-4) doc/examples/cloud-config.txt (+3/-3) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
cloud-init Commiters | Pending | ||
Review via email: mp+312917@code.launchpad.net |
Description of the change
Change `nobootwait` to `nofail` in docs
`nobootwait` is an ubuntu specific extension to the mount syntax that is
not supported by other non-derivative linux operating systems.
`nobootwait` support appears to have been dropped Ubuntu 16.04 onwards,
based on http://
Last Ubuntu version with mention of `nobootwait` appears to be 15.10,
based on http://
All examples using `nobootwait` were updated to use the standard
`nofail`, which gives the expected behaviour of not failing to boot in
case a volume is missing. There are likely subtle differences in semantics
between `nobootwait` and `nofail`, but it is the best (only?) substitute
that gives behaviour similar to the defunct `nobootwait` option.
In addition to tests, there are tests (namely: tests/data/ merge_sources/ source8- 1.yaml, tests/data/ merge_sources/ expected8. yaml) and some code (config?) files (namely: cloudinit/ config/ cc_mounts. py) that use nobootwait as well, but I haven't modified them because I'm not entirely clear about the scope of those changes. If those need to be changed as well, please let me know.