elasticache: Retry deletion of param grp on InvalidCacheParameterGroupState

[radeksimko]

This is to address the following test failure:

=== RUN   TestAccAWSElasticacheParameterGroup_importBasic
--- FAIL: TestAccAWSElasticacheParameterGroup_importBasic (6.98s)
    testing.go:492: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error applying: 1 error(s) occurred:
        
        * aws_elasticache_parameter_group.bar (destroy): 1 error(s) occurred:
        
        * aws_elasticache_parameter_group.bar: InvalidCacheParameterGroupState: Cache parameter group parameter-group-test-terraform-620255685172994862 can not be deleted in the current state.
            status code: 400, request id: 1bb9eeba-4cd3-11e7-8b4a-e9587f270628
        
        State: aws_elasticache_parameter_group.bar:
          ID = parameter-group-test-terraform-620255685172994862
          description = Managed by Terraform
          family = redis2.8
          name = parameter-group-test-terraform-620255685172994862
          parameter.# = 1
          parameter.283487565.name = appendonly
          parameter.283487565.value = yes

Test results

$ make testacc TESTARGS='-run=TestAccAWSElasticacheParameterGroup'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test $(go list ./... |grep -v 'vendor') -v -run=TestAccAWSElasticacheParameterGroup -timeout 120m
?   	github.com/terraform-providers/terraform-provider-aws	[no test files]
=== RUN   TestAccAWSElasticacheParameterGroup_importBasic
--- PASS: TestAccAWSElasticacheParameterGroup_importBasic (31.20s)
=== RUN   TestAccAWSElasticacheParameterGroup_basic
--- PASS: TestAccAWSElasticacheParameterGroup_basic (51.81s)
=== RUN   TestAccAWSElasticacheParameterGroupOnly
--- PASS: TestAccAWSElasticacheParameterGroupOnly (28.15s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	111.192s

[stack72]

LGTM!

[ghost]

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!