-
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
Error trying to tag instance before it exists #138
Comments
@tyler-ball Weirdly, this still seems to be happening periodically on the chef kitchen-tests. For example, https://travis-ci.org/chef/chef/jobs/73639153 . I checked, and the version we're pulling from I'm a little confused why we're not getting to see the stacktrace from the job though! Can't be sure it's exactly the same stacktrace, just that it's the same error. |
Found the stack!
|
Yep, it's the same issue, just an the fix wasn't quite enough. It looks to me like it's stopping right away instead of looping like it's supposed to.. |
According to AWS, the default delay for But I'm seeing it stop instantaneously! |
Further investigation: the error being raised is A barely related point: it would be more efficient to rescue the error when tagging and do the loop there, because most of the time the tag succeeds out of the gate. |
OK, yeah, |
I see why we were doing instance_running ... so that it would wait for the instance to be running. We need to loop until instance is running as well as until it exists. Blargh. Side note: this is one reason I hate unit tests. They give you false confidence. (The tests tested that we called the AWS functions we wanted to call, but not whether we'd accomplished what we wanted.) |
The text was updated successfully, but these errors were encountered: