Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't start a workspace by factory on dogfooding instance #21421

Closed
Tracked by #21438 ...
svor opened this issue May 24, 2022 · 3 comments · Fixed by eclipse-che/che-server#327
Closed
Tracked by #21438 ...

Can't start a workspace by factory on dogfooding instance #21421

svor opened this issue May 24, 2022 · 3 comments · Fixed by eclipse-che/che-server#327
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. sprint/current

Comments

@svor
Copy link
Contributor

svor commented May 24, 2022

Describe the bug

It is not possible to start any workspace by using factory.

The error is: Failed to resolve a devfile. Failed to request factory resolver: There is an error happened when communicate with SCM server. Error message: Unexpected status code 401 (GET https://api.github.com/user) 401

Che version

next (development version)

Steps to reproduce

  1. Try to start the workspace by https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/#/https://github.com/crw-samples/web-nodejs-sample/tree/che-qe-no-extensions

Expected behavior

The workspace should start

Runtime

OpenShift

Screenshots

screenshot-che-dogfooding apps che-dev x6e0 p1 openshiftapps com-2022 05 24-18_37_14

Installation method

OperatorHub

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

@svor svor added the kind/bug Outline of a bug - must adhere to the bug report template. label May 24, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 24, 2022
@benoitf
Copy link
Contributor

benoitf commented May 24, 2022

you should remove your ‘personal-access-token’ secret from your user namespace

@azatsarynnyy azatsarynnyy added kind/question Questions that haven't been identified as being feature requests or bugs. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. kind/question Questions that haven't been identified as being feature requests or bugs. labels May 24, 2022
@azatsarynnyy
Copy link
Member

Removing the personal-access-token secret fixed the problem for me.
I'm closing this one within the issue triage process. Feel free to reopen if the problem is still relevant.

@ibuziuk ibuziuk reopened this May 25, 2022
@ibuziuk
Copy link
Member

ibuziuk commented May 25, 2022

if this error occurs there should be a clear error message with the instructions on how to fix it. In the ideal case we should prevent this error from occurring and renew the token if expired

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. sprint/current
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants