Failed to start a workspace when deployed Che with minishift addon installer

Describe the bug

Can’t start a workspace in Minishift

2019-12-02 14:08:08,958[nio-8080-exec-7]  [ERROR] [o.e.c.w.i.o.p.OpenShiftProject 178]  - Unable to create new OpenShift project due to lack of permissions.HINT: When using workspace project name placeholders, os-oauth or service account with more lenient permissions (cluster-admin) must be used.
--
  | 2019-12-02 14:08:08,961[nio-8080-exec-7]  [ERROR] [o.e.c.a.w.s.WorkspaceRuntimes 481]   - Failure executing: POST at: https://172.30.0.1/apis/project.openshift.io/v1/projectrequests . Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. projectrequests.project.openshift.io is forbidden: User "system:serviceaccount:che:che" cannot create projectrequests.project.openshift.io at the cluster scope: no RBAC policy matched. The error may be caused by an expired token or changed password. Update Che server deployment with a new token or password.
  | org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesInfrastructureException: Failure executing: POST at: https://172.30.0.1/apis/project.openshift.io/v1/projectrequests . Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. projectrequests.project.openshift.io is forbidden: User "system:serviceaccount:che:che" cannot create projectrequests.project.openshift.io at the cluster scope: no RBAC policy matched. The error may be caused by an expired token or changed password. Update Che server deployment with a new token or password.
  | at org.eclipse.che.workspace.infrastructure.openshift.project.OpenShiftProject.create(OpenShiftProject.java:182)
  | at org.eclipse.che.workspace.infrastructure.openshift.project.OpenShiftProject.prepare(OpenShiftProject.java:112)

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

1. start Minishift minishift start --profile minishift --cpus 4 --memory 10240 --docker-opt userland-proxy=false
2. Deploy Che via chectl chectl server:start -p minishift
3. Try to create and start a workspace

Expected behavior

Runtime

• minishift (v1.34.1+c2ff9cb)

Installation method

• chectl (chectl/0.0.20191028-next.e762c88 linux-x64 node-v10.17.0)

Environment

• my computer
  • Windows
  • Linux
  • macOS
• Cloud
  • Amazon
  • Azure
  • GCE
  • other (please specify)
• other: please specify

[sleshchenko]

It should be fixed by https://github.com/eclipse/che/issues/15380 but I did not test it yet. So, I believe that this issue can be closed when the PR is merged and newer chectl is tested.

[svor]

I used to use single user, with --installer=operator I have multiuser - but it isn’t a problem for me. So, workaround works for me. Thanks @skabashnyuk