Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 3.10.0.GA
Affects Version/s: 3.9.1.GA
Component/s: Team A: Dashboard, devfile and plugin registries, open-vsx, operator + chectl/dsc, devfile-converter, configbump + traefik, image-puller, server, gateway, authentication, try-in-web-ide action, telemetry
Labels:

Blocked:
False
Blocked Reason:
None
Ready:
False
Release Note Text:

Hide
= "No PersonalAccessTokenFetcher configured" error message appears in re-opened workspaces

Before this update, re-opening an existing workspace resulted in a "No PersonalAccessTokenFetcher configured" error message. With this update, the token is refreshed on a workspace restart.

Show
= "No PersonalAccessTokenFetcher configured" error message appears in re-opened workspaces Before this update, re-opening an existing workspace resulted in a "No PersonalAccessTokenFetcher configured" error message. With this update, the token is refreshed on a workspace restart.
Release Note Type:
Bug Fix
Release Note Status:
Done

SFDC Cases Counter:
SFDC Cases Links:

Description

Description of problem:

Client is facing issue accessing their existing workspaces where it is showing "No PersonalAccessTokenFetcher configured" when they are been accessed.
The new workspaces that client creates are working fine the git token issue exists only for the existing workspaces.

Prerequisites (if any, like setup, operators/versions):

OCP: 4.12.30
devspacesoperator.v3.9.1

Expected results:

Client is expecting token should be refreshed on a workspace restart to fix the issue.

Additional info (Such as Logs, Screenshots, etc):

Opening this JIRA with reference to previous JIRA [1] in order to have better traction of the current issue that client is facing with their existing workspaces.
[1] https://issues.redhat.com/browse/CRW-4957

[2] https://github.com/eclipse/che/issues/21291