-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shared AWS credentials file being ignored. #295
Comments
We've identified a bad merge that is causing this and are trying to resolve this - I'd recommend pinning to 1.2.0 for the time being but I'm hoping to have this resolved by EOD tomorrow (I'm unfortunately on an airplane a good deal of the day) |
@tom-schultz do you happen to have any ENV vars related to AWS set as well? Specifically - "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" (not the values obviously just whether they are set or not) |
Nope, no AWS vars. Thanks for the tip!
…On Mon, Feb 13, 2017 at 5:48 PM, Seth Thomas ***@***.***> wrote:
@tom-schultz <https://github.com/tom-schultz> do you happen to have any
ENV vars related to AWS set as well?
Specifically - "AWS_ACCESS_KEY_ID" and "AWS_SECRET_ACCESS_KEY" (not the
values obviously just whether they are set or not)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#295 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACA7oNe2IbKdXsFhRx9efRri5KyoH92Pks5rcQf3gaJpZM4L_8VP>
.
|
Additional information: I was just standing up a new cookbook and testing our our kitchen.yml to make sure it stood up an instance successfully when we hit the issue. Reposting what I have found when I ran into this issue. I'm not fully sure I understand the issue getting fixed here, but I upgraded to kitchen-ec2 1.3.0 in order to take advantage of PR #291 to get Windows 2016 AMI's working. Now when I'm trying to interact with the 2016 instance or my previously working 2012r2 instance, I get the following kitchen error:
This is mostly new ground for me in interacting with AWS EC2 instances, but I do know that what I had was working with 1.2.0 kitchen-ec2 and now it's not. I'm running ChefDK 1.1.16 and Kitchen 1.14.2 and kitchen-ec2 1.3.0. |
Reverting to 1.2.0 fixed this for me.
|
@cheeseplus I believe this has to do with this line: https://github.com/test-kitchen/kitchen-ec2/blob/master/lib/kitchen/driver/aws/client.rb#L72 The way I changed it in #259, it only sources the shared credentials file if a profile name is provided. Originally, |
This allows a user to rely on a [default] profile getting picked up in the shared credentials file (~/.aws/credentials). Fixes test-kitchen#295 Fixes test-kitchen#258
Hi,
When I try to run kitchen test I get the following error. I have AWS credentials and they can be used by knife and the AWS CLI. Any idea why kitchen seems to be ignoring them? I've also attached kitchen.log.
The text was updated successfully, but these errors were encountered: