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

[devworkspace-che-operator] A failed workspace routing is not finalized #19067

Closed
metlos opened this issue Feb 15, 2021 · 1 comment
Closed
Assignees
Labels
engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. 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

@metlos
Copy link
Contributor

metlos commented Feb 15, 2021

Is your enhancement related to a problem? Please describe.

When there is a failed devworkspace (with che routingClass) with a workspace routing in the "Failed" phase, the routing is not cleaned up upon deleting the devworkspace object.

Describe the solution you'd like

The devworkspace che operator should correctly process the workspace routing and clean up the finalizer so that the routing can be properly deleted along with the owning devworkspace object.

Describe the bug

When there is a failed devworkspace (with che routingClass) with a workspace routing in the "Failed" phase, the routing is not cleaned up upon deleting the devworkspace object.

Che version

devworkspace-operator master + devworkspace-che-operator master

Steps to reproduce

  1. Create 2 chemanager objects in the cluster
  2. Apply the sample workspace from the devworkspace-che-operator repo
  3. run kubectl delete devworkspace theia-nodejs

Expected behavior

The delete completes successfully and there is no workspacerouting object in the namespace where the devworkspace object was deployed.

Runtime

  • minikube (minikube version: v1.17.1, Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:52:00Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:20:00Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
    )

Installation method

Manual

Environment

my computer, linux

@metlos metlos added kind/bug Outline of a bug - must adhere to the bug report template. engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. labels Feb 15, 2021
@skabashnyuk skabashnyuk added this to the 7.27 milestone Feb 15, 2021
@ibuziuk ibuziuk added the severity/P1 Has a major impact to usage or development of the system. label Feb 15, 2021
@metlos metlos self-assigned this Feb 19, 2021
@metlos
Copy link
Contributor Author

metlos commented Mar 1, 2021

All PRs related to this problem are merged, closing.

@metlos metlos closed this as completed Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. 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
None yet
Development

No branches or pull requests

3 participants