This bug is for replicationgroup.elasticache.aws.jet.crossplane.io/v1alpha2
Crossplane is able to create the replication group and then it goes into reconciliation error saying "Error creating Elasticache Replication group". It does create the resource in AWS and then the reconciliation fails leaving the object is erroneous state.
DEBUG provider-jet-aws Cannot create external resource {"controller": "managed/elasticache.aws.jet.crossplane.io/v1alpha2, kind=replicationgroup", "request": "/redis-test", "uid": "123456789", "version": "835937905", "external-name": "redis-test", "error": "cannot apply: apply failed: Error creating ElastiCache Replication Group (redis-test): ReplicationGroupAlreadyExists: Replication group with specified name already exists.\n\tstatus code: 400, request id: 123456789: : File name: main.tf.json", "errorVerbose": "apply failed: Error creating ElastiCache Replication Group (redis-test): ReplicationGroupAlreadyExists: Replication group with specified name already exists.\n\tstatus code: 400, request id: 123456789: : File name: main.tf.json\ncannot apply\ngithub.com/crossplane/terrajet/pkg/controller.(*external)
Because of the above error, the process does not fully complete and the READY/SYNC status is set to false.
NAME READY SYNCED EXTERNAL-NAME AGE
redis-test False False redis-test 12h
What happened?
This bug is for replicationgroup.elasticache.aws.jet.crossplane.io/v1alpha2
Crossplane is able to create the replication group and then it goes into reconciliation error saying "Error creating Elasticache Replication group". It does create the resource in AWS and then the reconciliation fails leaving the object is erroneous state.
Because of the above error, the process does not fully complete and the READY/SYNC status is set to false.
How can we reproduce it?
What environment did it happen in?
Crossplane version: v1.6.3 Terrajet version: v0.4.0-39 Cloud: AWS K8S: EKS