-
Bug
-
Resolution: Done
-
Critical
-
3.9.1.GA
-
None
-
False
-
-
False
-
Workaround Exists
-
-
-
Description of problem:
It's not possible to log into Dev Spaces after adding incorrect BitBucket Server personal access token.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Go to workspaces.openshift.com
- Open Dev Spaces Dashboard
- Go to "Dashboard > User Preferences > Personal Access Tokens" page
- Try to add incorrect personal access token for Bitbucket Server
- Reload Dev Spaces page
Actual results:
Error page with "Backend is not available. Try to refresh the page or re-login to the Dashboard." message displayed, and "Sign in" button were redirecting to those error page again.
There was 500 error return from https://devspaces.apps.sandbox-m4.g2pi.p1.openshiftapps.com/api/kubernetes/namespace/provision
Screencast: devsandbox_3.9.1_bitbucket_serwer_CRW-5291.webm
Expected results:
It's possible to log into Dev Spaces
Reproducibility (Always/Intermittent/Only Once):
Always
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
There was no problem with log into Dev Spaces after trying to add incorrect personal access token for other supported Git providers:
- is related to
-
CRW-4351 "Backend is not available" error when trying to login into Dev Spaces Dashboard with both Bitbucket Server OAuth and PAT configured
-
- Resolved
-
- links to