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

bug version 1.40 #6157

Closed
Elihai opened this issue Oct 15, 2018 · 9 comments · Fixed by #6391
Closed

bug version 1.40 #6157

Elihai opened this issue Oct 15, 2018 · 9 comments · Fixed by #6391
Labels
bug Addresses a defect in current functionality. service/rds Issues and PRs that pertain to the rds service.
Milestone

Comments

@Elihai
Copy link

Elihai commented Oct 15, 2018

issuse:
aws_rds_cluster.default: Failed to modify RDS Cluster (demo): InvalidParameterCombination: The specified new engine version is same as current version: 9.6.9
status code: 400, request id: 04f08c7a-3aee-4754-96f1-b1e33bcacbe6

it happened when I trying to restore the last snapshot and the snapshot already configured to with rds engine version 9.6.9 it also happens when I trying to upgrade to 10.4.

so, for now, I back to version 1.39

@bflad bflad added the service/rds Issues and PRs that pertain to the rds service. label Oct 15, 2018
@asaghri
Copy link

asaghri commented Oct 25, 2018

Same problem here ! Had to switch back to 1.39 to make it work.

@namachieli
Copy link

namachieli commented Oct 31, 2018

Ran into this myself tonight.

TF v0.11.10
AWS v1.41
Aurora RDS PostrgreSQL v10.4

Error

* aws_rds_cluster.postgresql: 1 error(s) occurred:

* aws_rds_cluster.postgresql: Failed to modify RDS Cluster (test-postgresql-cluster): InvalidParameterCombination: The specified new engine version is same as current version: 10.4
	status code: 400, request id: 565a<...>8b9fe5

Edit
Confirmed, forcing AWS provider to v1.39 got this working.

@DI-DaveGoodine
Copy link

changing my provider to:

provider "aws" {
  region = "us-east-1"
  version = "~> 1.39.0"
}

fixed this, as it did for others. I was also trying to create an rds aurora postgresql 10.4 cluster from snapshot with latest aws provider and latest tf.

@bflad bflad added the bug Addresses a defect in current functionality. label Nov 7, 2018
@bflad
Copy link
Contributor

bflad commented Nov 7, 2018

I was able to reproduce this with some new acceptance testing -- working on a fix now. 👍

--- FAIL: TestAccAWSRDSCluster_SnapshotIdentifier_EngineVersion_Different (307.45s)
    testing.go:538: Step 0 error: Error applying: 1 error occurred:
        	* aws_rds_cluster.test: 1 error occurred:
        	* aws_rds_cluster.test: Failed to modify RDS Cluster (tf-acc-test-5310186777500539203): InvalidParameterCombination: The specified new engine version is same as current version: 9.6.6
        	status code: 400, request id: cd9bb70c-0af8-4783-95b9-ef9fa72251d0




--- FAIL: TestAccAWSRDSCluster_SnapshotIdentifier_EngineVersion_Equal (307.49s)
    testing.go:538: Step 0 error: Error applying: 1 error occurred:
        	* aws_rds_cluster.test: 1 error occurred:
        	* aws_rds_cluster.test: Failed to modify RDS Cluster (tf-acc-test-4108683443326527325): InvalidParameterCombination: The specified new engine version is same as current version: 9.6.3
        	status code: 400, request id: ee7ee554-035b-43e7-9a66-9fd57254a04e

@bflad
Copy link
Contributor

bflad commented Nov 7, 2018

Pull request submitted with acceptance testing to cover this going forward: #6391

@bflad bflad added this to the v1.43.1 milestone Nov 8, 2018
@bflad
Copy link
Contributor

bflad commented Nov 8, 2018

Sorry for the trouble, folks! The fix for this has been merged and will release with version 1.43.1 of the AWS provider, likely later today. 👍

@DI-DaveGoodine
Copy link

Thank you sir!

@bflad
Copy link
Contributor

bflad commented Nov 9, 2018

This has been released in version 1.43.1 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

@ghost
Copy link

ghost commented Apr 2, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/rds Issues and PRs that pertain to the rds service.
Projects
None yet
5 participants