It isn't possible to start workspace once it has been stopped #14436

vitaliy-guliy · 2019-09-05T10:01:03Z

Today morning it become not possible to start the workspace.
The day before I used to stop minikube, and after starting the minikube again my workspace become not accessible.

Describe the bug

Nothing to describe. Just stop the minikube and start it in a day.
I believe that after deleting the minikube machine, updating chectl and creating the machine again everything could be fine. But it's not an option for the developer who is focused on doing his job.

Che version

latest
nightly

Steps to reproduce

  $minikube stop
  $minikube start

Expected behavior

Workspace must be running with alive IDE.

Runtime

minikube (include output of minikube version and kubectl version)

Screenshots

Installation method

chectl

Environment

my computer
- Linux

Devfile

metadata:
  name: che-theia-all
projects:
  - name: che-theia
    source:
      location: 'https://github.com/eclipse/che-theia.git'
      type: git
      branch: master
  - name: theia
    source:
      location: 'https://github.com/theia-ide/theia.git'
      type: git
      branch: master
components:
  - mountSources: true
    endpoints:
      - name: theia-dev-flow
        attributes:
          protocol: http
          public: 'true'
        port: 3010
    memoryLimit: 3Gi
    type: dockerimage
    image: 'eclipse/che-theia-dev:next'
    alias: che-dev
  - id: redhat/vscode-yaml/latest
    type: chePlugin
  - id: che-incubator/typescript/latest
    type: chePlugin
apiVersion: 1.0.0
commands:
  - name: init ... DEV che-theia
    actions:
      - workdir: /projects/theia
        type: exec
        command: |
          che:theia init
        component: che-dev

IDE2 team is using Che-Theia daily and expected that everything is always working.
Taking that into account I marked the issue as blocking.

The text was updated successfully, but these errors were encountered:

tolusha · 2019-09-05T11:08:34Z

@skabashnyuk Could you have a look pls to decide if it is blocker?

sleshchenko · 2019-09-05T11:12:45Z

@vitaliy-guliy Please add Devfile of the workspace to issue description

vitaliy-guliy · 2019-09-05T11:25:22Z

I believe it's blocking for whom is using Che-Theia, I'm talking not about severity/blocker label.
I often hear that I should push the changes to the GitHub as often as possible. But here is a question of the stability.
A developer is usually become upset when he cannot access his sources.

sleshchenko · 2019-09-05T11:29:48Z

Looks like it's caused by #14402
cc @vzhukovskii

tolusha · 2019-09-05T11:34:45Z

@vitaliy-guliy I agree with you

skabashnyuk · 2019-09-05T11:40:14Z

I was able to successfully create/start/stop workspace from provided devfile. I think it's something related to profile configuration && as @sleshchenko suggested may be related to #14402

vitaliy-guliy · 2019-09-05T11:40:33Z

I get an error when creating and starting a workspace from any node stack

2019-09-05 11:38:04,581[nio-8080-exec-5]  [INFO ] [o.e.c.a.w.s.WorkspaceRuntimes 432]   - Starting workspace 'che/n10' with id 'workspaceal2r9uu2yh726m5f' by user 'che'
2019-09-05 11:38:04,599[aceSharedPool-1]  [WARN ] [.i.k.KubernetesInternalRuntime 249]  - Failed to start Kubernetes runtime of workspace workspaceal2r9uu2yh726m5f. Cause: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 29 path $.
2019-09-05 11:38:04,629[aceSharedPool-1]  [INFO ] [o.e.c.a.w.s.WorkspaceRuntimes 854]   - Workspace 'che:n10' with id 'workspaceal2r9uu2yh726m5f' start failed
2019-09-05 11:38:04,630[aceSharedPool-1]  [ERROR] [o.e.c.a.w.s.WorkspaceRuntimes 864]   - java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 29 path $.
org.eclipse.che.api.workspace.server.spi.InternalInfrastructureException: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 29 path $.
	at org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesInternalRuntime.wrapAndRethrow(KubernetesInternalRuntime.java:865)
	at org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesInternalRuntime.internalStart(KubernetesInternalRuntime.java:271)
	at org.eclipse.che.api.workspace.server.spi.InternalRuntime.start(InternalRuntime.java:141)
	at org.eclipse.che.api.workspace.server.WorkspaceRuntimes$StartRuntimeTask.run(WorkspaceRuntimes.java:830)
	at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:38)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 29 path $.
	at com.google.gson.Gson.fromJson(Gson.java:939)
	at com.google.gson.Gson.fromJson(Gson.java:892)
	at com.google.gson.Gson.fromJson(Gson.java:841)
	at org.eclipse.che.workspace.infrastructure.kubernetes.provision.GitUserProfileProvisioner.getMapFromJsonObject(GitUserProfileProvisioner.java:87)
	at org.eclipse.che.workspace.infrastructure.kubernetes.provision.GitUserProfileProvisioner.lambda$provision$1(GitUserProfileProvisioner.java:69)
	at java.util.Optional.ifPresent(Optional.java:159)
	at org.eclipse.che.workspace.infrastructure.kubernetes.provision.GitUserProfileProvisioner.provision(GitUserProfileProvisioner.java:67)
	at org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesEnvironmentProvisioner$KubernetesEnvironmentProvisionerImpl.provision(KubernetesEnvironmentProvisioner.java:156)
	at org.eclipse.che.workspace.infrastructure.kubernetes.wsplugins.PluginBrokerManager.getTooling(PluginBrokerManager.java:110)
	at org.eclipse.che.workspace.infrastructure.kubernetes.wsplugins.SidecarToolingProvisioner.provision(SidecarToolingProvisioner.java:79)
	at org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesInternalRuntime.internalStart(KubernetesInternalRuntime.java:183)
	... 7 common frames omitted
Caused by: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 1 column 29 path $.
	at com.google.gson.stream.JsonReader.nextString(JsonReader.java:825)
	at com.google.gson.internal.bind.TypeAdapters$16.read(TypeAdapters.java:402)
	at com.google.gson.internal.bind.TypeAdapters$16.read(TypeAdapters.java:390)
	at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:41)
	at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:187)
	at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:145)
	at com.google.gson.Gson.fromJson(Gson.java:927)
	... 17 common frames omitted

vitaliy-guliy · 2019-09-05T11:49:58Z

Preferences

GET http://che-che.192.168.99.112.nip.io/api/preferences

{ 
   "theia-user-preferences":"{\"chePlugins.repositories\":{\"Eclipse Che plugins\":\"http://plugin-registry-che.192.168.99.112.nip.io/v3/plugins/\",\"my\":\"https://raw.githubusercontent.com/vitaliy-guliy/che-theia-plugin-registry/master/plugins/plugins.json\"}}",
   "codenvy:created":"1567082487909",
   "temporary":"false"
}

Profile
GET http://che-che.192.168.99.112.nip.io/api/profile

{ 
   "links":[ 
      { 
         "href":"http://che-che.192.168.99.112.nip.io/api/profile",
         "rel":"current_profile",
         "method":"GET",
         "produces":"application/json"
      },
      { 
         "href":"http://che-che.192.168.99.112.nip.io/api/profile/che",
         "rel":"self",
         "method":"GET",
         "produces":"application/json"
      },
      { 
         "href":"http://che-che.192.168.99.112.nip.io/api/profile/attributes",
         "rel":"current_profile.attributes",
         "method":"PUT",
         "produces":"application/json",
         "consumes":"application/json"
      },
      { 
         "href":"http://che-che.192.168.99.112.nip.io/api/profile/attributes",
         "rel":"current_profile.attributes",
         "method":"DELETE",
         "produces":"application/json",
         "consumes":"application/json"
      },
      { 
         "href":"http://che-che.192.168.99.112.nip.io/api/profile/che/attributes",
         "rel":"profile.attributes",
         "method":"PUT",
         "produces":"application/json",
         "consumes":"application/json"
      }
   ],
   "email":"che@eclipse.org",
   "userId":"che"
}

vzhukovs · 2019-09-05T12:26:44Z

Will take a look on it

vitaliy-guliy added 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. team/platform labels Sep 5, 2019

che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 5, 2019

tolusha removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 5, 2019

sleshchenko added team/ide and removed team/platform labels Sep 5, 2019

tolusha changed the title ~~Failed to run the workspace: java.lang.IllegalStateException~~ It isn't possible to start workspace once it has been stopped Sep 5, 2019

che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 5, 2019

skabashnyuk added this to the 7.2.0 milestone Sep 5, 2019

vzhukovs self-assigned this Sep 5, 2019

tolusha removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 5, 2019

vparfonov mentioned this issue Sep 5, 2019

IDE-2019-09-24 (Sprint: 172) #14295

Closed

19 tasks

vzhukovs mentioned this issue Sep 5, 2019

Reconfigure Gson to parse more complex theia preference object #14442

Merged

vzhukovs closed this as completed Sep 10, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

It isn't possible to start workspace once it has been stopped #14436

It isn't possible to start workspace once it has been stopped #14436

vitaliy-guliy commented Sep 5, 2019 •

edited

Loading

tolusha commented Sep 5, 2019

sleshchenko commented Sep 5, 2019

vitaliy-guliy commented Sep 5, 2019 •

edited

Loading

sleshchenko commented Sep 5, 2019

tolusha commented Sep 5, 2019

skabashnyuk commented Sep 5, 2019

vitaliy-guliy commented Sep 5, 2019

vitaliy-guliy commented Sep 5, 2019 •

edited

Loading

vzhukovs commented Sep 5, 2019

It isn't possible to start workspace once it has been stopped #14436

It isn't possible to start workspace once it has been stopped #14436

Comments

vitaliy-guliy commented Sep 5, 2019 • edited Loading

Describe the bug

Che version

Steps to reproduce

Expected behavior

Runtime

Screenshots

Installation method

Environment

Devfile

tolusha commented Sep 5, 2019

sleshchenko commented Sep 5, 2019

vitaliy-guliy commented Sep 5, 2019 • edited Loading

sleshchenko commented Sep 5, 2019

tolusha commented Sep 5, 2019

skabashnyuk commented Sep 5, 2019

vitaliy-guliy commented Sep 5, 2019

vitaliy-guliy commented Sep 5, 2019 • edited Loading

vzhukovs commented Sep 5, 2019

vitaliy-guliy commented Sep 5, 2019 •

edited

Loading

vitaliy-guliy commented Sep 5, 2019 •

edited

Loading

vitaliy-guliy commented Sep 5, 2019 •

edited

Loading