cfn-userdata is located /var/lib/cloud/data/scripts/ vs the expected location of /var/lib/cloud/data. This breaks the provision logging as well as the provision completion file touching.
shardy
---------
I noticed this too, wonder if we can just drop some directory symlinks in as part of building the jeos (ie after cloud-init is installed, which owns /var/lib/cloud, but annoyingly not the subdirectories, so I guess it creates those at runtime)
If the above approach is viable then I guess this should be a heat-jeos issue
zane
--------
Note that in the case of the provision-finished file, it's the missing /var/lib/cloud/instance path that's the problem.
jpeeler
--------
I'm wondering if we shouldn't put logic in the scripts to handle cloud-init path handling. Thoughts on that? I'm unsure if the locations changed due to different version or distro, but I'm assuming at least the locations are fairly static now. (There's also the issue of assuming execution of runcmd will be successful which I have a fix for, so I think there's a precedent to making sure script execution is successful lies with the script itself - unless somebody knows of a cloud-config option I haven't found.)
Fix proposed to branch: master
Review: https:/