kubernetes: SchedulerPredicates - failures in 1.6 to 1.7 upgrade tests

triage query

Within the above link can be found failures for

  • SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching
  • SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2
  • SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching
  • SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching
  • SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching
  • SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching
  • SchedulerPredicates [Serial] validates that embedding the JSON PodAffinity and PodAntiAffinity setting as a string in the annotation value work
  • SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching with multiple Affinities

Sampled failures:

SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching

go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:461
Not scheduled Pods: []api.Pod(nil)
Expected
    <int>: 0
to equal
    <int>: 1
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:930

SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:640
Expected
    <string>: gke-bootstrap-e2e-default-pool-efb8e5cb-rvjc
to equal
    <string>: gke-bootstrap-e2e-default-pool-efb8e5cb-nt2j
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:639

Other failures look similar.

/sig scheduling /assign @davidopp

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 22 (21 by maintainers)

Most upvoted comments

/close I’m taking an educated guess that this issue won’t get worked on as we’re now in the 1.10 release cycle. Please /reopen if you disagree or notice these tests failing in a later version of the upgrade tests