Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oc status says nothing about the info it has to show me #18016

Closed
0xmichalis opened this issue Jan 8, 2018 · 2 comments
Closed

oc status says nothing about the info it has to show me #18016

0xmichalis opened this issue Jan 8, 2018 · 2 comments

Comments

@0xmichalis
Copy link
Contributor

Initially:

2 warnings identified, use 'oc status -v' to see details.

When I run with -v:

Warnings:
  * bc/origin-release-golang-1.8 builds from istag/common-test-base:golang-1.8, but the image stream tag does not exist.
    try: istag/common-test-base:golang-1.8 needs to be imported.
  * bc/origin-release-golang-1.9 builds from istag/common-test-base:golang-1.9, but the image stream tag does not exist.
    try: istag/common-test-base:golang-1.9 needs to be imported.

Info:
  * pod/18cca2af-f405-11e7-a3c2-0a58ac100e1c has no liveness probe to verify pods are still running.
    try: oc set probe pod/18cca2af-f405-11e7-a3c2-0a58ac100e1c --liveness ...
  * pod/30d50c86-f3f4-11e7-a3c2-0a58ac100e1c has no liveness probe to verify pods are still running.
    try: oc set probe pod/30d50c86-f3f4-11e7-a3c2-0a58ac100e1c --liveness ...
  * pod/b5b546f0-f448-11e7-a3c2-0a58ac100e1c has no liveness probe to verify pods are still running.
    try: oc set probe pod/b5b546f0-f448-11e7-a3c2-0a58ac100e1c --liveness ...
  * pod/cdfbdeb0-f437-11e7-a3c2-0a58ac100e1c has no liveness probe to verify pods are still running.
    try: oc set probe pod/cdfbdeb0-f437-11e7-a3c2-0a58ac100e1c --liveness ...
  * pod/cherrypick-12-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/cherrypick-12-build --liveness ...
  * pod/cherrypick-13-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/cherrypick-13-build --liveness ...
  * pod/cherrypick-binaries-6-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/cherrypick-binaries-6-build --liveness ...
  * pod/cherrypick-binaries-7-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/cherrypick-binaries-7-build --liveness ...
  * pod/commenter-6-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/commenter-6-build --liveness ...
  * pod/deck-15-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/deck-15-build --liveness ...
  * pod/deck-16-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/deck-16-build --liveness ...
  * pod/deck-binaries-15-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/deck-binaries-15-build --liveness ...
  * pod/deck-binaries-16-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/deck-binaries-16-build --liveness ...
  * pod/e6afdf76-f426-11e7-a3c2-0a58ac100e1c has no liveness probe to verify pods are still running.
    try: oc set probe pod/e6afdf76-f426-11e7-a3c2-0a58ac100e1c --liveness ...
  * pod/ff641873-f415-11e7-a3c2-0a58ac100e1c has no liveness probe to verify pods are still running.
    try: oc set probe pod/ff641873-f415-11e7-a3c2-0a58ac100e1c --liveness ...
  * pod/gcsweb-4-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/gcsweb-4-build --liveness ...
  * pod/hook-11-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/hook-11-build --liveness ...
  * pod/hook-42-deploy has no liveness probe to verify pods are still running.
    try: oc set probe pod/hook-42-deploy --liveness ...
  * pod/hook-binaries-12-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/hook-binaries-12-build --liveness ...
  * pod/hook-binaries-5-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/hook-binaries-5-build --liveness ...
  * pod/horologium-10-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/horologium-10-build --liveness ...
  * pod/horologium-38-deploy has no liveness probe to verify pods are still running.
    try: oc set probe pod/horologium-38-deploy --liveness ...
  * pod/horologium-binaries-10-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/horologium-binaries-10-build --liveness ...
  * pod/horologium-binaries-9-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/horologium-binaries-9-build --liveness ...
  * pod/jenkins-config-updater-28-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-config-updater-28-build --liveness ...
  * pod/jenkins-config-updater-binaries-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-config-updater-binaries-23-build --liveness ...
  * pod/jenkins-config-updater-binaries-24-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-config-updater-binaries-24-build --liveness ...
  * pod/jenkins-operator-18-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-operator-18-build --liveness ...
  * pod/jenkins-operator-binaries-15-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-operator-binaries-15-build --liveness ...
  * pod/jenkins-operator-binaries-16-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/jenkins-operator-binaries-16-build --liveness ...
  * pod/kubernetes-metrics-4-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/kubernetes-metrics-4-build --liveness ...
  * pod/kubernetes-metrics-5-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/kubernetes-metrics-5-build --liveness ...
  * pod/kubernetes-metrics-6-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/kubernetes-metrics-6-build --liveness ...
  * pod/kubernetes-metrics-7-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/kubernetes-metrics-7-build --liveness ...
  * pod/kubernetes-metrics-binary-6-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/kubernetes-metrics-binary-6-build --liveness ...
  * pod/kubernetes-metrics-binary-7-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/kubernetes-metrics-binary-7-build --liveness ...
  * pod/kubernetes-metrics-binary-8-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/kubernetes-metrics-binary-8-build --liveness ...
  * pod/oauth-proxy-17-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/oauth-proxy-17-build --liveness ...
  * pod/oauth-proxy-18-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/oauth-proxy-18-build --liveness ...
  * pod/oauth-proxy-binary-23-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/oauth-proxy-binary-23-build --liveness ...
  * pod/oauth-proxy-binary-24-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/oauth-proxy-binary-24-build --liveness ...
  * pod/origin-release-base-1-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/origin-release-base-1-build --liveness ...
  * pod/plank-10-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/plank-10-build --liveness ...
  * pod/plank-11-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/plank-11-build --liveness ...
  * pod/plank-53-deploy has no liveness probe to verify pods are still running.
    try: oc set probe pod/plank-53-deploy --liveness ...
  * pod/plank-binaries-12-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/plank-binaries-12-build --liveness ...
  * pod/plank-binaries-5-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/plank-binaries-5-build --liveness ...
  * pod/prometheus-11-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prometheus-11-build --liveness ...
  * pod/prometheus-12-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prometheus-12-build --liveness ...
  * pod/prometheus-13-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prometheus-13-build --liveness ...
  * pod/prometheus-alertmanager-6-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prometheus-alertmanager-6-build --liveness ...
  * pod/prometheus-alertmanager-7-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prometheus-alertmanager-7-build --liveness ...
  * pod/prometheus-binary-10-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prometheus-binary-10-build --liveness ...
  * pod/prometheus-binary-11-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prometheus-binary-11-build --liveness ...
  * pod/prometheus-binary-12-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/prometheus-binary-12-build --liveness ...
  * pod/promrules-1-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/promrules-1-build --liveness ...
  * pod/promrules-2-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/promrules-2-build --liveness ...
  * pod/refresh-3-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/refresh-3-build --liveness ...
  * pod/refresh-4-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/refresh-4-build --liveness ...
  * pod/refresh-binaries-3-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/refresh-binaries-3-build --liveness ...
  * pod/refresh-binaries-4-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/refresh-binaries-4-build --liveness ...
  * pod/sinker-10-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/sinker-10-build --liveness ...
  * pod/sinker-44-deploy has no liveness probe to verify pods are still running.
    try: oc set probe pod/sinker-44-deploy --liveness ...
  * pod/sinker-9-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/sinker-9-build --liveness ...
  * pod/sinker-binaries-10-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/sinker-binaries-10-build --liveness ...
  * pod/sinker-binaries-9-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/sinker-binaries-9-build --liveness ...
  * pod/splice-10-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/splice-10-build --liveness ...
  * pod/splice-38-deploy has no liveness probe to verify pods are still running.
    try: oc set probe pod/splice-38-deploy --liveness ...
  * pod/splice-9-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/splice-9-build --liveness ...
  * pod/splice-binaries-10-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/splice-binaries-10-build --liveness ...
  * pod/splice-binaries-9-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/splice-binaries-9-build --liveness ...
  * pod/submit-queue-22-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/submit-queue-22-build --liveness ...
  * pod/submit-queue-binary-6-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/submit-queue-binary-6-build --liveness ...
  * pod/submit-queue-binary-8-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/submit-queue-binary-8-build --liveness ...
  * pod/tide-32-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/tide-32-build --liveness ...
  * pod/tide-33-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/tide-33-build --liveness ...
  * pod/tide-35-deploy has no liveness probe to verify pods are still running.
    try: oc set probe pod/tide-35-deploy --liveness ...
  * pod/tide-binaries-13-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/tide-binaries-13-build --liveness ...
  * pod/tide-binaries-14-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/tide-binaries-14-build --liveness ...
  * pod/tracer-2-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/tracer-2-build --liveness ...
  * pod/tracer-binaries-2-build has no liveness probe to verify pods are still running.
    try: oc set probe pod/tracer-binaries-2-build --liveness ...
  * dc/cherrypick has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/cherrypick --readiness ...
  * dc/cherrypick has no liveness probe to verify pods are still running.
    try: oc set probe dc/cherrypick --liveness ...
  * dc/deck has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/deck --readiness ...
  * dc/deck has no liveness probe to verify pods are still running.
    try: oc set probe dc/deck --liveness ...
  * dc/gcsweb has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/gcsweb --readiness ...
  * dc/gcsweb has no liveness probe to verify pods are still running.
    try: oc set probe dc/gcsweb --liveness ...
  * dc/hook has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/hook --readiness ...
  * dc/hook has no liveness probe to verify pods are still running.
    try: oc set probe dc/hook --liveness ...
  * dc/horologium has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/horologium --readiness ...
  * dc/horologium has no liveness probe to verify pods are still running.
    try: oc set probe dc/horologium --liveness ...
  * dc/jenkins-config-updater has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/jenkins-config-updater --readiness ...
  * dc/jenkins-config-updater has no liveness probe to verify pods are still running.
    try: oc set probe dc/jenkins-config-updater --liveness ...
  * dc/jenkins-operator has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/jenkins-operator --readiness ...
  * dc/jenkins-operator has no liveness probe to verify pods are still running.
    try: oc set probe dc/jenkins-operator --liveness ...
  * dc/jenkins-origin-operator has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/jenkins-origin-operator --readiness ...
  * dc/jenkins-origin-operator has no liveness probe to verify pods are still running.
    try: oc set probe dc/jenkins-origin-operator --liveness ...
  * dc/plank has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/plank --readiness ...
  * dc/plank has no liveness probe to verify pods are still running.
    try: oc set probe dc/plank --liveness ...
  * dc/refresh has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/refresh --readiness ...
  * dc/refresh has no liveness probe to verify pods are still running.
    try: oc set probe dc/refresh --liveness ...
  * dc/sinker has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/sinker --readiness ...
  * dc/sinker has no liveness probe to verify pods are still running.
    try: oc set probe dc/sinker --liveness ...
  * dc/splice has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/splice --readiness ...
  * dc/splice has no liveness probe to verify pods are still running.
    try: oc set probe dc/splice --liveness ...
  * dc/submit-queue has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/submit-queue --readiness ...
  * dc/submit-queue has no liveness probe to verify pods are still running.
    try: oc set probe dc/submit-queue --liveness ...
  * dc/submit-queue-openshift-ansible has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/submit-queue-openshift-ansible --readiness ...
  * dc/submit-queue-openshift-ansible has no liveness probe to verify pods are still running.
    try: oc set probe dc/submit-queue-openshift-ansible --liveness ...
  * dc/submit-queue-origin-aggregated-logging has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/submit-queue-origin-aggregated-logging --readiness ...
  * dc/submit-queue-origin-aggregated-logging has no liveness probe to verify pods are still running.
    try: oc set probe dc/submit-queue-origin-aggregated-logging --liveness ...
  * dc/submit-queue-origin-web-console has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/submit-queue-origin-web-console --readiness ...
  * dc/submit-queue-origin-web-console has no liveness probe to verify pods are still running.
    try: oc set probe dc/submit-queue-origin-web-console --liveness ...
  * dc/tide has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/tide --readiness ...
  * dc/tide has no liveness probe to verify pods are still running.
    try: oc set probe dc/tide --liveness ...
  * dc/tracer has no readiness probe to verify pods are ready to accept traffic or ensure deployment is successful.
    try: oc set probe dc/tracer --readiness ...
  * dc/tracer has no liveness probe to verify pods are still running.
    try: oc set probe dc/tracer --liveness ...

We could either collapse recurring info (though one could argue that I use -v) or at least say something in the case where I don't use -v:

2 warnings and 355 info identified, use 'oc status -v' to see details.

@openshift/sig-user-interface

@damemi
Copy link

damemi commented Feb 1, 2018

I can work on this

@damemi damemi self-assigned this Feb 1, 2018
openshift-merge-robot added a commit that referenced this issue Feb 5, 2018
Automatic merge from submit-queue.

Issue 18016: Add infos count to `oc status`

Fix for #18016

Now `oc status` without `-v` will show a count for number of errors, warnings, and info identified. Also refactored this output to reduce redundant switch statements with including infos.
@juanvallejo
Copy link
Contributor

Closing via #18422

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants