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.

Sign up for GitHub

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

Jump to bottom

Waiter does not exist: ClusterRunning #937

Closed
tilusnet opened this issue Oct 8, 2014 · 4 comments · Fixed by boto/botocore#346
Closed

Waiter does not exist: ClusterRunning #937

tilusnet opened this issue Oct 8, 2014 · 4 comments · Fixed by boto/botocore#346
Labels
bug This issue is a bug.

Comments

@tilusnet
Copy link

tilusnet commented Oct 8, 2014

Version 1.3.25 had a very nice feature that made aws-cli process calls to a booting cluster wait until the cluster was ready. This was manifesting itself with a "Waiting for the cluster to start." message and the process waiting.

Now, in version 1.5.0 such a scenario makes the aws-cli process call to exit with an error:
"Waiter does not exist: ClusterRunning."
This is inconvenient as it makes calling code to poll until the cluster is ready.

Can you please fix this / revert it the way it worked?

Thank you.
@jamesls
Copy link
Member

jamesls commented Oct 8, 2014

Looking into this. Can you confirm what command you were running that is now failing?

@jamesls jamesls added the investigating This issue is being investigated and/or work is in progress to resolve the issue. label Oct 8, 2014
@tilusnet
Copy link
Author

tilusnet commented Oct 8, 2014

Yes, it was an emr ssh command:

aws emr --region eu-west-1 ssh --cluster-id j-1A9VQCZSVXUJ --key-pair-file /home/attila/.ssh/id_rsa.pem --command "echo 'Cluster ready.'"

@jamesls
Copy link
Member

jamesls commented Oct 8, 2014

Thanks, I've confirmed the issue. Working on a fix.

@jamesls jamesls added bug This issue is a bug. confirmed and removed investigating This issue is being investigated and/or work is in progress to resolve the issue. labels Oct 8, 2014
@tilusnet
Copy link
Author

tilusnet commented Oct 8, 2014

Thank you for being so prompt.

@jamesls jamesls mentioned this issue Oct 8, 2014
Merged
jamesls added a commit that referenced this issue Oct 8, 2014
@jamesls
Add issue #937 to the changelog
40a6a11
@tilusnet tilusnet mentioned this issue Oct 15, 2014
Closed
kyleknap added a commit that referenced this issue Oct 17, 2014
@kyleknap
Merge branch 'release-1.5.2'
10d2de1 
* release-1.5.2:
  Bumping version to 1.5.2
  Updated Changelog with new features.
  EMR: Updated test for describe-cluster
  EMR: Fix describe-cluster
  EMR: Add validation logic in steputils and clean up create-cluster and add-steps examples.
  Update tests based on feedback
  Renamed sync strategy class names.
  Remove unused imports and vars in handlers
  Update handlers with new event kwargs
  Fix cloudsearch define-index-field for type latlon
  Add issue #937 to the changelog
  Updated the changelog with bugfix.
  Delete large files for cross region ``mv``
  Cleaned up the custom sync strategy code
  Made seperate directory for  sync strategies
  Add more customizations to sync strategies
  Added custom sync strategy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue is a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add waiter config and fix config lookup jamesls/botocore
2 participants
@jamesls @tilusnet