[cetic/nifi] Nifi Pods Status is Init:0/1 indefinitely

cetic / helm-nifi

Helm Chart for Apache Nifi

Apache License 2.0

215 stars 225 forks source link

[cetic/nifi] Nifi Pods Status is Init:0/1 indefinitely #144

Closed Lavanya2102 closed 3 years ago

Lavanya2102 commented 3 years ago

I am trying to install Nifi on the Kubernetes cluster using cetic/helm-nifi. But once I installed nifi, the pods are not running but are in "status: Init:0/1" indefinitely. Screenshot (9) Then I checked the logs of the containers and the init container zookeeper has been having a problem. It shows bad address.

Due to this issue, the pods aren't running and I'm not able to access Nifi UI. How do I debug this?

Version of helm: 3.5.4 Version of Kubernetes Cluster: 1.21.0

nuttybrewer commented 3 years ago

kubectl describe pod my-release-nifi-0

In the events it'll show you why it's failing. Usually it's because it can't mount something or a claim for a persistent volume is broken.

Lavanya2102 commented 3 years ago

I did check the events and it says none. But the storage class was not set, now I set it on all zookeeper nodes. All of them are running, but the nifi node still says init 0/1. what might be the reason?

deebify commented 3 years ago

I have the same issue with k8s on GCP. Nifi pods in Init state. Have you solved it?

Lavanya2102 commented 3 years ago

No, i haven't.

banzo commented 3 years ago

Please provide more information. The full output of nuttybrewer's command for example.

Note: I can not reproduce the issue on Minikube, it takes 45 minutes to install with my home internet connection but it gets there in the end.