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

Version 1.10.29 breaks EC2 searches with tags (by specifying MaxResults) #1976

Closed
hashbrowncipher opened this issue May 18, 2016 · 9 comments
Labels
bug This issue is a bug.

Comments

@hashbrowncipher
Copy link

hashbrowncipher commented May 18, 2016

The following works in version 1.10.28:

aws ec2 describe-instances --region=us-west-1 --filters "Name=tag:aws:autoscaling:groupName,Values=consul"

It does not work in 1.10.29. Instead, this result is returned:

A client error (InvalidParameterCombination) occurred when calling the DescribeInstances operation: The parameter 'maxResults' cannot be used with tag filters in the parameter 'filterSet'. Remove either the tag filters from 'filterSet' or the 'maxResults' parameter and try again.
@leo100
Copy link

leo100 commented May 18, 2016

Broken with: aws-cli/1.10.29 Python/2.6.9 Linux/4.4.8-20.46.amzn1.x86_64 botocore/1.4.20

aws ec2 describe-volumes --volume-ids vol-bce02671

A client error (InvalidParameterCombination) occurred when calling the DescribeVolumes operation: The parameter volumeSet cannot be used with the parameter maxResults

Or trying to mount Ebs volume produces:

A client error (InvalidParameterCombination) occurred when calling the DescribeVolumes operation: The parameter volumeSet cannot be used with the parameter maxResults
Volume ID: vol-bce02671 State:
Volume vol-bce02671 is in and not available , exiting

But works with:
aws-cli/1.10.28 Python/2.6.9 Linux/4.4.8-20.46.amzn1.x86_64 botocore/1.4.19

@hieurl
Copy link

hieurl commented May 18, 2016

Same problem here
Suddenly many of my cron jobs failed today after upgrading awscli to 1.10.29 with same error

aws ec2 describe-instances --filters "Name=tag:Name,Values=SMSMkt-Workers"

A client error (InvalidParameterCombination) occurred when calling the DescribeInstances operation: The parameter 'maxResults' cannot be used with tag filters in the parameter 'filterSet'. Remove either the tag filters from 'filterSet' or the 'maxResults' parameter and try again.

@watsonrp
Copy link

watsonrp commented May 18, 2016

Me too

PS C:\> aws --version
aws-cli/1.10.29 Python/3.4.4 Windows/10 botocore/1.4.20

aws ec2 describe-instances --instance-ids i-AAAAAAAA

Produces...


A client error (InvalidParameterCombination) occurred when calling the DescribeInstances operation:
The parameter instancesSet cannot be used with the parameter maxResults

@sue445
Copy link

sue445 commented May 18, 2016

me too 😢

$ aws --version
aws-cli/1.10.29 Python/2.7.5 Linux/3.10.0-327.10.1.el7.x86_64 botocore/1.4.20

$ aws ec2 describe-instances --instance-ids "xxxxxxxxxx" --region "ap-northeast-1"

A client error (InvalidParameterCombination) occurred when calling the DescribeInstances operation: The parameter instancesSet cannot be used with the parameter maxResults

$ echo $?
255

@onuki-yoshihisa
Copy link

me too.

# aws ec2 describe-instances --region ${REGION} --instance-ids ${INSTANCE_ID} 

A client error (UnauthorizedOperation) occurred when calling the DescribeInstances operation: You are not authorized to perform this operation.

@jamesls
Copy link
Member

jamesls commented May 18, 2016

Change that's causing this issue has been reverted: #1977

@jamesls jamesls added the bug This issue is a bug. label May 18, 2016
@tsyardley
Copy link

tsyardley commented May 18, 2016

can confirm this has broken using filters in describe-instances

aws ec2 describe-instances --region eu-west-1 --filter 'Name=tag-key,Values=Name','Name=tag-value,Values=MYINSTANCE*' --output text

A client error (InvalidParameterCombination) occurred when calling the DescribeInstances operation: The parameter 'maxResults' cannot be used with tag filters in the parameter 'filterSet'. Remove either the tag filters from 'filterSet' or the 'maxResults' parameter and try again.

@jamesls
Copy link
Member

jamesls commented May 18, 2016

We've just released v1.10.30 of the CLI which reverts the change that caused this issue. Please upgrade to 1.10.30.

Going to go ahead and close out this issue. Let us know if anyone's still seeing issues on v1.10.30.

@jamesls jamesls closed this as completed May 18, 2016
@nswanson7
Copy link

I'm seeing this error using the get_only_instances() function with boto.

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

No branches or pull requests

9 participants