-
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
EC2 Driver Relies on undefined refresh! method of Aws::Credentials in at least some cases #576
Comments
Hi, The above issue is raised from the |
The PR - aws/aws-sdk-ruby#2686 for fixing the issue in the |
@ashiqueps This is great! :) Am I missing the release of |
Hey @timvisher, Sorry that I've closed this issue as soon as the aws-sdk-core gem was published. I'll reopen this issue and will close it once a new version of workstation is released. |
I more just assumed I'd missed something. I have no authority here. :) Thanks again for chasing down the bug! |
@timvisher commented on Thu Apr 29 2021
EC2 Driver Relies on undefined
refresh!
method ofAws::Credentials
in at least some casesSome credentials classes are non-refreshing and when those are in use
test-kitchen may trigger an inappropriate call.
Version
I tested this down to the latest
20
release as well.Environment
Doesn't seem to have anything to do with the contents of the kitchen run.
Scenario
Use EC2 test platforms and have a decent error message if the clock is skewed.
Steps to Reproduce
I'm happy to go to the trouble of providing a little
Vagrantfile/.kitchen.yml
reproduction repo if there's interest in fixing this. Didn't want to go that far until someone told me I should. :)Launch an Ubuntu 20.04 instance
Install chef-workstation like:
Setup a
.kitchen.yml
file with an EC2 platform. Something like:Login to the Ubuntu instance, skew the clock, and go for a
create
.Something like:
Unskew the clock and retry the
create
action:Expected Result
Anything but a call to an undefined method by the AWS SDK.
Actual Result
Additional context
I'm willing to bet dollars to pay that this is actually an upstream issue
in https://github.com/aws/aws-sdk-ruby but I'm not sure whether it would
make more sense to defend against it here while simultaneously opening a
bug report there.
The text was updated successfully, but these errors were encountered: