Bug 1859900 - [sig-scheduling] Multi-AZ Cluster Volumes [sig-storage] should schedule pods in the same zones as statically provisioned PVs
Summary: [sig-scheduling] Multi-AZ Cluster Volumes [sig-storage] should schedule pods ...
Keywords:
Status: CLOSED DUPLICATE of bug 1806594
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.0
Assignee: Mike Dame
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-23 10:02 UTC by Nikolaos Leandros Moraitis
Modified: 2020-07-23 17:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
[sig-scheduling] Multi-AZ Cluster Volumes [sig-storage] should schedule pods in the same zones as statically provisioned PVs
Last Closed: 2020-07-23 17:38:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nikolaos Leandros Moraitis 2020-07-23 10:02:17 UTC
test:
[sig-scheduling] Multi-AZ Cluster Volumes [sig-storage] should schedule pods in the same zones as statically provisioned PVs 

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-scheduling%5C%5D+Multi-AZ+Cluster+Volumes+%5C%5Bsig-storage%5C%5D+should+schedule+pods+in+the+same+zones+as+statically+provisioned+PVs


FIXME: Replace this paragraph with a particular job URI from the search results to ground discussion.  A given test may fail for several reasons, and this bug should be scoped to one of those reasons.  Ideally you'd pick a job showing the most-common reason, but since that's hard to determine, you may also chose to pick a job at random.  Release-gating jobs (release-openshift-...) should be preferred over presubmits (pull-ci-...) because they are closer to the released product and less likely to have in-flight code changes that complicate analysis.

FIXME: Provide a snippet of the test failure or error from the job log

Comment 1 Maciej Szulik 2020-07-23 11:37:33 UTC
Mike this looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1806594 and https://bugzilla.redhat.com/show_bug.cgi?id=1856341 feel free to close as dupes.

Comment 2 Mike Dame 2020-07-23 17:38:34 UTC

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


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