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

chectl: k8s health check fails if logged in user does not have cluster admin rights #14534

Closed
8 of 23 tasks
sleshchenko opened this issue Sep 13, 2019 · 5 comments
Closed
8 of 23 tasks

chectl: k8s health check fails if logged in user does not have cluster admin rights #14534

sleshchenko opened this issue Sep 13, 2019 · 5 comments
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template.
Milestone
7.10

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Sep 13, 2019 •
edited
Loading

Describe the bug

chectl: k8s health check fails if logged in user does not have cluster admin rights
See more che-incubator/chectl#257 (comment)

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. Start minishift.
  2. Log in as developer.
  3. Try to deploy Che with chectl and minishift addon as installer.

Actual behavior

Chectl failed to check cluster status:
Screenshot_20190910_135245

Expected behavior

Che is deployed.

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Installation method

  • chectl (minishift-addon as installer)
  • che-operator
  • minishift-addon
  • I don't know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify
@sleshchenko sleshchenko added the kind/bug Outline of a bug - must adhere to the bug report template. label Sep 13, 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 13, 2019
@sleshchenko sleshchenko mentioned this issue Sep 13, 2019
Merged
@sleshchenko sleshchenko changed the title chectl: k8s health check fails is logged in used does not have cluster admin rights chectl: k8s health check fails if logged in user does not have cluster admin rights Sep 13, 2019
@rhopp
Copy link
Contributor

rhopp commented Sep 13, 2019

I'm bit puzzled...
You are saying you encounter this problem, when installing on minishift as the default user developer using minishift-addon installer, yet the error message you have in the screenshot is (in the chectl source code) used only when stopping or deleting server (AFAIK).
So I've gone and tried ti by myself and indeed chectl server:start failed, but on something different -> Get pods by selector "app=che" returned 3 pods (1 was expected) (chectl expects the selector to return just one pod, instead it gets three (server+2 registries))

Could you tell me what I've been doing wrong to reproduce this issue?

@rhopp rhopp added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 13, 2019
@sleshchenko
Copy link
Member Author

So I've gone and tried ti by myself and indeed chectl server:start failed, but on something different -> Get pods by selector "app=che" returned 3 pods (1 was expected) (chectl expects the selector to return just one pod, instead it gets three (server+2 registries))

It's another issue I wanted to report but have not done it yet, will create it soon.

Could you tell me what I've been doing wrong to reproduce this issue?

To easily reproduce this issue - please start from a scratch - remote existing Che namespace, log in as developer and try to deploy Che, for example with minishift-addon. There are other scenarios when you can face the same issue, but I think it's should be the simplest. Let me know if you still is not able to reproduce it.

@sleshchenko
Copy link
Member Author

@rhopp here is a quick fix for the issue you faced che-incubator/chectl#322

@sleshchenko
Copy link
Member Author

@rhopp I reproduced this issue on the latest chectl from next channel.
And also registered an issue that I mentioned when chectl fails to start Che because of 2 pods while 1 is expected #14595

@sleshchenko sleshchenko added the area/chectl Issues related to chectl, the CLI of Che label Sep 19, 2019
@sleshchenko sleshchenko mentioned this issue Sep 26, 2019
Closed
23 tasks
@sleshchenko sleshchenko mentioned this issue Oct 4, 2019
Closed
@tolusha tolusha added team/deploy and removed status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Feb 20, 2020
This was referenced Feb 20, 2020
Closed
Merged
@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 added this to the 7.10.0 milestone 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/bug Outline of a bug - must adhere to the bug report template.
Projects
None yet
Milestone
7.10
Development

Successfully merging a pull request may close this issue.

fix: do not fetch service account if it's unneeded sleshchenko/chectl
4 participants
@rhopp @tolusha @sleshchenko @che-bot