Bug 1999578

Summary: AWS EFS CSI tests are constantly failing
Product: OpenShift Container Platform Reporter: Jan Safranek <jsafrane>
Component: StorageAssignee: Jan Safranek <jsafrane>
Storage sub component: Kubernetes External Components QA Contact: Chao Yang <chaoyang>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs
Version: 4.9   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:06:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2002561    

Description Jan Safranek 2021-08-31 11:29:03 UTC
https://prow.ci.openshift.org/job-history/gs/origin-ci-test/pr-logs/directory/pull-ci-openshift-aws-efs-csi-driver-operator-master-operator-e2e has not passed any single time.

This is the job run with the least errors: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_aws-efs-csi-driver-operator/17/pull-ci-openshift-aws-efs-csi-driver-operator-master-operator-e2e/1432640063862214656

At least "[Testpattern: Dynamic PV (block volmode)] volumeMode should fail in binding dynamic provisioned PV to PVC" looks like a genuine error that should be fixed.

Comment 1 Jan Safranek 2021-09-02 12:34:01 UTC
Upstream PR for "volumeMode should fail in binding dynamic provisioned PV to PVC": https://github.com/kubernetes-sigs/aws-efs-csi-driver/pull/548

Comment 2 Jan Safranek 2021-09-02 12:49:15 UTC
I checked the other flakes in https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_aws-efs-csi-driver-operator/17/pull-ci-openshift-aws-efs-csi-driver-operator-master-operator-e2e/1432640063862214656 and both of them failed because a PVC was not deleted. The PVC was not deleted because of PVC protection, a test pod that used them was still in the API server. I checked kubelet logs, I haven't found anything obviously wrong - the pod volumes were deleted. Not sure what kept the Pod in the API server. I can't reproduce the issue on my cluster.

Comment 3 Jan Safranek 2021-09-02 12:49:35 UTC
s/the pod volumes were deleted/the pod volumes were unmounted/

Comment 9 errata-xmlrpc 2022-03-10 16:06:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056