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

[nickboldt]

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)

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.

4. shutdown workspace as directed. Restart it.

5. 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."

Environment

• Hosted Che

[amisevsk]

@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]

should be fixed by #14950