yahoo-eng-team team mailing list archive

[James Falcon <1861903@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3603

** Bug watch added: github.com/canonical/cloud-init/issues #3603
   https://github.com/canonical/cloud-init/issues/3603

** Changed in: cloud-init
       Status: Triaged => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1861903

Title:
  Mountpoint containing a space not working

Status in cloud-init:
  Expired

Bug description:
  If I want to mount a directory containing a space (for example to
  match a remote share name), it will not work currently with the
  default cc_mounts plugin.

   - if I surround the mountpoint with quotes, it will create the destination directory properly, but then /etc/fstab won't contain the quotes and the spaces will cause parsing error in /etc/fstab
   - If I use the common workaround of replacing spaces with \040, then the directory will contain a literal '\' and then '040', and the mountpoint won't be found because mount interprets the escape sequence properly.

  My suggestion: when outputting to /etc/fstab, escape spaces (and any
  other character part of fstab grammar) properly. This way the cloud-
  init config will just work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1861903/+subscriptions