-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
False
-
None
-
False
-
-
There are many Driver: azure-disk related failures.
Starting investigation...
A lot of tests end like this:
: [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern: Generic Ephemeral-volume (default fs) (late-binding)] ephemeral should create read/write inline ephemeral volume [Suite:openshift/conformance/parallel] [Suite:k8s] expand_less 15m1s { fail [k8s.io/kubernetes@v1.29.0/test/e2e/storage/testsuites/ephemeral.go:203]: Interrupted by User Ginkgo exit error 1: exit with code 1} sysout: May 23 09:49:07.672: INFO: Wait up to 15m0s for pod "inline-volume-dbcxk" to be fully deleted May 23 09:49:09.825: INFO: Creating resource for dynamic PV May 23 09:49:09.825: INFO: Using claimSize:1Gi, test suite supported size:{ }, driver(azure-disk) supported size:{ } STEP: creating a StorageClass e2e-ephemeral-97804cqrf @ 05/23/24 09:49:09.825 STEP: checking the requested inline volume exists in the pod running on node {Name: Selector:map[] Affinity:nil} @ 05/23/24 09:49:09.901 [INTERRUPTED] in [It] - k8s.io/kubernetes@v1.29.0/test/e2e/storage/testsuites/ephemeral.go:203 @ 05/23/24 10:04:04.743
Look for tests in sippy that match ": [sig-storage] In-tree Volumes [Driver: azure-disk] [Testpattern:" on azure, upgrade-minor and pick one of them; you will see the red