-
Bug
-
Resolution: Done
-
Critical
-
2.8.0.GA
-
None
-
False
-
False
-
Undefined
-
Environment
OCP 4.7 cluster
Codeready Workspaces deployed by crwctl in proxied environment
Steps to reproduce
1. Install CRW with next properties in custom-resources:
- nonProxyHosts: 'non-proxy-host'
- proxyPort: '3128'
- proxyURL: 'proxy-url'
2. Create and start workspace from any devfile.
Expected behavior:
The workspace ready to work with sample project imported successfully.
Observed behavior:
There is 'Couldn't import' error notification
This issue only for OCP 4.7. On OCP 3.11 it works as expected.
If try to get sample zip file in proxy container(like "wget https://devfile-registry-crw-crwctl-with-proxy.apps.ocp311.crw-qe.com") it returns "ERROR: cannot verify devfile-registry-crw-crwctl-with-proxy.apps.ocp311.crw-qe.com's certificate" error. With `--no-check-certificate` works as expected. It looks like proxy certificate problem but this issue not reproduces on OCP 3.11 and worked well before on OCP 4.7 in previous CRW 2.7 version.
- is related to
-
CRW-1702 Workspace start error while fetching featured recommendation: self signed certificate in certificate chain
- Closed