[WHIRR-74] AWS Keys Not being Propagated to Instances via Userdata

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: contrib/python

Environment

Ubuntu 10.04 and Mac OSX
with ami-ed59bf84 for instances

• Assignee: Unassigned
• Reporter: Sameer Al-Sakran
• Created: 17/Aug/10 01:20
• Updated: 07/Aug/11 20:38
• Resolved: 07/Aug/11 20:38

Description

The %ENV% string in contrib/python/src/py/hadoop/cloud/data/hadoop-ec2-init-remote.sh is mean to export various environment variables.

These variables exist in the invoking client shell process, but dont exist on the launched instance. In this specific case, the aws keys for S3/S3n access were being set to empty strings. Manually adding AWS ID/SECRET to the pairs dictionary passed to build_env_string in py.hadoop.cloud.service:209 fixes this problem, but introduces aws specific information to the Service class.

Should the ENV string do an assignment + export instead of just an export here?