Hmm. I was using the latest karmic euca2ools package (bzr200) w/ just
euca-run-instances fixed. If anything else related to user data
handling changed in between, this might be the cause. I'll be able to
look into that tomorrow.
--
User data is not base64 decoded before being presented to the
Public bug reported:
User data supplied using euca-run-instances --user-data-file is not decoded
before being presented to the instance.
Inside the instance, curl http://169.254.169.254/latest/user-data; should
fetch the decoded user data, whereas eucalyptus will return a base64 and url