Closed davsclaus closed 9 years ago
If you leave the screen on the pods page, then the age stays as-is.
If you run oc get pods on a shell you can see the age is older than on the ui. You will have to navigate in the web console to get age updated.
oc get pods
And the age from the shell
davsclaus:/workspace/fabric8-installer/vagrant/openshift-latest (master)/$ oc get pods NAME READY REASON RESTARTS AGE amqbroker-dw4yt 1/1 Running 0 21m docker-registry-1-gkjxt 1/1 Running 0 33m elasticsearch-18huo 2/2 Running 0 33m fabric8-8nq6i 1/1 Running 0 33m fabric8mq-consumer-l6n5e 1/1 Running 0 22m fabric8mq-js70k 1/1 Running 0 21m fabric8mq-producer-0bro0 1/1 Running 0 17m fluentd-elasticsearch-172.28.128.4 1/1 Running 0 32m kibana-mmn93 1/1 Running 0 33m router-1-0ki8h 1/1 Running 0 35m
Ah bollocks looks like I must have navigated, let me wait a bit longer for a new screenshot
oh they update now. But I did have them with old age, eg > 5 min behind.
Leg me see if I can reproduce and then reopen
If you leave the screen on the pods page, then the age stays as-is.
If you run
oc get pods
on a shell you can see the age is older than on the ui. You will have to navigate in the web console to get age updated.And the age from the shell