-
Notifications
You must be signed in to change notification settings - Fork 14
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
Refreshing temporary credentials failed during advisory refresh period. #15
Comments
Connection timeout too low perhaps? |
Do you see this behavior only with 2.10, meaning you can switch back and forth between 2.6 and 2.10 and reproduce it only with 2.10? If the problem does not follow the version, is it intermittent, which would be characteristic of a network and service issue? |
Haven't dug too far into it Eric - it may not be related to the version bump, we only started noticing it recently. I can see it from over two weeks ago (logDna retention time) - it may have been present before that, and even before 2.6.3 - but cannot be sure |
(Updated OP to remove specifics about versioning) |
WARNING:ibm_botocore.credentials:Refreshing temporary credentials failed during advisory refresh period. During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Having local issues creating a PR - may I suggest something like the below as a solution to enable us to override the default of 5 seconds. credentials.py
|
We are looking at your proposed solution now for possible inclusion. In most cases like this, we recommend users extend |
Thanks Eric - I was hoping to avoid extending the class as some future breaking changes would expose me to being forced to address them, when all I want/ed is to provide a timeout value |
We have implemented an override in 2.11.0, though the changelog mistakenly has omitted listing this. Can you verify and close this ticket? |
Thank you Eric - I try to get it in and tested next sprint |
Closing this ticket as resolved. |
I'm not an experienced Python developer, so go easy on me ;-) Noticing lots of credential refreshing errors in our logs
The text was updated successfully, but these errors were encountered: