nautobot pod hangs in Init state

[finchr]

Hi, I'm attempting to install nautobot using helmfile and the deploy is stuck in the Init phase:

$ kubectl -n nautobot get all
NAME                                           READY   STATUS     RESTARTS        AGE
pod/nautobot-celery-beat-b7b595dbf-s9667       1/1     Running    4 (4m45s ago)   5m52s
pod/nautobot-celery-default-7cdcf6bdbf-k8292   1/1     Running    2 (5m37s ago)   5m52s
pod/nautobot-default-6868bb76dd-htt5r          0/1     Init:0/2   0               5m52s

NAME                       TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
service/nautobot-default   ClusterIP   172.20.162.83   <none>        443/TCP,80/TCP   5m53s

NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/nautobot-celery-beat      1/1     1            1           5m53s
deployment.apps/nautobot-celery-default   1/1     1            1           5m53s
deployment.apps/nautobot-default          0/1     1            0           5m53s

NAME                                                 DESIRED   CURRENT   READY   AGE
replicaset.apps/nautobot-celery-beat-b7b595dbf       1         1         1       5m54s
replicaset.apps/nautobot-celery-default-7cdcf6bdbf   1         1         1       5m54s
replicaset.apps/nautobot-default-6868bb76dd          1         1         0       5m54s

The logs from the pod end with the following logs.txt

Sending installation metrics...
Installation metrics are disabled by INSTALLATION_METRICS_ENABLED setting, skipping.

Refreshing _content_type cache
CONTENT_TYPE_CACHE_TIMEOUT is set to 0; skipping cache refresh

Any idea what is going on? I've attached the full log file.

[finchr]

FYI, this appears to be a version issue, I downgraded to 2.0.2 from 2.0.5 and the everything started:

kubectl -n nautobot get all

NAME                                           READY   STATUS    RESTARTS        AGE
pod/nautobot-celery-beat-695b9bd65f-9jd74      1/1     Running   2 (4m23s ago)   4m33s
pod/nautobot-celery-default-744fcc7b4f-sz6sz   1/1     Running   0               4m33s
pod/nautobot-default-f57cfd66d-rtjmr           1/1     Running   0               4m33s

NAME                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
service/nautobot-default   ClusterIP   172.20.147.218   <none>        443/TCP,80/TCP   4m33s

NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/nautobot-celery-beat      1/1     1            1           4m34s
deployment.apps/nautobot-celery-default   1/1     1            1           4m34s
deployment.apps/nautobot-default          1/1     1            1           4m34s

NAME                                                 DESIRED   CURRENT   READY   AGE
replicaset.apps/nautobot-celery-beat-695b9bd65f      1         1         1       4m34s
replicaset.apps/nautobot-celery-default-744fcc7b4f   1         1         1       4m34s
replicaset.apps/nautobot-default-f57cfd66d           1         1         1       4m34s

[ubajze]

I guess this is no longer relevant. If you find similar issues in the future, fell free to open a new issue.