Skip to content

[efs-controller] Mount target gets stuck in lifeCycleState: creating #2496

Closed
@cellux

Description

@cellux

Describe the bug

Hi.

Since AWS EFS controller release 1.0.13 we can successfully create EFS filesystems via ACK.

Now we hit a similar problem with EFS mount targets created over these EFS filesystems: although they sync successfully, their IP address is not updated in the resource spec.

EFS controller logs:

{"level":"info","ts":"2025-05-24T05:24:43.906Z","logger":"ackrt","msg":"desired resource state has changed","kind":"MountTarget","namespace":"cratus","name":"cratus-root-eu-west-1a","account":"REDACTED","role":"","region":"eu-west-1","is_adopted":false,"generation":1,"diff":[{"Path":{"Parts":["Spec","IPAddress"]},"A":null,"B":"10.36.85.154"}]}
{"level":"info","ts":"2025-05-24T05:24:43.906Z","logger":"ackrt","msg":"updated resource","kind":"MountTarget","namespace":"cratus","name":"cratus-root-eu-west-1a","account":"REDACTED","role":"","region":"eu-west-1","is_adopted":false,"generation":1}

MountTarget resource:

apiVersion: efs.services.k8s.aws/v1alpha1
kind: MountTarget
metadata:
  creationTimestamp: "2025-05-24T05:17:52Z"
  finalizers:
  - finalizers.efs.services.k8s.aws/MountTarget
  generation: 1
  labels:
    kustomize.toolkit.fluxcd.io/name: cratus-production-perception-infra-config
    kustomize.toolkit.fluxcd.io/namespace: aws-production
  name: cratus-root-eu-west-1a
  namespace: cratus
  resourceVersion: "79377900"
  uid: 0a170faa-65c6-49e2-a7ad-33fd7356b6b6
spec:
  fileSystemRef:
    from:
      name: cratus-root-multi-az
      namespace: cratus
  securityGroups:
  - sg-00bfe3fb5d78362a5
  subnetID: subnet-0bf4468f641086785
status:
  ackResourceMetadata:
    ownerAccountID: "REDACTED"
    region: eu-west-1
  availabilityZoneID: euw1-az3
  availabilityZoneName: eu-west-1a
  conditions:
  - lastTransitionTime: "2025-05-24T05:24:43Z"
    status: "True"
    type: ACK.ReferencesResolved
  - lastTransitionTime: "2025-05-24T05:24:43Z"
    message: Resource synced successfully
    reason: ""
    status: "True"
    type: ACK.ResourceSynced
  lifeCycleState: creating
  mountTargetID: fsmt-0505d8bf2b9b4d8c8
  networkInterfaceID: eni-043f91217844a06cc
  ownerID: "REDACTED"
  vpcID: vpc-0bf21415c6efebee6

The mount target resource apparently gets stuck in lifeCycleState: creating and the IP is never written into spec.ipAddress.

Steps to reproduce

  1. Create an EFS filesystem via ACK
  2. Create a mount target which refers to it

Expected outcome

The state of the successfully created mount target is properly reflected in Kubernetes.

Environment

  • Kubernetes version: v1.31.7-eks-bcf3d70
  • Using EKS (yes/no), if so version? v1.31.7-eks-bcf3d70
  • AWS service targeted (S3, RDS, etc.): EFS

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.service/efsIndicates issues or PRs that are related to efs-controller.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions