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' ?
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' ?