"nobootwait" mount option doesn't work on Fedora

Bug #785542 reported by Garrett Holmstrom
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Scott Moser

Bug Description

Since the "nobootwait" mount option is not part of upstream util-linux, mountall chokes on fstab entries created by cloud-init when run on a distro that doesn't patch that option into the source. Is the idea to prevent boot failure due to disks that go missing between boots? If so, perhaps "nofail" would be better.

Related branches

Scott Moser (smoser)
Changed in cloud-init:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Scott Moser (smoser) wrote :

This is now fix-committed, since revision 403 of trunk.

If you do not want 'nobootwait', then you will need to supply config (in /etc/cloud.cfg, or in /etc/cloud.cfg.d/<file>) that specifies a 'mount_default_fields'. Something like:
 mount_default_fields: [ None, None, "auto", "defaults,nofail", "0", "2" ]

Changed in cloud-init:
assignee: nobody → Scott Moser (smoser)
status: Triaged → Fix Committed
Revision history for this message
Garrett Holmstrom (gholms) wrote :

For future reference, use ~ or null in place of None to make PyYAML interpret it as a literal None instead of the string "None":

mount_default_fields: [~, ~, 'auto', 'defaults,nofail', '0', '2']

Scott Moser (smoser)
Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.