Skip to content

Extended.[k8s.io] Probing container should *not* be restarted with a /healthz http liveness probe [Conformance] #12072

@bparees

Description

@bparees
• Failure [138.845 seconds]
[k8s.io] Probing container
/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:793
  should *not* be restarted with a /healthz http liveness probe [Conformance] [It]
  /data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/container_probe.go:233

  Nov 29 23:16:31.438: pod e2e-tests-container-probe-dk0xc/liveness-http - expected number of restarts: 0, found restarts: 1

  /data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/container_probe.go:373

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/8991/

Metadata

Metadata

Labels

component/kuberneteskind/test-flakeCategorizes issue or PR as related to test flakes.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.priority/P1

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions