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

Chectl doc does not mention user priviledge requirements #14761

Closed
tsmaeder opened this issue Oct 3, 2019 · 5 comments
Closed

Chectl doc does not mention user priviledge requirements #14761

tsmaeder opened this issue Oct 3, 2019 · 5 comments
Labels
area/chectl Issues related to chectl, the CLI of Che severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@tsmaeder
Copy link
Contributor

tsmaeder commented Oct 3, 2019

The documentation at https://github.com/che-incubator/chectl/blob/master/README.md does not mention that the user needs to be logged into minishift, for example and that the user needs to have cluster admin priviledges.

@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 3, 2019
@tsmaeder tsmaeder added area/chectl Issues related to chectl, the CLI of Che team/devex severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 3, 2019
@tsmaeder
Copy link
Contributor Author

tsmaeder commented Oct 3, 2019

Improving failure diagnostics is a big ticket item and doc is part of it.

@l0rd
Copy link
Contributor

l0rd commented Oct 6, 2019

That's a bug. User should not need admin privileges to install Che on minishift.

@sleshchenko @benoitf it looks to me that chectl is broken on minishift: when calling checkKubeApi() we are trying to get token of the service account default but the default user (developer) doesn't have access to this API. That's the command output:

./bin/run server:start --platform=minishift                                                                       minishift/myproject
  ✖ Verify Kubernetes API
    → Failed to connect to Kubernetes API. Error: [object Object]
    👀  Looking for an already existing Che instance
 ›   Error: Failed to connect to Kubernetes API. Error: [object Object]

The other problem is that the error message is not parsed correctly (Error: [object Object]) and makes it impossible to understand what's going on. I suspect that this can be due to an update to the kubernetes js client. What I have seen is that the function wrapK8sClientError() tries to access e.body.message whereas it should look at e.response.body.message. When that is fixed the following error message is displayed:

  ✖ Verify Kubernetes API
    → Failed to connect to Kubernetes API. Error: Error: Unable to get default service account secret
    👀  Looking for an already existing Che instance
 ›   Error: Failed to connect to Kubernetes API. Error: Error: Unable to get default service account secret

@sleshchenko
Copy link
Member

when calling checkKubeApi() we are trying to get token of the service account default but the default user (developer) doesn't have access to this API. That's the command output:

@l0rd the fix is already done but I was not able to set up secure K8s cluster and test it there che-incubator/chectl#340

@l0rd
Copy link
Contributor

l0rd commented Oct 7, 2019

Thanks @sleshchenko for the update.

@tolusha
Copy link
Contributor

tolusha commented Feb 26, 2020

che-incubator/chectl#524 merged
Error messages are improved.

@tolusha tolusha closed this as completed Feb 26, 2020
@tolusha tolusha modified the milestones: Backlog - Deploy, 7.10.0 Feb 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/chectl Issues related to chectl, the CLI of Che severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

6 participants