Skip to content

Extended.[k8s.io] StatefulSet [k8s.io] Basic StatefulSet functionality [StatefulSetBasic] should not deadlock when a pod's predecessor fails #15416

@bparees

Description

@bparees
[k8s.io] StatefulSet
/go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:656
  [k8s.io] Basic StatefulSet functionality [StatefulSetBasic]
  /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:656
    should not deadlock when a pod's predecessor fails [It]
    /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/statefulset.go:249

    Jul 22 15:24:24.738: Failed waiting for pods to enter running: timed out waiting for the condition

    /go/src/github.com/openshift/origin/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/statefulset_utils.go:303

from https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/1349/

possibly a dupe of
#15408
and
#15401

Note that this was seen on a merge to the 3.6 branch (ie pre-rebase)

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions