-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.13
-
Critical
-
No
-
Approved
-
False
-
-
N/A
-
Release Note Not Required
-
Done
This is a clone of issue OCPBUGS-10475. The following is the description of the original issue:
—
Description of problem:
AWS EFS driver controller, node pods are not coming up and reaching CrashLoopBackOff status
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-arm64-2023-03-14-173645
How reproducible:
Always
Steps to Reproduce:
1. Try to install cluster from flexy templates with below mentioned details.
Template: aos-4_13/upi-on-aws/versioned-installer-disconnected-arm-efs-ci
installer_payload_image: registry.ci.openshift.org/ocp-arm64/release-
arm64:4.13.0-0.nightly-arm64-2023-03-14-173645
rhel8-installer-4_13
2. Check the EFS Driver/Node pod status.
Actual results:
EFS Driver/Node pods reaching to CrashLoopBackOff/Error status.
Expected results:
EFS related pods should be up and Running in openshift-cluster-csi-drivers ns
Additional info:
rohitpatil@ropatil-mac Downloads % oc logs aws-efs-csi-driver-controller-7d77db9875-6t25w -c csi-driver -n openshift-cluster-csi-drivers exec /usr/bin/aws-efs-csi-driver: exec format error
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
