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

User reports that Che workspace that entered 'timeout' does not always restart on first attempt #16418

Closed
2 of 23 tasks
skabashnyuk opened this issue Mar 22, 2020 · 0 comments
Closed
2 of 23 tasks
Assignees
Labels
area/che-server kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

Describe the bug

After failed attempt users has to restart che workspace several times.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. Workspace fail to start like this [OpenShift OAuth] Idling doesn't have enough permissions to stop the workspace. #15906
  2. Re-Start workspace fails
  3. The second attempt successful.

Expected behavior

  1. Restart should be successful with the first attempt with high probability.

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

Eclipse Che Logs

Additional context

@skabashnyuk skabashnyuk added kind/bug Outline of a bug - must adhere to the bug report template. area/che-server severity/P1 Has a major impact to usage or development of the system. team/platform labels Mar 22, 2020
@skabashnyuk skabashnyuk added this to the 7.12 milestone Mar 22, 2020
@sparkoo sparkoo self-assigned this Mar 31, 2020
@skabashnyuk skabashnyuk added this to To do in Che Platform team sprint #182 via automation Apr 1, 2020
@skabashnyuk skabashnyuk moved this from To do to In progress in Che Platform team sprint #182 Apr 1, 2020
@sparkoo sparkoo closed this as completed Apr 1, 2020
Che Platform team sprint #182 automation moved this from In progress to Done Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
No open projects
Development

No branches or pull requests

2 participants