[Bug 1124384] Re: cloud-init parses yaml incorrectly

[Steve Langasek]

'mounted' events are handled synchronously in mountall, and the
'filesystem' isn't emitted until they're all done.  Prelim tests seem to
confirm that this is working correctly (and if it wasn't that would be a
very bad bug, that I think we would have caught before now).

In a test instance from smoser, I've confirmed that a file touched
directly by /etc/init/cloud-config.conf persists, whereas a file touched
from within /var/lib/cloud/instance/scripts/runcmd is not created.  As
I'm not really familiar with the cloud-init architecture I can't
effectively debug this further, but it's definitely not mountall causing
the issue.

** Package changed: mountall (Ubuntu) => cloud-init (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1124384

Title:
  cloud-init parses yaml incorrectly

Status in “cloud-init” package in Ubuntu:
  New

Bug description:
  Example from failure: https://jenkins.qa.ubuntu.com/job/raring-server-
  ec2/ARCH=amd64,REGION=eu-west-1,STORAGE=ebs,TEST=multi-part-ud,label
  =ubuntu-server-ec2-testing/17/console

  Cloud-init is parsing YAML incorrectly
  runcmd:
  ...  - [ sh, -c, "echo ============= $(date) ': hello world!' ============= " ]
  ...  - [ sh, -c, 'echo "$(date)" > /root/runcmd.date.txt' ]
  ...  - [ wget, "http://slashdot.org", -O, /tmp/index.html ]
  ...  - touch /tmp/done

  Fails, while changing "- touch /tmp/done" to " - [ touch /tmp/done ]"
  works.

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