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

Che cannot access old database after it's upgrade #8068

Closed
mkuznyetsov opened this issue Dec 27, 2017 · 1 comment · Fixed by #8073
Closed

Che cannot access old database after it's upgrade #8068

mkuznyetsov opened this issue Dec 27, 2017 · 1 comment · Fixed by #8073
Labels
kind/bug Outline of a bug - must adhere to the bug report template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@mkuznyetsov
Copy link
Contributor

Description

After upgrading existing Che instance to 6.0.0-M3 version, it doesn't work with existing database but new one is being created and used instead.

Old database location: /<path_to_che_instance/data/db/che.mv.db
New database location: /<path_to_che_instance/data/storage/db/che.mv.db

Reproduction Steps

  1. Run any Che prior to 6.0.0-M3 version.
  2. Stop it, and upgrade that Che instance to 6.0.0-M3
  3. Run upgraded Che

OS and version:
Fedora 27

@mkuznyetsov mkuznyetsov added kind/bug Outline of a bug - must adhere to the bug report template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Dec 27, 2017
@mkuznyetsov
Copy link
Contributor Author

Some exports in entrypoint.sh are overriding the enviroment variables that are being provided in Che env file from init image

entrypoint.sh: https://github.com/eclipse/che/blob/master/dockerfiles/che/entrypoint.sh#L233
che.env.erb: https://github.com/eclipse/che/blob/master/dockerfiles/init/modules/che/templates/che.env.erb#L36

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. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants