After upgrading to 3.9.51, `oc logs <pod>` commands come back with 'Bad Gateway'.
Issue
After upgrading to 3.9.51, oc logs <pod> commands come back with 'Bad Gateway'. Upon inspecting the various projects, we noticed that in some projects we can view logs while in others we cannot.
Working Projects:
[root@m1 ~]# oc project openshift-web-console
Now using project "openshift-web-console" on server "https://ose-prod-internal.example.com:8443".
[root@m1 ~]# oc get pods
NAME READY STATUS RESTARTS AGE
webconsole-9c9b46cd9-2zbdb 1/1 Running 0 3h
webconsole-9c9b46cd9-ch75b 1/1 Running 0 3h
webconsole-9c9b46cd9-cs89h 1/1 Running 0 3h
[root@m1 ~]# oc logs webconsole-9c9b46cd9-2zbdb
I1211 14:25:50.187240 1 start.go:201] OpenShift Web Console Version: v3.9.51
I1211 14:25:50.199381 1 serve.go:89] Serving securely on 0.0.0.0:8443
Bad Projects:
[root@m1 ~]# oc project default
Now using project "default" on server "https://ose-prod-internal.example.com:8443".
[root@bolosepm1 ~]# oc get pods
NAME READY STATUS RESTARTS AGE
docker-registry-6-2fzh7 1/1 Running 0 1h
docker-registry-6-rl2pj 1/1 Running 0 1h
docker-registry-6-t9kgh 1/1 Running 0 1h
registry-console-5-6dcpx 1/1 Running 0 1h
router-4-2p8kk 1/1 Running 0 1h
router-4-c4hjf 1/1 Running 0 1h
router-4-hv4zd 1/1 Running 0 1h
[root@m1 ~]# oc logs registry-console-5-6dcpx
Error from server: Get https://s1.example.com:10250/containerLogs/default/registry-console-5-6dcpx/registry-console: Bad Gateway
[root@m1 ~]# oc logs router-4-2p8kk
Error from server: Get https://i1.example.com:10250/containerLogs/default/router-4-2p8kk/router: Bad Gateway
[root@m1 ~]# oc logs docker-registry-6-2fzh7
Error from server: Get https://i1.example.com:10250/containerLogs/default/docker-registry-6-2fzh7/registry: Bad Gateway
Environment
-Openshift 3.9 (Behavior should be similar in other 3.x releases)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.