gitea getting Init:CrashLoopBackOff state
Hi all,
I am trying to get EMCO up on kubernetes. I got the following:
- helm 3.8.2
- Ubuntu 18.04
- kubernetes 1.21
- calico 3.21.4
- emco 22.09 (but I tested with 22.06 and 22.03 too)
And I am getting the following:
vagrant@rio-amazonas-jauarana:~$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
calico-system calico-kube-controllers-666bb9949-dhxjp 1/1 Running 0 77m
calico-system calico-node-88pvj 1/1 Running 0 77m
calico-system calico-typha-6f5d9896fd-7wbq9 1/1 Running 0 77m
emco emco-ca-certs-7cf4fdbbd9-mzc9w 1/1 Running 2 3m45s
emco emco-clm-85955cc448-hck6z 1/1 Running 2 3m45s
emco emco-dcm-785d9f87d-vgd5t 1/1 Running 2 3m45s
emco emco-dtc-7c4bc7b646-wjh45 1/1 Running 2 3m45s
emco emco-emco-mongo-0 1/1 Running 0 3m45s
emco emco-etcd-0 1/1 Running 0 3m45s
emco emco-fluentd-0 1/1 Running 0 3m45s
emco emco-fluentd-r5lk9 1/1 Running 3 3m45s
emco emco-gac-6c844b4b67-8x5nv 1/1 Running 2 3m45s
emco emco-gitea-0 0/1 Init:CrashLoopBackOff 2 3m45s
emco emco-hpa-ac-65d6f47c6b-5228h 1/1 Running 1 3m45s
emco emco-hpa-plc-b6496998c-7dzb7 1/1 Running 1 3m45s
emco emco-its-685bdcc89c-skhzc 1/1 Running 1 3m45s
emco emco-memcached-85844b566-bpj8d 1/1 Running 0 3m45s
emco emco-ncm-57d98757bf-r299x 1/1 Running 1 3m45s
emco emco-nps-6f7469d489-5khrs 1/1 Running 1 3m45s
emco emco-orchestrator-54c69bdc6b-gl97b 1/1 Running 1 3m44s
emco emco-ovnaction-68bb754766-z4q4p 1/1 Running 1 3m44s
emco emco-postgresql-0 1/1 Running 0 3m45s
emco emco-rsync-685898c787-27t4f 1/1 Running 1 3m44s
emco emco-sds-9bf7bd5c5-fcxjn 1/1 Running 1 3m44s
emco emco-sfc-f8d847d55-cwpfz 1/1 Running 1 3m44s
emco emco-sfcclient-7b8bf5fc5b-rs2c2 1/1 Running 1 3m43s
emco emco-swc-59697d79b8-xjjgn 1/1 Running 1 3m43s
emco emco-tac-c4445697f-hzbn8 1/1 Running 1 3m43s
emco emco-workflowmgr-7845d8dc87-8mxnb 1/1 Running 1 3m43s
kube-system coredns-558bd4d5db-qkzbg 1/1 Running 0 85m
kube-system coredns-558bd4d5db-wj44q 1/1 Running 0 85m
kube-system etcd-rio-amazonas-jauarana 1/1 Running 0 86m
kube-system kube-apiserver-rio-amazonas-jauarana 1/1 Running 1 86m
kube-system kube-controller-manager-rio-amazonas-jauarana 1/1 Running 0 86m
kube-system kube-proxy-jbf5t 1/1 Running 0 85m
kube-system kube-scheduler-rio-amazonas-jauarana 1/1 Running 0 86m
tigera-operator tigera-operator-c4b9549c7-rxzhd 1/1 Running 0 77m
Am I doing something wrong? As can be seen, gitea is not getting up. I waitted for hours and the problem persist.
To install emco i am executing:
helm install emco -n emco emco/emco --set global.db.emcoPassword=****** --set global.db.rootPassword=****** --set global.contextdb.rootPassword=****** --set global.emcoTag=22.09
checking the logs:
vagrant@rio-amazonas-jauarana:~$ kubectl logs emco-gitea-0 --all-containers -n emco
+ chown 1000:1000 /data
+ mkdir -p /data/git/.ssh
+ chmod -R 700 /data/git/.ssh
+ '[' '!' -d /data/gitea ']'
+ mkdir -p /tmp/gitea
+ chown 1000:1000 /tmp/gitea
+ chmod ug+rwx /tmp/gitea
...Initial secrets generated
Processing inlines...
repository
+ 'ROOT'
metrics
+ 'ENABLED'
database
+ 'DB_TYPE'
+ 'HOST'
+ 'NAME'
+ 'PASSWD'
+ 'USER'
cache
+ 'ADAPTER'
+ 'ENABLED'
+ 'HOST'
[ini root]
server
+ 'APP_DATA_PATH'
+ 'DOMAIN'
+ 'ENABLE_PPROF'
+ 'HTTP_PORT'
+ 'PROTOCOL'
+ 'ROOT_URL'
+ 'SSH_DOMAIN'
+ 'SSH_LISTEN_PORT'
+ 'SSH_PORT'
security
+ 'INSTALL_LOCK'
Reloading preset envs...
+ 'ENV_TO_INI__REPOSITORY__ENABLE_PUSH_CREATE_ORG'
+ 'ENV_TO_INI__REPOSITORY__ENABLE_PUSH_CREATE_USER'
+ 'ENV_TO_INI__REPOSITORY__ONLY_ALLOW_PUSH_IF_GITEA_ENVIRONMENT_SET'
=== All configuration sources loaded ===
An app.ini file already exists. To prevent overwriting secret keys, these settings are dropped and remain unchanged:
- security.INTERNAL_TOKEN
- security.SECRET_KEY
- oauth2.JWT_SECRET
- server.LFS_JWT_SECRET
==== BEGIN GITEA CONFIGURATION ====
2022/12/28 15:07:09 cmd/migrate.go:34:runMigrate() [I] AppPath: /usr/local/bin/gitea
2022/12/28 15:07:09 cmd/migrate.go:35:runMigrate() [I] AppWorkPath: /data
2022/12/28 15:07:09 cmd/migrate.go:36:runMigrate() [I] Custom path: /data/gitea
2022/12/28 15:07:09 cmd/migrate.go:37:runMigrate() [I] Log path: /data/log
2022/12/28 15:07:09 cmd/migrate.go:38:runMigrate() [I] Configuration file: /data/gitea/conf/app.ini
2022/12/28 15:07:09 ...e/cli@v1.22.9/app.go:277:Run() [I] PING DATABASE postgres
2022/12/28 15:07:14 cmd/migrate.go:41:runMigrate() [F] Failed to initialize ORM engine: dial tcp: lookup emco-postgresql.emco.svc.cluster.local: Try again
Gitea migrate might fail due to database connection...This init-container will try again in a few seconds
Error from server (BadRequest): container "gitea" in pod "emco-gitea-0" is waiting to start: PodInitializing
Checking pv:
vagrant@rio-amazonas-jauarana:~$ kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
data-emco-etcd-0 1Gi RWX Retain Terminating emco/data-emco-postgresql-0 21h
emco-emco-mongo-data 1Gi RWX Retain Bound emco/emco-emco-mongo-data emco-emco-mongo-data 19h
gitea-pv-postgress-data 1Gi RWX Retain Terminating emco/data-emco-etcd-0 21h
gitea-pv-volume-data 2Gi RWX Retain Terminating emco/data-emco-gitea-0 21h
vagrant@rio-amazonas-jauarana:~$ kubectl get pvc -A
NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
emco data-emco-etcd-0 Bound gitea-pv-postgress-data 1Gi RWX 21h
emco data-emco-gitea-0 Bound gitea-pv-volume-data 2Gi RWX 21h
emco data-emco-postgresql-0 Bound data-emco-etcd-0 1Gi RWX 21h
emco emco-emco-mongo-data Bound emco-emco-mongo-data 1Gi RWX emco-emco-mongo-data 19h
vagrant@rio-amazonas-jauarana:~$ kubectl get pv -A
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
data-emco-etcd-0 1Gi RWX Retain Terminating emco/data-emco-postgresql-0 21h
emco-emco-mongo-data 1Gi RWX Retain Bound emco/emco-emco-mongo-data emco-emco-mongo-data 19h
gitea-pv-postgress-data 1Gi RWX Retain Terminating emco/data-emco-etcd-0 21h
gitea-pv-volume-data 2Gi RWX Retain Terminating emco/data-emco-gitea-0