openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.48k stars 4.7k forks source link

oc status is complaining about missing readiness checks in build pods #17213

Open 0xmichalis opened 6 years ago

0xmichalis commented 6 years ago

Not sure it should.

  * pod/deck-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/deck-23-build --liveness ...
  * pod/hook-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/hook-23-build --liveness ...
  * pod/horologium-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/horologium-23-build --liveness ...
  * pod/jenkins-config-updater-6-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-config-updater-6-build --liveness ...
  * pod/jenkins-config-updater-7-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-config-updater-7-build --liveness ...
  * pod/jenkins-config-updater-binaries-5-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-config-updater-binaries-5-build --liveness ...
  * pod/jenkins-operator-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-operator-23-build --liveness ...
  * pod/jenkins-proxy-17-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-proxy-17-build --liveness ...
  * pod/plank-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/plank-23-build --liveness ...
  * pod/prow-26-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prow-26-build --liveness ...
  * pod/prow-27-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prow-27-build --liveness ...
  * pod/prow-28-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prow-28-build --liveness ...
  * pod/sinker-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/sinker-23-build --liveness ...
  * pod/splice-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/splice-23-build --liveness ...
  * pod/tide-18-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/tide-18-build --liveness ...

@bparees

openshift-bot commented 6 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

juanvallejo commented 6 years ago

/remove-lifecycle stale

openshift-bot commented 6 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

0xmichalis commented 6 years ago

/remove-lifecycle stale /lifecycle frozen

bparees commented 6 years ago

in general i would think no "runonce" pod should be checked for a liveness probe.