Continuous crashloopbackoff of the jira container about helm-charts

[stevehipwell]

Hi @MrAmbiG it'd be useful to know a bit more information about your setup such as K8s version and provider as well as a bit of information about what you're trying to achieve?

For Format 1 you are specifying that you wish to use the bundled PostgreSQL chart. Based on the error I suspect that your version of K8s is does not have the APIs to support the bundled chart (PostgreSQL 10). If this is the case the approach in Format 2 would be correct (or you could raise an issue with Bitnami to get their charts to support different API versions).

For Format 2 you are specifying that you will be providing the PostgreSQL instance to run Jira on, so you will need to provide the host for that instance to the chart or it will not work.

As a final bit of information, the bundled PostgreSQL instance is provided for convenience but I'd recommend using a separate instance as using the bundled one ties you in to a shared lifecycle. Also Atlassian does not keep the PostgreSQL compatibility for Jira (and confluence) very up to date and as I don't use the bundled PostgreSQL I only upgrade this when both Jira & Confluence support the same version of PostgreSQL, which currently limits us to PostgreSQL v10.

[MrAmbiG]

@stevehipwell
appreciate your response.
the version of kubernetes is 1.17.4. I Redacted the host. I will try again with some more additional settings and update you soon. So I even tried with a different storageclass and a new bitnami/postgresql helm chart.

pvc

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: jirapvc
  namespace: jira
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 99Gi

The pvc is shown as bound. Using nfs provisioner helm chart from helm/stable. The same storageclass is working with many of our apps flawlessly.

jira yaml.

persistence:
  enabled: true
  accessMode: ReadWriteMany
  storageClass: nfsserver
  existingClaim: jirapvc
psql:
  host: postgresql.postgresql.svc.cluster.local
  port: 5432
  database: jiradb
  username: jiraadmin
  password:
    secret: jirapsql
    key: password

The error message

INFO:root:Generating /etc/container_id from template container_id.j2
INFO:root:Generating /opt/atlassian/jira/conf/server.xml from template server.xml.j2
INFO:root:Generating /opt/atlassian/jira/atlassian-jira/WEB-INF/classes/seraph-config.xml from template seraph-config.xml.j2
INFO:root:/var/atlassian/application-data/jira/dbconfig.xml exists; skipping.
Traceback (most recent call last):
  File "/entrypoint.py", line 26, in <module>
    start_app(f'{JIRA_INSTALL_DIR}/bin/start-jira.sh -fg', JIRA_HOME, name='Jira')
  File "/entrypoint_helpers.py", line 85, in start_app
    set_perms(home_dir, env['run_user'], env['run_group'], 0o700)
  File "/entrypoint_helpers.py", line 34, in set_perms
    shutil.chown(path, user=user, group=group)
  File "/usr/lib/python3.8/shutil.py", line 1296, in chown
    os.chown(path, _user, _group)
PermissionError: [Errno 1] Operation not permitted: '/var/atlassian/application-data/jira'

$ kl -n jira get pvc
NAME      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
jirapvc   Bound    pvc-022225a2-bc88-438e-805f-fe30a03bd3e5   99Gi       RWX            nfs58          23m

$ kl -n postgresql get all
NAME                          READY   STATUS    RESTARTS   AGE
pod/postgresql-postgresql-0   1/1     Running   0          38m

NAME                          TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
service/postgresql            ClusterIP   11.47.172.15   <none>        5432/TCP   38m
service/postgresql-headless   ClusterIP   None            <none>        5432/TCP   38m

NAME                                     READY   AGE
statefulset.apps/postgresql-postgresql   1/1     38m

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.