Uploaded image for project: 'Eclipse Che development'
  1. Eclipse Che development
  2. CHE-216

Cannot start stopped workspace on free-int

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • IDE
    • None

      Starting a stopped workspace on free-int cluster fails. It starts a workspace, but it hangs on a job

      Restoring project structure...

      it does not proceed further. So far I have wait over 10 minuted and the job is still there.

      There is no relevant log in Che server pod. Just for curiosity, this is the log from the point of started workspace:

       2017-04-19 12:03:22,185[aceSharedPool-0]  [INFO ] [o.e.c.a.w.s.WorkspaceManager 756]    - Workspace 'che/jkjordhv' with id 'workspacevcuw2hy3p0f0mqaa' started by user 'che'
      2017-04-19 12:07:54,889[ ConnectionPool]  [WARN ] [okhttp3.OkHttpClient 129]            - A connection to https://kubernetes.default.svc/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
      2017-04-19 12:07:57,605[ ConnectionPool]  [WARN ] [okhttp3.OkHttpClient 129]            - A connection to https://kubernetes.default.svc/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
      2017-04-19 12:07:57,612[ ConnectionPool]  [WARN ] [okhttp3.OkHttpClient 129]            - A connection to https://kubernetes.default.svc/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
      2017-04-19 12:08:02,300[ ConnectionPool]  [WARN ] [okhttp3.OkHttpClient 129]            - A connection to https://kubernetes.default.svc/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
      2017-04-19 12:08:04,994[ ConnectionPool] [WARN ] [okhttp3.OkHttpClient 129] - A connection to https://kubernetes.default.svc/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);

              amisevsk Angel Misevski (Inactive)
              mlabuda_jira Marián Labuda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: