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.

Sign up for GitHub

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

Jump to bottom

Error messages are not clear when chectl failed to start che-server #14665

Closed
tolusha opened this issue Sep 26, 2019 · 2 comments
Closed

Error messages are not clear when chectl failed to start che-server #14665

tolusha opened this issue Sep 26, 2019 · 2 comments
Labels
area/chectl Issues related to chectl, the CLI of Che kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Milestone
7.10

Comments

@tolusha
Copy link
Contributor

tolusha commented Sep 26, 2019 •
edited by sleshchenko
Loading

Is your enhancement related to a problem? Please describe.

Errors messages should be clear.
I faced the following cases:

  1. oc content is not set
  ✖ Verify Kubernetes API
    → Failed to connect to Kubernetes API. Failed to get current Kubernetes cluster: returned null
    👀  Looking for an already existing Che instance
 ›   Error: Failed to connect to Kubernetes API. Failed to get current Kubernetes cluster: returned null
  1. The current user in context is not an admin and does not have any projects
$ chectl server:start --platform=minishift  --installer=operator --k8spodreadytimeout=500000
  ✖ Verify Kubernetes API
    → Failed to connect to Kubernetes API. [object Object]
    👀  Looking for an already existing Che instance
 ›   Error: Failed to connect to Kubernetes API. [object Object]

So, chectl requires the current context to be set, and the current user should have cluster admin rights. And there is no clue about it in error messages.
@tolusha tolusha added kind/enhancement A feature request - must adhere to the feature request template. area/chectl Issues related to chectl, the CLI of Che labels Sep 26, 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 Sep 26, 2019
@sleshchenko sleshchenko changed the title Error messages are not clear when chectl starts che-server Error messages are not clear when chectl failed to start che-server Sep 26, 2019
@tsmaeder tsmaeder added 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 Sep 26, 2019
@tsmaeder
Copy link
Contributor

I'm treating this as a P1: we need to improve error analysis.

@l0rd l0rd added this to the Backlog - Dev Experience milestone Sep 27, 2019
@tsmaeder tsmaeder closed this as completed Oct 3, 2019
@tsmaeder tsmaeder reopened this Oct 3, 2019
@tsmaeder tsmaeder mentioned this issue Oct 3, 2019
Closed
This was referenced Oct 4, 2019
Closed
Merged
@tolusha tolusha mentioned this issue Nov 28, 2019
Open
@tolusha tolusha mentioned this issue Feb 18, 2020
Closed
@slemeur slemeur mentioned this issue Feb 18, 2020
Closed
5 tasks
This was referenced Feb 19, 2020
Closed
Merged
@tolusha
Copy link
Contributor Author

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
Assignees
No one assigned
Labels
area/chectl Issues related to chectl, the CLI of Che kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.10
Development

No branches or pull requests
5 participants
@benoitf @l0rd @tolusha @tsmaeder @che-bot