Closed Uikola closed 1 month ago
Two out of Four Neo4j Instances failed to start after host reboot
$ kubectl get pods --all-namespaces | grep -v Running
NAMESPACE NAME READY STATUS RESTARTS AGE
context-pink pink-neo4j-0 0/1 Pending 0 23h
context-xxx xxx-neo4j-0 0/1 Pending 0 23h
Both pods encountered the same error.
Warning FailedScheduling 15m (x210 over 17h) default-scheduler 0/1 nodes are available: persistentvolumeclaim "neo4j-plugins" not found. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
last events in namespace
$ kubectl -n context-xxx get events
LAST SEEN TYPE REASON OBJECT MESSAGE
117s Normal WaitForPodScheduled persistentvolumeclaim/data-xxx-neo4j-0 waiting for pod xxx-neo4j-0 to be scheduled
22m Warning FailedScheduling pod/xxx-neo4j-0 0/1 nodes are available: persistentvolumeclaim "neo4j-plugins" not found. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
For some reason, there is no managed PVC resource for the neo4j-plugin:
$ kubectl get ns | grep -i context-
context-cyan Active 23h
context-pink Active 23h
context-xxx Active 23h
$ kubectl get managed | grep -i PersistentVolumeClaim
object.kubernetes.crossplane.io/cyan-neo4j-plugin-pvc PersistentVolumeClaim default True True 23h
doesn't reproduce
After the cluster deployment, purple-neo4j-0 hangs in Pending