-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
3.4.0.GA
-
None
-
False
-
-
False
-
-
Description of problem:
Customer is not able to create a workspace which has oauth configuration in their private gitlab instance
Making the workspace creation to fail in cloning the code into vscode
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
1. Installed Red Hat OpenShift Dev Spaces 3.4 in OCP 4.10
2. Configured oauth gitlab as per documentation: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.4/html/administration_guide/configuring-devspaces#configuring-oauth-2-for-gitlab
3. Created a workspace pointing to a private instance of gitlab with a private repository
4. IDE vscode opens with a message: Workspace does not exist. Please select another workspace to open.
5. Using an empty workspace and cloning the gitlab repo from the console works by providing user credentials.
6. devworkspace-merged-git-credentials secret in user's namespace is empty, no token information available despites the authorization gitlab page showed up.
Actual results:
IDE doesn't open when pointing to a private gitlab repo with oauth configured
Expected results:
IDE to open with code cloned from private gitlab repo configured with oauth
Reproducibility (Always/Intermittent/Only Once):
Always in customer's environment
Locally tested and worked in a lab (not customer)
Build Details:{}
Additional info (Such as Logs, Screenshots, etc):
Adding screenshots