Skip to content
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

Wait for instances to move out of pending state before adding name tags. #140

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Wait for instances to move out of pending state before adding name tags. #140

wants to merge 2 commits into from

Conversation

jwm
Copy link
Contributor

@jwm jwm commented Dec 14, 2014

Avoids intermittent startup errors when instances not yet ready.

ERROR:gc3.elasticluster:could not start node compute002 for reason `EC2ResponseError: 400 Bad Request

InvalidInstanceID.NotFoundThe instance ID 'i-0df866e1' does not exist58c878c1-2c59-484c-835c-44b9176fae77`

Avoids intermittent startup errors when instances not yet ready.

ERROR:gc3.elasticluster:could not start node `compute002` for reason `EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidInstanceID.NotFound</Code><Message>The instance ID 'i-0df866e1' does not exist</Message></Error></Errors><RequestID>58c878c1-2c59-484c-835c-44b9176fae77</RequestID></Response>`
…move out of pending state. Supplement to /jwm/elasticluster#4 gc3-uzh-ch/elasticluster#140
"""
try:
status = vm.update()
except EC2ResponseError:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you run into this issue? I haven't seen this one before.

@riccardomurri riccardomurri self-assigned this Dec 7, 2015
@riccardomurri riccardomurri added this to the 1.4 milestone Dec 7, 2015
@riccardomurri
Copy link
Contributor

It would be relatively easy to merge this code into #536 but I tend to share @nicolasbaer view: I have never seen the error that this code claims to work around. Maybe the EC2 API server code has become more responsive over the years, thus eliminating the source of this error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants