Hide Forgot
Description of problem: https://bugs.launchpad.net/heat/+bug/1454401 Version-Release number of selected component (if applicable): 7.0 How reproducible: 100% Steps to Reproduce: user_data: type: string default: "file:///root/heat-templates/samples/user_data.sh" resources: instance: #depends_on: [network_port_resource] type: OS::Nova::Server properties: name: { get_param: instance_name } key_name: { get_param: ssh_key_name } image: { get_param: image_name } flavor: { get_param: image_flavor } networks: - port: { get_param: network_port_resource } availability_zone: { get_param: az } user_data_format: RAW user_data: #get_file: "file:///root/heat-templates/samples/user_data.sh" ### Works get_file: { get_param: user_data } ### Does not work (its precised because of the note in http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-file) Actual results: Fails to Create Instance, "No content found in the "files" section for get_file path when" Error Expected results: Suscessfull Stack creation with a customizable cloud-init file. Additional info:
It works fine AFAIK. What doesn't work is that the client doesn't automatically upload the file in question the way it does if a filename appears directly within the {get_file: <filename>} intrinsic in the template. It pretty much can't know without completely executing heat-engine's environment and parameter resolution code in the client, and even then there are circumstances that it may not be able to for lack of data (e.g. PATCH update, where some of the parameter values are not known to the client). It'd be nice to have a way of forcing extra file inclusions on the CLI for those who do want to use this pattern. The server side will certainly accept any files you want to upload there.
Sorry, ignore previous comment, this RFE refers to the *global* environment, not the environment passed by the user. So the note in http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-file has nothing to do with it. This seems inherently insecure to me.
There is an upstream change, but it needs work and is currently looking likely to miss mitaka-rc2
Current status: upstream reviews are still ongoing.
Didn't make upstream feature freeze for Ocata, so bumping to OSP 12.
Obsolete RFE without enough of backed demand.