-
Bug
-
Resolution: Done
-
Critical
-
2.5.1.GA
-
False
-
False
-
Undefined
-
Workaround Exists
-
-
-
Using IBM cloud COLO for Power that need to do proxy configuration.
CLI logs
# oc project Using project "dipika-codeready" on server "https://api.ghatwala-addon06-sm-fef0.169.48.22.99.nip.io:6443" # oc get pods NAME READY STATUS RESTARTS AGEworkspacep6ggjjrsxpkgydbo.maven-cdb749555-897z5 6/6 CrashLoopBackOff 6 9m39s
logs from pod, from platform (che-jwtproxy) component
time="2021-01-11T14:29:26Z" level=info msg="Starting reverse proxy (Listening on ':4400')" time="2021-01-11T14:29:26Z" level=info msg="Starting reverse proxy (Listening on ':4401')" time="2021-01-11T14:29:26Z" level=info msg="Starting reverse proxy (Listening on ':4402')" 2021/01/11 14:30:29 [011] WARN: Websocket error: <nil>2021/01/11 14:30:29 http: response.WriteHeader on hijacked connection from github.com/eclipse/che-jwtproxy/vendor/github.com/coreos/goproxy.(*ProxyHttpServer).ServeHTTP (proxy.go:129)2021/01/11 14:30:29 http: response.Write on hijacked connection from fmt.Fprintln (print.go:265)2021/01/11 14:30:33 [011] WARN: Websocket error: readfrom tcp 127.0.0.1:39016->127.0.0.1:3100: use of closed network connection
- is related to
-
CRW-1637 Add resource limits/requests to the devfiles and plugins in the registries
- Closed