[Bug] Error: could not create fargate profiles: failed to create Fargate profile "fp-default" on EKS cluster

[prasobhen]

Fargate profile is already its trying to create again after EKS cluster upgrade from 1.21 to 1.22

EKSCTL_VERSION=0.107.0

creating Fargate profile "fp-default" on EKS cluster "xxx-xxx-xx-eks" 2022-08-29T06:58:39.6404332Z Error: could not create fargate profiles: failed to create Fargate profile "fp-default" on EKS cluster "xxx-xxx-xx-eks": failed to create Fargate profile "fp-default": operation error EKS: CreateFargateProfile, https response error StatusCode: 409, RequestID: 69f8ee49-a113-46bd-9abc-97c5a9fcb0a9, api error ResourceInUseException: A Fargate Profile already exists with this name in this cluster.

[github-actions[bot]]

Hello prasobhen :wave: Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-3 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

[prasobhen]

Some one please check this error

[cPu1]

@prasobhen, can you share your ClusterConfig file? This does look like a bug. We'll investigate the issue and get back to you soon.

[prasobhen]

As requested , please find the cluster config file

apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig metadata: name: xxx-xxx-xx-eks # EKS Cluster Name region: eu-central-1 version: "1.22" tags: project: xxx environment: xxx map-migrated: d-server-xxxxxxxx vpc: id: "vpc-xxxxxx" # VPC ID created with Terraform. ID got from Terraform output

publicAccessCIDRs: ["1.1.1.1/32", "2.2.2.0/24"] #If Azure DevOps CIDR range is known

subnets: private: eu-central-1a: id: "subnet-xxxxx" # Subnet created and properly tagged with Terraform. ID got from Terraform output eu-central-1b: id: "subnet-xxxxx" # Subnet created and properly tagged with Terraform. ID got from Terraform output eu-central-1c: id: "subnet-xxxxx" # Subnet created and properly tagged with Terraform. ID got from Terraform output identityProviders:

• name: eks-oidc-config type: oidc issuerUrl: "https://cognito-idp.eu-central-1.amazonaws.com/eu-central-1_xxxxx" clientId: "xxxxxxxx" usernameClaim: email groupsClaim: "cognito:groups" groupsPrefix: "gid:" fargateProfiles: # creating Fargate profiles for each workload
• name: fp-default selectors:

  All workloads in the "default" Kubernetes namespace will be scheduled onto Fargate:

  • namespace: default

  All workloads in the "kube-system" Kubernetes namespace will be scheduled onto Fargate:

  • namespace: kube-system

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.

[jeraldsm]

Hi @Himangini

We tried upgrading eksctl version from 0.96.0 to the latest one which is 0.128.0, and the issue is still happening..

2022-XX-XX ... Error: could not create fargate profiles: ..., https response error StatusCode: 409, RequestID: ..., api error ResourceInUseException: A Fargate Profile already exists with this name in this cluster.