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

Errors in oc status not being printed #14794

Closed
smarterclayton opened this issue Jun 21, 2017 · 2 comments
Closed

Errors in oc status not being printed #14794

smarterclayton opened this issue Jun 21, 2017 · 2 comments
Assignees
Labels
component/cli kind/bug Categorizes issue or PR as related to a bug. priority/P1

Comments

@smarterclayton
Copy link
Contributor

smarterclayton commented Jun 21, 2017

oc status
In project default on server https://10.1.2.2:8443

svc/docker-registry - 172.30.150.71:5000
  dc/docker-registry deploys docker.io/openshift/origin-docker-registry:v3.6.0-alpha.2
    deployment #1 deployed 2 days ago - 1 pod

svc/kubernetes - 172.30.0.1 ports 443->8443, 53->8053, 53->8053

https://proxy-default.router.default.svc.cluster.local (reencrypt) (svc/proxy)
  pod/proxy-2744412972-rp4bf runs registry.svc.ci.openshift.org/ci/oauth-proxy:v1, openshift/hello-openshift:latest

bc/oauth-proxy docker builds Dockerfile on docker.io/library/centos:7
  -> istag/oauth-proxy:latest
  build #4 succeeded 2 days ago

bc/oauth-proxy-binary docker builds https://github.com/openshift/oauth-proxy.git on docker.io/openshift/origin-release:golang-1.7
  -> istag/oauth-proxy:binaries
  build #4 succeeded 2 days ago - bd24956: Merge pull request #2 from smarterclayton/fix_bar (Clayton Coleman <[email protected]>)
  build #1 failed 2 days ago - bd24956: Merge pull request #2 from smarterclayton/fix_bar (Clayton Coleman <[email protected]>)

Errors:

1 error identified, use 'oc status -v' to see details.
$ oc status -v
In project default on server https://10.1.2.2:8443

svc/docker-registry - 172.30.150.71:5000
  dc/docker-registry deploys docker.io/openshift/origin-docker-registry:v3.6.0-alpha.2
    deployment #1 deployed 2 days ago - 1 pod

svc/kubernetes - 172.30.0.1 ports 443->8443, 53->8053, 53->8053

https://proxy-default.router.default.svc.cluster.local (reencrypt) (svc/proxy)
  pod/proxy-2744412972-rp4bf runs registry.svc.ci.openshift.org/ci/oauth-proxy:v1, openshift/hello-openshift:latest

bc/oauth-proxy docker builds Dockerfile on docker.io/library/centos:7
  -> istag/oauth-proxy:latest
  build #4 succeeded 2 days ago

bc/oauth-proxy-binary docker builds https://github.com/openshift/oauth-proxy.git on docker.io/openshift/origin-release:golang-1.7
  -> istag/oauth-proxy:binaries
  build #4 succeeded 2 days ago - bd24956: Merge pull request #2 from smarterclayton/fix_bar (Clayton Coleman <[email protected]>)
  build #1 failed 2 days ago - bd24956: Merge pull request #2 from smarterclayton/fix_bar (Clayton Coleman <[email protected]>)

Errors:
  * route/proxy is routing traffic to svc/proxy, but either the administrator has not installed a router or the router is not selecting this route.
    try: oc adm router -h

This keeps happening.

@smarterclayton
Copy link
Contributor Author

Errors are supposed to be shown, not filtered.

@smarterclayton
Copy link
Contributor Author

oc status
In project default on server https://10.192.208.113:8443

svc/kubernetes - 172.30.0.1 ports 443->8443, 53->8053, 53->8053

Errors:

5 errors and 5 warnings identified, use 'oc status -v' to see details.

@pweil- pweil- added the kind/bug Categorizes issue or PR as related to a bug. label Jun 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/cli kind/bug Categorizes issue or PR as related to a bug. priority/P1
Projects
None yet
Development

No branches or pull requests

3 participants