Description of problem: [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)] volumes should allow exec of files on the volume [Suite:openshift/conformance/parallel] [Suite:k8s] expand_less 5m26s fail [k8s.io/kubernetes/test/e2e/framework/util.go:1674]: Unexpected error: <*errors.errorString | 0xc0041b77b0>: { s: "expected pod \"exec-volume-test-aws-dynamicpv-lfb5\" success: Gave up after waiting 5m0s for pod \"exec-volume-test-aws-dynamicpv-lfb5\" to be \"success or failure\"", } expected pod "exec-volume-test-aws-dynamicpv-lfb5" success: Gave up after waiting 5m0s for pod "exec-volume-test-aws-dynamicpv-lfb5" to be "success or failure" occurred [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (block volmode)(allowExpansion)] volume-expand Verify if offline PVC expansion works [Suite:openshift/conformance/parallel] [Suite:k8s] expand_less 5m24s fail [k8s.io/kubernetes/test/e2e/storage/testsuites/volume_expand.go:165]: While creating pods for resizing Unexpected error: <*errors.errorString | 0xc003164be0>: { s: "pod \"security-context-721a2ff7-d718-463a-a4a9-6fa42c9e599e\" is not Running: timed out waiting for the condition", } pod "security-context-721a2ff7-d718-463a-a4a9-6fa42c9e599e" is not Running: timed out waiting for the condition occurred https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-mirrors-4.3/137
The test went through very unusual path because it failed to provision a PV for a PVC due to RequestLimitExceeded for some time. When provisioning finally succeeded, kubelet wanted to resize the volume (!) and failed (!!!): FailedMount: MountVolume.MountDevice failed while expanding volume for volume "pvc-d36aa909-2f21-40d1-9d49-4416ce7665c2" : MountVolume.NodeExpandVolume get PVC failed : persistentvolumeclaims "awstr77d" is forbidden: User "system:node:ip-10-0-134-135.ec2.internal" cannot get resource "persistentvolumeclaims" in API group "" in the namespace "e2e-volume-5888": no relationship found between node "ip-10-0-134-135.ec2.internal" and this object The test should not involve any resizing, it just tests running a script on the volume.
Failed due to RequestLimitExceeded that's fixed in bug #1690588. *** This bug has been marked as a duplicate of bug 1690588 ***