Description of problem: Check pod's log on web console, when there is no log for the pod, after the spinning icon disappears in the black box , user can only see "the status:running" and "connection closed reconnect" info. This would make user confused, they will think the logs can not be seen due to closed connection and would try again and again. It's better to show info such as "There is no log for the pod". Version-Release number of selected component (if applicable): openshift v1.0.6-876-gf453941-dirty kubernetes v1.2.0-alpha.1-1107-g4c8e6f4 etcd 2.1.2 How reproducible: Always Steps to Reproduce: 1.Create a pod, when pod is running, check there is no log for the pod. $ oc create -f origin/examples/project-quota/pod-with-resources.yaml in pro1 $ oc logs pod-with-resources -n pro1 2.Login on web console, check the logs of the pod. 3. Actual results: 1.There is no log displayed. 2.There is no log displayed, after the spinning icon disappears in the black box , user can only see "the status:running" and "connection closed reconnect" info. Expected results: 2.It's better to show info such as "There is no log for the pod". Additional info:
this got fixed in origin
Checked on origin: openshift v1.3.0-alpha.1-251-ga19279f kubernetes v1.3.0-alpha.1-331-g0522e63 etcd 2.3.0 When there is no log for pod's container, check the pod's log on web console, it will display info now: "Logs are not available. The logs are no longer available or could not be loaded." The bug has been fixed, so move it to Verified.