+++ This bug was initially created as a clone of Bug #1989180 +++ We run e2e tests on a cluster with masters in 5 different zones, while workers only in 3 zones. Test "should schedule pods in the same zones as statically provisioned PVs" schedules a pod on a master, which then won't run. We have a "<drop>" PR to skip the test: https://github.com/openshift/kubernetes/pull/870. Replace this <drop> patch with a proper fix upstream. Idea: Use GetReadySchedulableNodes to get list of all schedulable and untainted nodes when considering zones where to provision a volume. --- Additional comment from Jan Safranek on 2021-08-02 16:04:25 UTC --- Upstream PR: https://github.com/kubernetes/kubernetes/pull/104077 --- Additional comment from Maru Newby on 2021-08-04 15:12:08 UTC --- --- Additional comment from Maru Newby on 2021-08-04 15:22:55 UTC --- Adding proposed test skip pending the fix.
In other words, re-enable the skipped test (revert https://github.com/openshift/kubernetes/pull/925) when Kubernets 1.23 lands in OpenShift.
I can see the test got enabled during Kubernetes rebase. See this CI job: https://testgrid.k8s.io/redhat-openshift-ocp-release-4.10-informing#periodic-ci-openshift-release-master-nightly-4.10-e2e-gcp
The following is enabled and running passed, update the status to VERIFIED. Multi-AZ Cluster Volumes should schedule pods in the same zones as statically provisioned PV.
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 (Moderate: OpenShift Container Platform 4.10.3 security 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/RHSA-2022:0056