Authentication fails for juju 1.25.6 on aws
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Attempting to bootstrap a juju model on aws, using juju 1.25.6 on a trusty vm results in an authentication failure:
```
d@ubuntu:~$ juju switch amazon
amazon -> amazon
d@ubuntu:~$ juju bootstrap --debug
2017-02-13 18:46:30 INFO juju.cmd supercommand.go:37 running juju [1.25.6-
2017-02-13 18:46:30 INFO juju.provider.ec2 provider.go:49 opening environment "amazon"
2017-02-13 18:46:31 DEBUG juju.provider.ec2 provider.go:129 ec2 request failed: AWS was not able to validate the provided access credentials (AuthFailure)
2017-02-13 18:46:31 DEBUG juju.cmd.juju common.go:99 Destroying environment info.
2017-02-13 18:46:31 INFO juju.cmd cmd.go:129 Bootstrap failed, cleaning up the environment.
2017-02-13 18:46:31 ERROR juju.cmd supercommand.go:429 there was an issue examining the environment: authentication failed.
Please ensure the Access Key ID you have specified is correct.
You can obtain the Access Key ID via the "Security Credentials"
page in the AWS console.
```
Creating an ec2 instance directly through the web dashboard works. Bootstrapping a model (using the same credentials) with juju 2.0.0 on xenial works just fine as well.
@Domas,
1.25 series is upto to 1.25.10. Could you please re-test with latest version?
If you are running Ubuntu, you can get it from the juju proposed ppa:
sudo add-apt-repository ppa:juju/1.25
sudo apt-get update; sudo apt-get install juju-core