ClusterRunning waiter no longer successful when EMR cluster in a WAITING state #378
Labels
bug
This issue is a confirmed bug.
Comments
jamesls
added a commit
to jamesls/botocore
that referenced
this issue
Nov 19, 2014
Found by someboredkiddo Introduced in 23e042f Closes boto#378 Fixes aws/aws-cli#1007
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like when the changes were made to update waiters.py to a new v2 spec, valid Cluster State for a 'ClusterRunning' waiter was changed from accepting both the RUNNING & WAITING states to only the RUNNING state.
See commit: 23e042f#diff-561cbc8ca2199768839320b0a5e2f0f0L14
This has resulted in this waiter not returning successfully when an EMR cluster goes into a WAITING state, breaking functionality in aws emr tool (see aws/aws-cli#1007).
Not sure if removing WAITING was intentional? If not, I'd be happy to submit a pull request adding a WAITING success acceptor to ClusterRunning in emr/2009-03-31.waiters.json.
The text was updated successfully, but these errors were encountered: