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

[4.12] EFS csi controller&driver pod are CrashLoopBackOff due to csi-driver container is not running on arm.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • 4.12
    • Storage / Operators
    • None
    • Storage Sprint 226
    • 1
    • Approved
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      Description of problem:

      EFS csi controller&driver pod are CrashLoopBackOff due to csi-driver container is not running.
      This issue only happen on arm.
      

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

      aws-efs-csi-driver-operator.4.12.0-202210210958 
      

      How reproducible:

      always
      

      Steps to Reproduce:

      1.Install 
      2.
      aws-efs-csi-driver-controller-76fc7c9c6-drvch    3/4     CrashLoopBackOff   44 (77s ago)   3h21m
      aws-efs-csi-driver-controller-779896c759-rpj4s   3/4     CrashLoopBackOff   44 (64s ago)   3h21m
      aws-efs-csi-driver-node-76dkv                    2/3     CrashLoopBackOff   44 (80s ago)   3h21m
      3.
      oc logs aws-efs-csi-driver-controller-76fc7c9c6-drvch
      Defaulted container "csi-driver" out of: csi-driver, csi-provisioner, provisioner-kube-rbac-proxy, csi-liveness-probe
      exec /usr/bin/aws-efs-csi-driver: exec format error
      4.oc logs aws-efs-csi-driver-controller-76fc7c9c6-drvch -c csi-liveness-probe
      I1025 04:35:50.211079       1 connection.go:154] Connecting to unix:///csi/csi.sock
      W1025 04:36:00.211878       1 connection.go:173] Still connecting to unix:///csi/csi.sock
      W1025 04:36:10.211983       1 connection.go:173] Still connecting to unix:///csi/csi.sock
      W1025 04:36:20.211360       1 connection.go:173] Still connecting to unix:///csi/csi.sock
      5.
      2022-10-25T04:01:34.740380700+00:00 stderr F I1025 04:01:34.740076       1 metadata.go:85] retrieving instance data from ec2 metadata
      2022-10-25T04:01:34.742456021+00:00 stderr F I1025 04:01:34.742430       1 metadata.go:92] ec2 metadata is available
      2022-10-25T04:01:34.743333733+00:00 stderr F I1025 04:01:34.743315       1 metadata_ec2.go:25] regionFromSession 
      2022-10-25T04:01:34.745863434+00:00 stderr F I1025 04:01:34.745840       1 node.go:98] regionFromSession Node service 
      2022-10-25T04:01:34.745863434+00:00 stderr F I1025 04:01:34.745853       1 metadata.go:85] retrieving instance data from ec2 metadata
      2022-10-25T04:01:34.747779709+00:00 stderr F I1025 04:01:34.747760       1 metadata.go:92] ec2 metadata is available
      2022-10-25T04:01:34.748592772+00:00 stderr F I1025 04:01:34.748574       1 metadata_ec2.go:25] regionFromSession 
      2022-10-25T04:01:34.756140564+00:00 stderr F I1025 04:01:34.756117       1 mount_linux.go:217] Cannot run systemd-run, assuming non-systemd OS
      

      Actual results:

      
      

      Expected results:

      
      

      Additional info:

      
      

            rhn-engineering-jsafrane Jan Safranek
            rhn-support-chaoyang Chao Yang
            Rohit Patil Rohit Patil
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: