[stable/neo4j] Unable to run the cluster

[ppoliani]

Describe the bug I follow the instruction to install the helm chart:

helm install neo4j-helm ./ --set acceptLicenseAgreement=yes --set image=neo4j  --set imageTag=4.0.0-enterprise --set core.persistentVolume.storageClass=do-block-storage --set core.persistentVolume.size=2Gi  

I can see the pods running however when I check the logs I see the following lines:

Starting Neo4j.
2020-02-28 13:48:23.013+0000 WARN Unrecognized setting. No declared setting with name: PORT.7687.TCP.PORT
2020-02-28 13:48:23.019+0000 WARN Unrecognized setting. No declared setting with name: PORT.7474.TCP.ADDR
2020-02-28 13:48:23.019+0000 WARN Unrecognized setting. No declared setting with name: PORT.7687.TCP.PROTO
2020-02-28 13:48:23.019+0000 WARN Unrecognized setting. No declared setting with name: PORT.7474.TCP.PROTO
2020-02-28 13:48:23.020+0000 WARN Unrecognized setting. No declared setting with name: PORT
2020-02-28 13:48:23.020+0000 WARN Unrecognized setting. No declared setting with name: PORT.7474.TCP.PORT
2020-02-28 13:48:23.020+0000 WARN Unrecognized setting. No declared setting with name: PORT.7687.TCP.ADDR
2020-02-28 13:48:23.020+0000 WARN Unrecognized setting. No declared setting with name: PORT.6362.TCP.PROTO
2020-02-28 13:48:23.020+0000 WARN Unrecognized setting. No declared setting with name: SERVICE.PORT.6362TCP
2020-02-28 13:48:23.021+0000 WARN Unrecognized setting. No declared setting with name: PORT.6362.TCP
2020-02-28 13:48:23.021+0000 WARN Unrecognized setting. No declared setting with name: PORT.7687.TCP
2020-02-28 13:48:23.021+0000 WARN Unrecognized setting. No declared setting with name: SERVICE.PORT.7687TCP
2020-02-28 13:48:23.021+0000 WARN Unrecognized setting. No declared setting with name: SECRETS.PASSWORD
2020-02-28 13:48:23.021+0000 WARN Unrecognized setting. No declared setting with name: SERVICE.PORT.7474TCP
2020-02-28 13:48:23.021+0000 WARN Unrecognized setting. No declared setting with name: PORT.7474.TCP
2020-02-28 13:48:23.022+0000 WARN Unrecognized setting. No declared setting with name: SERVICE.PORT
2020-02-28 13:48:23.022+0000 WARN Unrecognized setting. No declared setting with name: PORT.6362.TCP.PORT
2020-02-28 13:48:23.023+0000 WARN Unrecognized setting. No declared setting with name: PORT.6362.TCP.ADDR
2020-02-28 13:48:23.023+0000 WARN Unrecognized setting. No declared setting with name: SERVICE.HOST
2020-02-28 13:48:23.061+0000 INFO ======== Neo4j 4.0.0 ========
2020-02-28 13:48:23.072+0000 INFO Starting...
2020-02-28 13:48:28.631+0000 INFO Resolved initial host 'neo4j-helm-neo4j.default.svc.cluster.local:5000' to [10.42.0.194:5000]
2020-02-28 13:48:29.576+0000 INFO Database 'system' is waiting for a total of 3 core members...
2020-02-28 13:48:33.635+0000 INFO Resolved initial host 'neo4j-helm-neo4j.default.svc.cluster.local:5000' to [10.42.0.194:5000]
2020-02-28 13:48:38.637+0000 INFO Resolved initial host 'neo4j-helm-neo4j.default.svc.cluster.local:5000' to [10.42.0.194:5000]
2020-02-28 13:48:39.638+0000 INFO Database 'system' is waiting for a total of 3 core members...

I also tried to read the logs from debug.log and got the following lines:

2020-02-28 13:52:36.092+0000 WARN [a.r.a.InboundHandshake$$anon$2] Dropping Handshake Request from [akka://cc-discovery-actor-system@neo4j-helm-neo4j-core-1.neo4j-helm-neo4j.default.svc.cluster.local:5000#-4381238615579183357] addressed to unknown local address [akka://cc-discovery-actor-system@10.42.0.194:5000]. Local address is [akka://cc-discovery-actor-system@neo4j-helm-neo4j-core-0.neo4j-helm-neo4j.default.svc.cluster.local:5000]. Check that the sending system uses the same address to contact recipient system as defined in the 'akka.remote.artery.canonical.hostname' of the recipient system. The name of the ActorSystem must also match.

Version of Helm and Kubernetes:

$ helm version

version.BuildInfo{Version:"v3.0.1", GitCommit:"7c22ef9ce89e0ebeb7125ba2ebf7d421f3e82ffa", GitTreeState:"clean", GoVersion:"go1.13.4"}

$kubectl version

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.1", GitCommit:"d224476cd0730baca2b6e357d144171ed74192d6", GitTreeState:"clean", BuildDate:"2020-01-15T15:50:38Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.4", GitCommit:"224be7bdce5a9dd0c2fd0d46b83865648e2fe0ba", GitTreeState:"clean", BuildDate:"2019-12-11T12:37:43Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Which chart: stable/neo4j

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.

[sinistersnare]

I do not think that this chart supports neo4j 4.x at the moment. #20942 says that they plan on adding support in a different ticket.