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 Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: cloud-init parses yaml incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
