neither Quick Start nor other ways with neo4j >= 4 are working about neo4j-helm HOT 4 CLOSED

sorry for the late answer.
Thanks for your fast answer.
After testing your solutions that didn't work for us, we still searched for the reason this was happening.
We found out that after the root user updated the neo4j.conf file in the startup script of the docker image
the user could not open the neo4f.conf file anymore.
Even if the user was the owner of the file.

We tested in a separate environment the reason behind this issue.
It turned out that there is a bug with the combination of the current sed version and the kernels of the OS the kubernetes Nodes are working on.

This result was that when the root user changed a file with a sed command the userrights and ownership of the file stayed the same but the user could not access the file without another change of the userrights.

I hope noone will ever have the same issue but if so this was our reason for the issue.
So I want to document this here and the only solutions (we know of) where

• updating the kernel
• after applying the sed do another chown or chmod

Nevertheless thank you @moxious for your support and your quick answer

from neo4j-helm.

@derbytau have you previously deployed a different cluster or instance with the name "mygraph"? The permission denied issues you're running into suggest that you maybe already had a persistent volume claim under the same name that was bound, and perhaps neo4j is running into trouble stepping on data that already existed.

I tried exactly your deploy command at the top and it worked, so I can't reproduce this. 2 specific follow-up steps to try:

• helm uninstall mygraph and then manually delete the PVC that is left over afterwards, then reinstall
• Try installing under a different name you've never used before (guaranteeing there's no leftover PVC) and see if the problem still occurs.

from neo4j-helm.

@derbytau I haven't heard back and so I'm closing this issue. The resolution above is what I think would fix the issue. But if you try it and this resolution fails, feel free to ping back, we will re-open and continue to investigate.

from neo4j-helm.

@derbytau wow, that's a pretty exotic one. Thanks for posting the solution that you found.

from neo4j-helm.