./test --functional errors if EC2 credentials aren't in the global environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
When running ./test --functional (the errors also occur if you run ./test without options, but --functional makes it fail quicker), I see a whole mess of errors. This looks to be because my AWS credentials aren't in the global environment. For example:
Traceback (most recent call last):
File "/home/
super(
File "/home/
File "/home/
s3_
File "/usr/lib/
creds = AWSCredentials(
File "/usr/lib/
raise ValueError("Could not find %s" % ENV_ACCESS_KEY)
exceptions.
I've attached the full output from ./test --functional for reference.
Changed in juju: | |
status: | Confirmed → Triaged |
I believe that the functional tests actually do require the use of EC2, so it doesn't look like this is an actual issue.
As Clint points out, the message could be improved, though, and the traceback avoided.