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 cannot find a workspace pod while injecting kubeconfig #14746

Closed
5 of 23 tasks
azatsarynnyy opened this issue Oct 2, 2019 · 0 comments · Fixed by che-incubator/chectl#335
Closed
5 of 23 tasks
Assignees
Labels
area/chectl Issues related to chectl, the CLI of Che severity/P1 Has a major impact to usage or development of the system.

Comments

@azatsarynnyy
Copy link
Member

Describe the bug

chectl workspace:inject -k looks for a workspace pod by label che.workspace_id. But it gets incorrect pod since there's another pod with the same label may present - che-jwt-proxy.

Need to change the way of looking for a workspace pod relying on the label che.original_name=che-workspace-pod.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

Call chectl workspace:inject -k. It should find a single running workspace pod. But it reports:

  ✔ Verify if namespace che exists
  ✖ Verify if the workspaces is running
    → More than one pod with running workspace is found. Please, specify Che Workspace ID.
    Injecting configurations
 ›   Error: More than one pod with running workspace is found. Please, specify Che Workspace ID.

Even after specifying the correct workspace ID, chectl tries using incorrect pod:

  ✔ Verify if namespace che exists
  ✔ Verify if the workspaces is running
  ✔ Injecting configurations
    ↓ injecting kubeconfig into container verifier [skipped]
      → Command failed with exit code 1 (EPERM): kubectl exec workspacedwptaf8bkgtune92.che-jwtproxy-6758c84d55-dqr4m -n che -c verifier -- mkdir //.kube -p

Expected behavior

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)

Screenshots

Installation method

  • chectl
  • che-operator
  • minishift-addon
  • I don't know

Environment

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

Additional context

@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 2, 2019
@benoitf benoitf added area/chectl Issues related to chectl, the CLI of Che 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 2, 2019
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

Successfully merging a pull request may close this issue.

3 participants