Jira Deployment Error using OpenShift - missing access to /opt/atlassian/jira

[Stephan Krause]

I am using the jira-software image from Atlassian (docker hub). I ran it on Openshift 3.11.

My deplyoment-file is pretty simple:

apiVersion: v1
kind: DeploymentConfig
metadata:
name: jira-software
labels:
app: jira-software
spec:
replicas: 1
template:
metadata:
generateName: jira-software
labels:
app: jira-software
type: backend
spec:
containers:
- image: "xxx.xxx:51015/test/atlassian/jira-software"
name: jira-software
ports:
- containerPort: 8080
protocol: TCP
env:
- name: SET_PERMISSIONS
value: "false"
resources:
limits:
cpu: 500m
memory: 1024Mi
livenessProbe:
failureThreshold: 3
httpGet:
path: /status
port: 8080
protocol: HTTP
initialDelaySeconds: 60
periodSeconds: 600
successThreshold: 1
timeoutSeconds: 30
readinessProbe:
failureThreshold: 10
httpGet:
path: /status
port: 8080
protocol: HTTP
periodSeconds: 60
successThreshold: 1
timeoutSeconds: 10

During deployment, I got the following error:

INFO:root:Generating /etc/container_id from template container_id.j2
WARNING:root:Container not started as root. Bootstrapping skipped for '/etc/container_id'
INFO:root:Generating /opt/atlassian/jira/conf/server.xml from template server.xml.j2
WARNING:root:Container not started as root. Bootstrapping skipped for '/opt/atlassian/jira/conf/server.xml'
INFO:root:Generating /var/atlassian/application-data/jira/dbconfig.xml from template dbconfig.xml.j2
WARNING:root:Container not started as root. Bootstrapping skipped for '/var/atlassian/application-data/jira/dbconfig.xml'
INFO:root:Running Jira with command '/bin/sh', arguments ['/bin/sh', '-c', '/opt/atlassian/jira/bin/start-jira.sh -fg']
executing as current user

`sMMMMMMMMMMMMMM+
MMMMMMMMMMMMMM
:sdMMMMMMMMMMM
MMMMMM
`sMMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sMMMMMMMMMMM MMMMM
MMMMMM `UOJ
`sMMMMMMMMMMMMM+ MMMMMM
MMMMMMMMMMMMMM +MMMMM
:sdMMMMMMMMMM MMMMM
MMMMMM `UOJ
MMMMMM
+MMMMM
MMMMM
`UOJ

Atlassian Jira
Version : 8.7.1

If you encounter issues starting or stopping Jira, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-087/Troubleshooting+installation

Using JIRA_HOME: /var/atlassian/application-data/jira

Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
OpenJDK 64-Bit Server VM warning: Cannot open file /opt/atlassian/jira/logs/atlassian-jira-gc-2020-02-12_14-09-36.log due to Permission denied

java.util.logging.ErrorManager: 4
java.io.FileNotFoundException: /opt/atlassian/jira/logs/catalina.2020-02-12.log (Permission denied)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at org.apache.juli.FileHandler.openWriter(FileHandler.java:504)

I tried "SET_PERMISSIONS=true" and SET_PERMISSIONS=false, but this makes no difference.

It seems that the container does not have the correct rights (root rights) to adjust the file system (directory /opt/atlassian/jira) for user jira:jira during startup ?!

here's my output of the terminal:

$ ls -al /opt/atlassian/jira
total 156
drwxr-xr-x. 13 root root 4096 Feb 11 05:29 .
drwxr-xr-x. 1 root root 17 Feb 11 05:29 ..
drwxr-xr-x. 18 root root 4096 Feb 11 05:29 atlassian-jira
drwxr-xr-x. 3 root root 4096 Feb 11 05:29 bin
-rw-r--r--. 1 root root 20101 Jun 4 2019 BUILDING.txt
drwxr-xr-x. 2 root root 238 Feb 11 05:29 conf
-rw-r--r--. 1 root root 5543 Jun 4 2019 CONTRIBUTING.md
drwxr-xr-x. 2 root root 41 Feb 11 05:29 external-source
drwxr-xr-x. 2 root root 4096 Feb 11 05:29 lib
drwxr-xr-x. 2 root root 69632 Feb 11 05:29 licenses
drwxr-xr-x. 2 jira jira 6 Jun 4 2019 logs
-rw-r--r--. 1 root root 1777 Jun 4 2019 NOTICE
-rw-r--r--. 1 root root 5662 Feb 10 13:45 README.html
-rw-r--r--. 1 root root 3334 Jun 4 2019 README.md
-rw-r--r--. 1 root root 3512 Feb 10 13:45 README.txt
drwxr-xr-x. 2 jira jira 48 Feb 11 05:29 temp
drwxr-xr-x. 2 root root 61 Feb 11 05:29 tomcat-docs
drwxr-xr-x. 2 root root 6 Feb 10 14:44 webapps

Any ideas?

I suspect that the container needs (more or higher) privileges (root?). 

[Gonchik Tsymzhitov]

Container is include already all rights I thought. 

you need to use user jira if you running process under jira user. 

[Gonchik Tsymzhitov]

Therefore don't forget to change ownership via 

chown -R. and check other rights