aws emr --ssh / --get / --put commands do not work for EMR Cluster in a Waiting state #1007
Assignees
Labels
bug
This issue is a bug.
Comments
|
see boto/botocore#378 for corresponding botocore Issue |
|
Thanks for the bug report, we'll get this updated. |
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
kyleknap
added a commit
that referenced
this issue
Nov 21, 2014
* release-1.6.3: (25 commits) Bumping version to 1.6.3 Update integration test Update changelog Add binary output issue to changelog Fix module docstring in scalarparse Update changelog [ci skip] Add customization to alter scalar parsing behavior Add 1012 to the CHANGELOG Update changelog with feature Update code with botocore changes Add read file in bytes using fileb:// Add #1007 to the changelog Update CloudTrail to use bucket location constraints Fix issue when error response is receieved for streaming output Add sigv4 issue to changelog Add #982 to the changelog Add get-bucket-location fix to changelog Add auth resign issue to changelog Update changelog Fix always return rc of 0 for ls ...
|
thanks for the fast resolution! |
thoward-godaddy
pushed a commit
to thoward-godaddy/aws-cli
that referenced
this issue
Feb 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to run aws emr commands do not seem to work if the Cluster is in a WAITING state. This is an issue for long running clusters that reach the WAIT state after all steps have been completed.
Ex.
aws emr ssh --cluster-id j-XXXX --key-pair-file ~/XYZ.pem --debugThe above command hangs while waiting for a ClusterRunning Waiter object on the following line:
File "/usr/local/aws/lib/python2.7/site-packages/awscli/customizations/emr/sshutils.py", line 48, in validate_and_find_master_dns
It appears this is related to a recent change made to botocore to update its waiters to conform to a new v2 spec, during which the valid Cluster State for a 'ClusterRunning' waiter was changed from both the RUNNING & WAITING states to only the RUNNING state. See commit: boto/botocore@23e042f#diff-561cbc8ca2199768839320b0a5e2f0f0L14
Adding another success acceptor for the WAITING state to the emr/2009-03-31.waiters.json fixes this, but I am not sure if this was an intentional change to botocore. I will open up an issue on that project's github project as well.
The text was updated successfully, but these errors were encountered: