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

Not possible to start a workspace if DevWorkspace is enabled #20801

Closed
svor opened this issue Nov 22, 2021 · 4 comments
Closed

Not possible to start a workspace if DevWorkspace is enabled #20801

svor opened this issue Nov 22, 2021 · 4 comments
Assignees
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator 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/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.

Comments

@svor
Copy link
Contributor

svor commented Nov 22, 2021

Describe the bug

It's not possible to start any workspace in DevWorkspace.

DevWorkspace was deployed by chectl server:deploy --installer=operator --platform=openshift --workspace-engine=dev-workspace

chectl version
chectl/0.0.20211119-next.53696c6 linux-x64 node-v12.22.7

Che version

next (development version)

Steps to reproduce

  1. Deploy DevWorkspace
  2. Try to create a workspace from the dashboard or by using factory

Expected behavior

The workspace should be created and started

Runtime

OpenShift

Screenshots

screenshot-che-eclipse-che apps cluster-5d7v2 5d7v2 sandbox925 opentlc com-2021 11 22-10_51_27

screenshot-nimbus-capture-2021 11 22-10_35_36

screenshot-console-openshift-console apps cluster-5d7v2 5d7v2 sandbox925 opentlc com-2021 11 22-10_52_27

Installation method

chectl/next

Environment

Linux

Eclipse Che Logs

Errors from devworkspace-controller-manager pod:

{"level":"info","ts":1637568774.1306536,"logger":"controllers.DevWorkspace","msg":"Error updating workspace status: Operation cannot be fulfilled on devworkspaces.workspace.devfile.io \"golang-echo-example-atxb\": the object has been modified; please apply your changes to the latest version and try again","Request.Namespace":"che-che","Request.Name":"golang-echo-example-atxb","devworkspace_id":"workspacee45c39d15b2a47e6"}
{"level":"error","ts":1637568774.130681,"logger":"controller","msg":"Reconciler error","reconcilerGroup":"workspace.devfile.io","reconcilerKind":"DevWorkspace","controller":"devworkspace","name":"golang-echo-example-atxb","namespace":"che-che","error":"Operation cannot be fulfilled on devworkspaces.workspace.devfile.io \"golang-echo-example-atxb\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:218\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:197\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\t/go/pkg/mod/k8s.io/apimachinery@v0.20.6/pkg/util/wait/wait.go:155\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\t/go/pkg/mod/k8s.io/apimachinery@v...

Additional context

No response

@svor svor 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. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. labels Nov 22, 2021
@benoitf
Copy link
Contributor

benoitf commented Nov 22, 2021

I've the same issue

@benoitf
Copy link
Contributor

benoitf commented Nov 22, 2021

As a workaround I reverted the latest commit of che-operator (eclipse-che/che-operator#1166) on a custom image (using eclipse-che/che-operator@18cdc63 )

chectl server:deploy --installer=operator --platform=openshift --workspace-engine=dev-workspace --che-operator-image=quay.io/fbenoit/che-operator:18cdc6391

and it's working again doing that

@benoitf benoitf added area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator team/deploy labels Nov 22, 2021
@svor
Copy link
Contributor Author

svor commented Nov 22, 2021

cc @tolusha @mmorhun

@benoitf benoitf changed the title Not possible to start a workspace if DevWorksapce is enable Not possible to start a workspace if DevWorkspace is enable Nov 22, 2021
@benoitf benoitf changed the title Not possible to start a workspace if DevWorkspace is enable Not possible to start a workspace if DevWorkspace is enabled Nov 22, 2021
@mmorhun mmorhun self-assigned this Nov 22, 2021
@mmorhun
Copy link
Contributor

mmorhun commented Nov 22, 2021

Fixed

@mmorhun mmorhun closed this as completed Nov 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator 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/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

No branches or pull requests

3 participants