Bug 1830324 - [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (immediate binding)] topology [Top Level]
Summary: [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (immed...
Keywords:
Status: CLOSED DUPLICATE of bug 1828174
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: aos-storage-staff@redhat.com
QA Contact: Qin Ping
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-01 15:51 UTC by Cyril
Modified: 2020-05-07 03:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
[sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (immediate binding)] topology [Top Level] [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (immediate binding)] topology should provision a volume and schedule a pod with AllowedTopologies [Suite:openshift/conformance/parallel] [Suite:k8s]
Last Closed: 2020-05-07 03:50:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Cyril 2020-05-01 15:51:02 UTC
test:
[sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (immediate binding)] topology [Top Level] [sig-storage] In-tree Volumes [Driver: azure] [Testpattern: Dynamic PV (immediate binding)] topology should provision a volume and schedule a pod with AllowedTopologies [Suite:openshift/conformance/parallel] [Suite:k8s] 

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%28immediate+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%28immediate+binding%5C%29%5C%5D+topology+should+provision+a+volume+and+schedule+a+pod+with+AllowedTopologies+%5C%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5C%5D+%5C%5BSuite%3Ak8s%5C%5D

Comment 2 Evan Cordell 2020-05-04 22:34:55 UTC
This appears to fail on gcp sometimes as well: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.4/1556

Comment 3 W. Trevor King 2020-05-07 03:50:34 UTC
> This appears to fail on gcp sometimes as well: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.4/1556

In that case, the underlying issue (popping open the accordion on the job-detail page) is:

  fail [k8s.io/kubernetes/test/e2e/framework/framework.go:423]: May  4 20:59:27.865: All nodes should be ready after test, Get https://api.ci-op-rrgwl5q5-972cc.origin-ci-int-gce.dev.openshift.com:6443/api/v1/nodes: unexpected EOF

which is almost certainly not what is going on with the Azure failures.

Popping open the first Azure hit from the original CI-search URI gets me [1].  Popping open its accordion and opening stdout shows:

  May  6 23:40:12.257: INFO: At 2020-05-06 23:35:11 +0000 UTC - event for pvc-84l5g: {persistentvolume-controller } ProvisioningFailed: Failed to provision volume with StorageClass "e2e-topology-1661-azure-scdfxcg": compute.DisksClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="LocationNotSupportAvailabilityZones" Message="The resource 'Microsoft.Compute/disks/ci-op-j6dr7gvf-5ab2f-hljhr-dynamic-pvc-2e2793ed-38ff-403c-b150-664e86ef7b07' does not support availability zones at location 'westus'."

which is bug 1828174.  Also in this space is bug 1832627.  Closing this a dup of the former, in the absence of someone providing an example with a different failure mode (not just the same failing test name).

[1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-azure-compact-4.4/104

*** This bug has been marked as a duplicate of bug 1828174 ***


Note You need to log in before you can comment on or make changes to this bug.