-
Bug
-
Resolution: Done
-
Major
-
2.1.0.GA
Use case:
- Install CRW with OS OAuth support
- Login into CRW as admin user
- Create and start workspace
- "oc login" as admin user
- Execute "crwctl workspace:inject" command
Expected result:
[ndp@localhost tmp]$ crwctl/bin/crwctl workspace:inject -n crw-using-crwctl-tls-oauth -k ✔ Verify if namespace crw-using-crwctl-no-tls-with-oauth exists ✔ Verify if the workspaces is running ✔ Injecting configurations
Actual wrong result:
[ndp@localhost tmp]$ crwctl/bin/crwctl workspace:inject -n crw-using-crwctl-tls-oauth -k ✔ Verify if namespace crw-using-crwctl-tls-oauth exists ✖ Verify if the workspaces is running → No workspace pod is found Injecting configurations › Error: No workspace pod is found [ndp@localhost tmp]$ crwctl/bin/crwctl workspace:inject -n crw-using-crwctl-tls-oauth -k -w java-eap-maven-h8goy ✔ Verify if namespace crw-using-crwctl-tls-oauth exists ✖ Verify if the workspaces is running → No workspace pod is found Injecting configurations › Error: No workspace pod is found
Root cause:
workspace pod is placed into separate namespace <username>-codeready
References:
"crwctl workspace:inject" command documentation.
- is documented by
-
RHDEVDOCS-1807 Document the fact that "crwctl workspace:inject" command doesn't work in CRW workspace with OS OAuth support
-
- Closed
-
