test: [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (delayed binding)] topology [Top Level] [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (delayed binding)] topology should provision a volume and schedule a pod with AllowedTopologies is failing frequently in CI, see search results: https://search.svc.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-storage%5C%5D+In-tree+Volumes+%5C%5BDriver%3A+azure%5C%5D+%5C%5BTestpattern%3A+Dynamic+PV+%5C%28delayed+binding%5C%29%5C%5D+topology+%5C%5BTop+Level%5C%5D+%5C%5Bsig-storage%5C%5D+In-tree+Volumes+%5C%5BDriver%3A+azure%5C%5D+%5C%5BTestpattern%3A+Dynamic+PV+%5C%28delayed+binding%5C%29%5C%5D+topology+should+provision+a+volume+and+schedule+a+pod+with+AllowedTopologies https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-ovn-4.4/1277641618135977984
*** Bug 1852955 has been marked as a duplicate of this bug. ***
Isn't this same as https://bugzilla.redhat.com/show_bug.cgi?id=1852924 ?
*** Bug 1855436 has been marked as a duplicate of this bug. ***
ALso [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (default fs)] subPath [Top Level] [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (default fs)] subPath should support file as subpath [LinuxOnly] [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (ext4)] volumes [Top Level] [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (ext4)] volumes should allow exec of files on the volume [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (default fs)] volumes [Top Level] [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (default fs)] volumes should store data
I checked the related cases passed recently, but all in region "centralus", I'd like to wait some days to check case passed in region "westus".
Hi Huffman, As e2e did not be triggered in "westus", I test it from our side but I did not reproduce this issue in our test env successfully on both 4.4.14 (without fix) and 4.4.16 Candidate nightly (with fix). In our test env, I set up 3 master + 2 worker in region "westus", pv were attached and mounted successfully. A. From the Aure portal, all nodes have "Availability zone": "NA", and the mounted volumes have "Availability zone":None. B. From the oc get info, all nodes have Labels: "topology.kubernetes.io/region=westus" and "topology.kubernetes.io/zone=0", and the mounted volumes only have "region=westus" for nodeSelector in nodeAffinity. Is it because our flexy installation added the label for "Availability zone", so I could not reproduce? Or something I missed?
I see in some azure dynamic case failed in the latest test, but from the log, it is a different failure on region centralus. https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-ovn-4.4/1292870227733778432
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 (OpenShift Container Platform 4.4.18 bug fix 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/RHBA-2020:3440