Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-34392

4.15 AWS EFS CSI driver is not compatible with the 4.16 OCP

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.16.0
    • 4.15.0
    • Storage / Operators
    • None
    • Important
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      Description of problem:

      Trying to install AWS EFS Driver 4.15 in 4.16 OCP. And driver pods get stuck with the below error:
      $ oc get pods
      NAME                                             READY   STATUS    RESTARTS   AGE
      aws-ebs-csi-driver-controller-5f85b66c6-5gw8n    11/11   Running   0          80m
      aws-ebs-csi-driver-controller-5f85b66c6-r5lzm    11/11   Running   0          80m
      aws-ebs-csi-driver-node-4mcjp                    3/3     Running   0          76m
      aws-ebs-csi-driver-node-82hmk                    3/3     Running   0          76m
      aws-ebs-csi-driver-node-p7g8j                    3/3     Running   0          80m
      aws-ebs-csi-driver-node-q9bnd                    3/3     Running   0          75m
      aws-ebs-csi-driver-node-vddmg                    3/3     Running   0          80m
      aws-ebs-csi-driver-node-x8cwl                    3/3     Running   0          80m
      aws-ebs-csi-driver-operator-5c77fbb9fd-dc94m     1/1     Running   0          80m
      aws-efs-csi-driver-controller-6c4c6f8c8c-725f4   4/4     Running   0          11m
      aws-efs-csi-driver-controller-6c4c6f8c8c-nvtl7   4/4     Running   0          12m
      aws-efs-csi-driver-node-2frs7                    0/3     Pending   0          6m29s
      aws-efs-csi-driver-node-5cpb8                    0/3     Pending   0          6m26s
      aws-efs-csi-driver-node-bchg5                    0/3     Pending   0          6m28s
      aws-efs-csi-driver-node-brndb                    0/3     Pending   0          6m27s
      aws-efs-csi-driver-node-qcc4m                    0/3     Pending   0          6m27s
      aws-efs-csi-driver-node-wpk5d                    0/3     Pending   0          6m27s
      aws-efs-csi-driver-operator-6b54c78484-gvxrt     1/1     Running   0          13m
      
      Events:
        Type     Reason            Age                    From               Message
        ----     ------            ----                   ----               -------
        Warning  FailedScheduling  6m58s                  default-scheduler  0/6 nodes are available: 1 node(s) didn't have free ports for the requested pod ports. preemption: 0/6 nodes are available: 1 node(s) didn't have free ports for the requested pod ports, 5 node(s) didn't match Pod's node affinity/selector.
        Warning  FailedScheduling  3m42s (x2 over 4m24s)  default-scheduler  0/6 nodes are available: 1 node(s) didn't have free ports for the requested pod ports. preemption: 0/6 nodes are available: 1 node(s) didn't have free ports for the requested pod ports, 5 node(s) didn't match Pod's node affinity/selector.

       

       

      Version-Release number of selected component (if applicable):

          4.15

      How reproducible:

          all the time

      Steps to Reproduce:

          1. Install AWS EFS CSI driver 4.15 in 4.16 OCP
          2.
          3.
          

      Actual results:

          EFS CSI drive node pods are stuck in pending state

      Expected results:

          All pod should be running.

      Additional info:

          More info on the initial debug here: https://redhat-internal.slack.com/archives/CBQHQFU0N/p1715757611210639

            rh-ee-mpatlaso Maxim Patlasov
            mashetty@redhat.com Mahesh Shetty
            Rohit Patil Rohit Patil
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: