-
Notifications
You must be signed in to change notification settings - Fork 200
[Bug]: AccessKey resource keeps trying to create more access keys #2009
Copy link
Copy link
Open
Labels
Description
Is there an existing issue for this?
- I have searched the existing issues
Affected Resource(s)
- iam.aws.m.upbound.io/v1beta1 - AccessKey
Resource MRs required to reproduce the bug
apiVersion: iam.aws.m.upbound.io/v1beta1
kind: AccessKey
metadata:
annotations:
crossplane.io/composition-resource-name: overlay-ci-uploader-access-key
crossplane.io/external-name: tbell-overlay-default-dev-7709a6-ci-uploader-access-key
labels:
crossplane.io/composite: default-dev-infra
name: tbell-overlay-default-dev-7709a6-ci-uploader
namespace: liferay-default-dev
spec:
forProvider:
userSelector:
matchLabels:
aws.liferay.com/username: tbell-overlay-default-dev-7709a6-ci-uploader
managementPolicies:
- '*'
Steps to Reproduce
- Create an AccessKey for a User.
Expected Result
- Only one AccessKey will be created
What happened?
Crossplane loses track of the AccessKey over time, and then creates a 2nd one, and then tries to create a third one.
Relevant Error Output Snippet
create failed: async create failed: failed to create the resource: [{0 creating IAM Access Key (gma-bs5-123456789012345-overlay-able-dev-690bc7-ci-uploader-user): operation error IAM: CreateAccessKey, https response error StatusCode: 409, RequestID: 7277fce5-aa1c-4023-974c-3de7fab11734, LimitExceeded: Cannot exceed quota for AccessKeysPerUser: 2 []}]Crossplane Version
2.1.3
Provider Version
2.3.0
Kubernetes Version
Server Version: v1.35.2-eks-f69f56f
Kubernetes Distribution
EKS
Additional Info
Could be root cause of #2008.
Reactions are currently unavailable