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

Potential inconsistency between 'che_workspace_activity' and 'che_k8s_runtime' for STOPPING / STARTING workspaces #14536

Closed
3 of 19 tasks
ibuziuk opened this issue Sep 13, 2019 · 1 comment
Closed
3 of 19 tasks

Potential inconsistency between 'che_workspace_activity' and 'che_k8s_runtime' for STOPPING / STARTING workspaces #14536

ibuziuk opened this issue Sep 13, 2019 · 1 comment
Assignees
@metlos
Labels
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. status/in-progress This issue has been taken by an engineer and is under active development.
Milestone
7.2.0

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Sep 13, 2019 •
edited
Loading

Describe the bug

Related downstream issue - redhat-developer/rh-che#1612
Basically there could be a situation when che_workspace_activity has "STOPPING" / "STARTING" status, but there actual status of the workspace is "status": "STOPPED" (I assume this means no entry in the 'che_k8s_runtime' table)

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

N/A

Expected behavior

Consistency for workspace status between che_workspace_activity & che_k8s_runtime

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)

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • Hosted Che
@ibuziuk ibuziuk added 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. labels Sep 13, 2019
@ibuziuk ibuziuk mentioned this issue Sep 13, 2019
Closed
@metlos metlos self-assigned this Sep 13, 2019
@skabashnyuk skabashnyuk mentioned this issue Sep 17, 2019
Closed
15 tasks
@metlos metlos added the status/in-progress This issue has been taken by an engineer and is under active development. label Sep 17, 2019
@metlos metlos mentioned this issue Sep 17, 2019
Merged
@skabashnyuk skabashnyuk added this to the 7.2.0 milestone Sep 19, 2019
@metlos
Copy link
Contributor

metlos commented Sep 20, 2019

Implemented in #14574

@metlos metlos closed this as completed Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@metlos metlos

Labels
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. status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Milestone
7.2.0
Development

No branches or pull requests
3 participants
@metlos @ibuziuk @skabashnyuk