-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
KeyError: 'RequestID' getting ec2 instances #339
Comments
Interesting. Is it possible we could get a debug log of this? It would be nice to see if the |
Unfortunately it happened in an alert and it's not easily reproducible since it likely requires AWS to fail. We have also modified the alert since we didn't need to use the AWS API. |
Alright we will need to investigate it then. Are you just using a |
It was using the |
Thanks. Out of curiosity do you have a lot of instances to iterate over in the collection? I wonder if that is why the |
I think there are about 3 instances to iterate over, so we don't have a lot of instances to iterate over. |
Thanks! We will look into this then. |
I have also stumbled upon this recently and got a bit of extra info (I caught it through sentry):
(sorry about the parsing for the following...)
|
Thanks! This should be enough for us to implement a fix. |
Fixes boto/boto3#339. I also had to fix an unrelated test because the response body is always read as bytes(), and two of the functional tests were using str().
When retrieving ec2 instances, we will occasionally get the following error from boto3:
It appears some error happened on Amazon's side and there's no RequestID in the returned request. I have no reproducer since this happens intermittently. It might be worth having a default value of
None
if the RequestID doesn't exist in the response though.The text was updated successfully, but these errors were encountered: