mounts option to cloud-config skips devices not starting with /

Bug #603329 reported by Clint Byrum
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Scott Moser
cloud-init (Ubuntu)
Fix Released

Bug Description

Binary package hint: cloud-init

When trying to add glusterfs mounts, this cloud config yaml section fails to produce any errors or fstab entries:

 - [ 'volfile-server-hostname:6996', /mnt/data, glusterfs, "defaults,nobootwait", "0", "2" ]

In chatting w/ Scott on IRC, he believe it is a problem with anything that starts with a non slash char:

Related branches

Changed in cloud-init (Ubuntu):
milestone: none → maverick-alpha-3
Scott Moser (smoser)
summary: - mounts option to cloud-config refuses to mount volumes not starting with
- /
+ mounts option to cloud-config skips devices not starting with /
Scott Moser (smoser)
Changed in cloud-init:
assignee: nobody → Scott Moser (smoser)
importance: Undecided → Medium
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.5.12-0ubuntu5

cloud-init (0.5.12-0ubuntu5) maverick; urgency=low

  * sync with upstream r226.
  * fix bug where nfs/network mounts could not be specified (LP: #603329)
  * manage hostname setting better (LP: #596993)
  * add legacy-grub-ec2 package.
 -- Scott Moser <email address hidden> Thu, 08 Jul 2010 22:24:59 -0400

Changed in cloud-init (Ubuntu):
status: New → Fix Released
Scott Moser (smoser)
Changed in cloud-init:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers