Sorry if this has been asked before, but I could not find it.  If is is a known issue then my search skills are weak.

While deploying via helm as described on Documentation > Installation & operations guide > Installation > Helm Chart i have not been able to completely deploy OpenProject.

The seeder pod gets stuck initializing:

pod/openproject-memcached-99bc94c55-86hw9         1/1     Running      0             66s
pod/openproject-postgresql-0                                        1/1     Running      0             65s
pod/openproject-seeder-20240317184502-hj7c2          0/1     Init:0/1        0             65s
pod/openproject-web-7d779dbf4d-5ckpk                      0/1     Init:Error     1 (19s ago)   66s
pod/openproject-worker-default-6bcc7b685b-px8kl       0/1     Init:0/1        2 (19s ago)   66s

Name:             openproject-seeder-20240317184502-hj7c2
Priority:         0
Service Account:  default
Labels:           app.kubernetes.io/instance=openproject
                 app.kubernetes.io/managed-by=Helm
                 app.kubernetes.io/name=openproject
                 app.kubernetes.io/version=13
                 batch.kubernetes.io/controller-uid=cb8e2f46-e543-492e-97f8-8904332c3a4d
                 batch.kubernetes.io/job-name=openproject-seeder-20240317184502
                 controller-uid=cb8e2f46-e543-492e-97f8-8904332c3a4d
                 helm.sh/chart=openproject-5.1.0
                 job-name=openproject-seeder-20240317184502
                 openproject/process=seeder
Annotations:      cni.projectcalico.org/containerID: 369820cccbc180478e5d1352a1c03a9d61bbace090b915d34daa0b709d3f2103
Status:           Pending

kubectl logs -n openproject pods/openproject-seeder-20240317184502-hj7c2 
Defaulted container "seeder" out of: seeder, check-db-ready (init)
Error from server (BadRequest): container "seeder" in pod "openproject-seeder-20240317184502-hj7c2" is waiting to start: PodInitializing

On premise k8s cluster major components:
kube-vip v0.7.1 (static pod yaml install)
kubeadm v1.29.2 
calico v3.26.4 (operator install)
metalLB v0.14.3 (yaml install)
traefik v2.11.0 (helm install)
trident 24.02.0 (operator install)

Am I missing something simple?  Any suggestions?  Any help is appreciated!

Thanks!

I ended up reworking my values.yaml file and found that I had a worker node that its file system running read-only.  This seems to have fixed the issue.