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

[Hosted Che] Forbidden!Configured service account doesn't have access. Service account may have been revoked. #14830

Closed
2 of 4 tasks
nickboldt opened this issue Oct 9, 2019 · 2 comments
Assignees
Labels
area/editor/theia Issues related to the che-theia IDE of Che kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@nickboldt
Copy link
Contributor

nickboldt commented Oct 9, 2019

Describe the bug

After generating an ssh key for use with a private github repo, I restarted my che.openshift.io workspace. And it broke as in #12366

Che version

  • latest
  • nightly
  • other: please specify che.openshift.io (7.1.0)

image

Steps to reproduce

  1. import a devfile into che.openshift.io such as https://che.openshift.io/f?url=https://raw.githubusercontent.com/eclipse/che-devfile-registry/master/devfiles/php-web-simple/devfile.yaml

  2. when the workspace loads, hit F1 then type "ssh" to find ssh commands.

  3. generate a SSH key. Upload it to github. Note the message that appears in the bottom right corner of the Theia editor:

Che Git plugin can leverage the generated keys now. To make them available in every workspace containers please restart your workspace.
  1. shutdown workspace as directed. Restart it.

  2. Wonder what cloud gods have forsaken you when you see this:

Error: Failed to run the workspace: "Failure executing: POST at: https://f8osoproxy-test-dsaas-production.09b5.dsaas.openshiftapps.com/api/v1/namespaces/nickboldt2-che/secrets. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. secrets "workspaceqqsx7krkwhp1b06s-github-com" is forbidden: exceeded quota: object-counts, requested: secrets=1, used: secrets=20, limited: secrets=20. The error may be caused by an expired token or changed password. Update Che server deployment with a new token or password."

image

Environment

  • Hosted Che
@nickboldt nickboldt added the kind/bug Outline of a bug - must adhere to the bug report template. label Oct 9, 2019
@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 Oct 9, 2019
@benoitf benoitf added this to the Backlog - IDE 1 milestone Oct 9, 2019
@benoitf benoitf added area/editor/theia Issues related to the che-theia IDE of Che severity/P1 Has a major impact to usage or development of the system. team/ide and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 9, 2019
@l0rd l0rd added the status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach label Oct 11, 2019
@l0rd l0rd removed this from the Backlog - IDE 1 milestone Oct 11, 2019
@amisevsk
Copy link
Contributor

@nickboldt Could you list the secrets in your namespace? Is the issue a quota issue in general or are we creating secrets that aren't getting deleted?

@vparfonov
Copy link
Contributor

should be fixed by #14950

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/editor/theia Issues related to the che-theia IDE of Che kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Development

No branches or pull requests

7 participants