-
Notifications
You must be signed in to change notification settings - Fork 147
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
Elasticsearch unable to start because of java.lang.IllegalStateException: Failed to create node environment #2609
Comments
@vincenzodnp so I'm confused why this needs to be changed now? as it worked from february 2021 until now? |
Maybe this is something specific to GCP? as this happened when we tried to deploy things to GCP today |
Here the change made by @shreddedbacon |
I did some more research on this, as I was confused why this has not been a problem earlier. So turns out if you mount a NEW PVC into a container, without any
see the
which means the elasticsearch user has no write access to the PVC (user doesn't match, and the group matches, but the group does not have write access). Now, if you set
the big difference is the Now why id this not cause more havoc: It also only causes issues with container images that switch the user of the service to something else than |
Fixed in #2610 |
Describe the bug
Elasticsearch image is not able to create "node environment" in the mounted (persistent)
/usr/share/elasticsearch/data
This is due to permission issues because of
fsGroup
(it was set to0
)The Java Exception is:
java.lang.IllegalStateException: Failed to create node environment
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Elasticsearch pod up&running.
Additional context
Tested by adding
fsGroup: 0
in the deploymentsecurityContext
and it works as expectedThe text was updated successfully, but these errors were encountered: