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

[Scott Moser]

The issue here is really that /tmp is getting cleaned after the above runs.
Then, the test harness is going looking for the file, but its long gone.

I'm not sure if its specifically a bug or not to rely on runcmd running after /tmp cleaning has run.  but it does seem like /tmp is being cleaned dangerously late in the boot process, given that runcmd is happening via cloud-config.conf at
   start on (filesystem and started rsyslog)

At what point in boot is it safe to put files in /tmp (even temporary
files) and assume that they will not be deleted by 'mounted-tmp' ?

** Package changed: cloud-init (Ubuntu) => mountall (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 “mountall” 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/mountall/+bug/1124384/+subscriptions