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

Workspace configurations are not saved on Che server restart. #2670

Closed
JamesDrummond opened this issue Sep 30, 2016 · 7 comments
Closed

Workspace configurations are not saved on Che server restart. #2670

JamesDrummond opened this issue Sep 30, 2016 · 7 comments
Assignees
Labels
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.
Milestone

Comments

@JamesDrummond
Copy link
Contributor

JamesDrummond commented Sep 30, 2016

On persistent storage with H2/JPA in che and docker containers

datasource is used as
https://github.com/eclipse/che/blob/dda5acf61ebe9e89a9dda6b6afe738b6fd09bfa6/assembly/assembly-main/src/assembly/tomcat/conf/server.xml#L53

and folder for db is using
https://github.com/eclipse/che/blob/dda5acf61ebe9e89a9dda6b6afe738b6fd09bfa6/assembly/assembly-main/src/assembly/bin/che.sh#L611

so database is saved into ${CHE_HOME}/db/

but when reading https://eclipse-che.readme.io/docs/usage-docker#workspace-storage we can use -e CHE_DATA_FOLDERto customize the host directory where to save the data

https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/codenvy/che.properties#L28-L29

Reproduction Steps:

  1. Start Che server with CLI or che-launcher.
  2. Create and open a new workspace.
  3. Make changes to workspace configuration.
  4. Stop che server.
  5. Repeat steps 1 and 2. Configurations are not there.

Expected behavior:

All workspace configurations are changed after restart.

Observed behavior:

Workspace configurations are not saved after restart.

Che version: 5.0.0 master(M3)

Additional information:

  • Problem started happening recently, didn't happen in an older version of Che: Yes
  • Problem can be reliably reproduced, doesn't happen randomly: Yes
@benoitf benoitf added the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Sep 30, 2016
@benoitf benoitf added this to the 5.0.0-M4 milestone Sep 30, 2016
@benoitf benoitf added the kind/bug Outline of a bug - must adhere to the bug report template. label Sep 30, 2016
@benoitf
Copy link
Contributor

benoitf commented Sep 30, 2016

adding labels asked by @JamesDrummond

@riuvshin riuvshin modified the milestones: 5.0.0-M5, 5.0.0-M4 Sep 30, 2016
@bmicklea bmicklea mentioned this issue Sep 30, 2016
11 tasks
@riuvshin
Copy link
Contributor

М4 already released. moved to M5

@riuvshin
Copy link
Contributor

@bmicklea please also move it to M5 milestone plan

@TylerJewell
Copy link

To be clear - the use case is that we need to honor the CHE_DATA_FOLDER and CHE_CONF_FOLDER variables that are in the CLI and in the che-launcher containers. These systems pass along certain configuration data to within the che-server.

https://eclipse-che.readme.io/docs/configuration#section-environment-variables

Also, if a user has 4.7.2 and they have their old JSON files saved with one of these values, then when the upgrade takes place, we should not lose that location. This should be fine, because within the che-server they were always saved in the same location. These values just change the location where they are volume mounted into che-server.

@akorneta akorneta self-assigned this Oct 3, 2016
@akorneta akorneta added the status/in-progress This issue has been taken by an engineer and is under active development. label Oct 3, 2016
@skabashnyuk
Copy link
Contributor

I'm not really familiar with che-launcher internals. @benoitf @TylerJewell can you confirm that changing -Dh2.baseDir=${CHE_HOME}/db to -Dh2.baseDir=${CHE_HOME}/storage is what are you looking for?

@benoitf
Copy link
Contributor

benoitf commented Oct 3, 2016

@skabashnyuk I would say it will at least restore the previous way of mounting storage folder

But before it seems this folder was also configurable through che.properties file

https://github.com/eclipse/che/blob/master/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/codenvy/che.properties#L28-L29

@skabashnyuk
Copy link
Contributor

skabashnyuk commented Oct 3, 2016

Ok let's restore previous way.
FYI -Dh2.baseDir= is the way to affect on database files location.
It's not pissible to configure it through che.properties now.

@bmicklea bmicklea mentioned this issue Oct 3, 2016
56 tasks
@akorneta akorneta removed the status/in-progress This issue has been taken by an engineer and is under active development. label Oct 4, 2016
@akorneta akorneta closed this as completed Oct 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

6 participants