-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[cli] fix issue around logs of che-server not written in host folder and update path of machines logs #3926
Conversation
…nally defined Change-Id: I73b8beed66b63f5368edb7b607fbdd96cbf69d93 Signed-off-by: Florent BENOIT <[email protected]>
Change-Id: I Signed-off-by: Florent BENOIT <[email protected]>
@@ -23,7 +22,8 @@ JPDA_ADDRESS=<%= scope.lookupvar('che::che_debug_port') %> | |||
|
|||
CHE_DATABASE=/data | |||
CHE_WORKSPACE_STORAGE=/data/workspaces | |||
CHE_WORKSPACE_LOGS=/data/logs/machine | |||
CHE_LOGS_DIR=/logs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it is hardcoded here then it is not possible to reassign it in user's che.env. Am I correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@garagatyi I've moved the definition few lines after its initial location so the LOGS_DIR are at the same place, I've not introduced a new hardcoded property.
AFAIK the definition of these values are "hardcoded" by CLI as it's inside the docker container. (for Che and Codenvy)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@garagatyi you may want to be able to override these values ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@garagatyi yes correct, this is the fix. Before it was hardcoded in che-server docker image. Now it is set only if not provided. And cli is providing the property so it handle it correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
Build success. https://ci.codenvycorp.com/job/che-pullrequests-build/1795/ |
Added to RN. |
What does this PR do?
Fix #3913 : che-server container should reuse property of CHE_LOGS_DIR if externally defined (else we couldn't configure the path externally)
Also machine logs should go in /logs/ folder as well (not in /data)
What issues does this PR fix or reference?
#3913
Changelog and Release Note Information
Changelog
Che logs should go in /logs folder. server log was not present.
Release Notes: N/A (bug)
Docs Pull Request
N/A as bugfix
https://www.eclipse.org/che/docs/setup/getting-started/index.html is not talking about logs