che: The workspace status changed unexpectedly to "Stopped"

Summary

i’m receiving The workspace status changed unexpectedly to "Stopped" message, i have no idea what is the reason for this issue, please help me to debug this issue. it was working fine till yesterday

below is the error message shown in dashboard

below is the pod-workspace log

below is the devfile.yaml which i used to create the workspace

schemaVersion: 2.1.0
metadata:
  name: cbfsel-repo
projects:
  - name: cbfsel-project
    git:
      checkoutFrom:
        revision: master
      remotes:
        origin: https://gitlab.eng.vmware.com/dchelladurai/cbf-sel.git
components:
  - container:
      image: 'artfact-prd.vmware.com:5001/qedocker/eclipseche/customopenjdk8:v10'
      memoryLimit: 4G
      volumeMounts:
        - name: m2volume
          path: /home/user/.m2
    name: javacontainer
  - container:
      image: 'artfact-prd.vmware.com:5001/qedocker/eclipseche/selenium/standalone-chrome:4.3.0-20220706'
      memoryLimit: 4G
      endpoints:
        - exposure: public
          name: 4444-tcp
          protocol: tcp
          targetPort: 4444
        - exposure: public
          name: 5900-tcp
          protocol: tcp
          targetPort: 5900
        - exposure: public
          name: 7900-http
          protocol: http
          targetPort: 7900
          secure: true
    name: chromecontainer
  - name: m2volume
    volume:
      size: 4G
commands:
  - exec:
      commandLine: mvn clean package -DskipTests
      component: javacontainer
      group:
        isDefault: true
        kind: build
      label: 'build project using maven'
      workingDir: '${PROJECT_SOURCE}'
    id: mvnpackage

Relevant information

No response

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 19 (10 by maintainers)

Most upvoted comments

After updating operator image, I can’t reproduce The workspace status changed unexpectedly to "Stopped" error anymore

tolusha on Jul 20, 2022

@Divine1 You can simply delete operator pod. A new one will come up in a few seconds and a new operator image (quay.io/eclipse/che-operator:next) will be pulled up.

tolusha on Jul 20, 2022

Hi @Divine1 could you please run and paste the output for:

kubectl get configmap che-idle-settings -n divine-chelladurai-che-pmjg9u -o yaml

dkwon17 on Jul 20, 2022

I faced the same problem. It seems workspace immediately stopped after booting up. DevWorkspace controller log shows:

{"level":"info","ts":1658319000.073287,"logger":"controllers.DevWorkspace","msg":"Reconciling Workspace","Request.Namespace":"che-kube-admin-che-x4dl9t","Request.Name":"bash","devworkspace_id":"workspace0256ca635bb144a8"}
{"level":"info","ts":1658319000.0918732,"logger":"controllers.DevWorkspace","msg":"Workspace stopped with reason","Request.Namespace":"che-kube-admin-che-x4dl9t","Request.Name":"bash","devworkspace_id":"workspace0256ca635bb144a8","stopped-by":"inactivity"}

/cc @dkwon17 Could you have a look pls.

tolusha on Jul 20, 2022

@AObuchow do you have any clue about the PVC problem above?

l0rd on Jul 19, 2022

It looks like there is no PersistentVolume in your cluster that matches the PersistentVolumeClaim created by Che, hence the PVC remains unbound. You may want to decrease the m2volume size in your devfile (or remove the size at all) OR you can create a new PV matching the PVC size.

l0rd on Jul 19, 2022

Hi @Divine1 we need more logs to figure out what’s going on.

Can you please look at following when the workspaces is starting:

the DW pod logs: (DW="cbfsel-repo"; kubectl logs -f -l controller.devfile.io/devworkspace_name="${DW}" --all-containers --max-log-requests 10)
the namespace events: kubectl get events -n devine-chelladurai-che-pmjg9u
the devworkspace controller logs: kubectl logs -f deploy/devworkspace-controller-manager -n openshift-operators -c devworkspace-controller

And are you able to reproduce this problem systematically or it happens only from time to time?

And the version of Che you are using and how you are installing it are alos important informations.

l0rd on Jul 19, 2022