Red Hat Bugzilla – Bug 1257996
"oc status" makes it seem like multiple deployments are active
Last modified: 2017-02-03 15:32:12 EST
[root@ose3-master openshift-ansible]# oc version
[root@ose3-master openshift-ansible]# oc status
In project default
service/docker-registry - 172.30.241.157:5000
dc/docker-registry deploys docker.io/openshift3/ose-docker-registry:v184.108.40.206
#2 deployed about a minute ago - 1 pod
#1 deployed 3 minutes ago
service/kubernetes - 172.30.0.1:443
service/router - 172.30.141.219:80
dc/router deploys docker.io/openshift3/ose-haproxy-router:v220.127.116.11
#1 deployed 8 minutes ago - 1 pod
To see more, use 'oc describe <resource>/<name>'.
You can use 'oc get all' to see a list of other objects.
[root@ose3-master openshift-ansible]# oc get pod
NAME READY STATUS RESTARTS AGE
docker-registry-2-4wsuk 1/1 Running 0 1m
router-1-lw8ef 1/1 Running 0 8m
[root@ose3-master openshift-ansible]# oc get rc
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
docker-registry-1 registry openshift3/ose-docker-registry:v18.104.22.168 deployment=docker-registry-1,deploymentconfig=docker-registry,docker-registry=default 0
docker-registry-2 registry openshift3/ose-docker-registry:v22.214.171.124 deployment=docker-registry-2,deploymentconfig=docker-registry,docker-registry=default 1
router-1 router openshift3/ose-haproxy-router:v126.96.36.199 deployment=router-1,deploymentconfig=router,router=router 1
Since deployment #1 is no longer running, I would expect to see some indication that it isn't there. Simply listing it makes it seem like it's still running, even though no pods for deployment 1 are.
> Since deployment #1 is no longer running, I would expect to see some indication that it isn't there. Simply listing it makes it seem like it's still running, even though no pods for deployment 1 are.
I don't know if I agree with this. The latest deployment is always listed first. It also displays the number of pods it currently has, while past deployments do not. This, to me, seems like enough information to know which deployment is still relevant.
I am closing this as NOTABUG but please re-open if you feel this should still be addressed
I would think "0 pods" would be clearer than no text...
Right now it really is not providing any indication that the older deployment is not running / defunct / nothing going on.
Thanks for clarifying, opened a PR to include pod number for old deployments:
Closing, please see https://github.com/openshift/origin/pull/12763#issuecomment-277349380. The initial decision to omit "0 pods" from old deployments was deliberate.