NFS-FIXER pod starts before PVC created

Hi,

I ran into something rather unusual when using nfsPermissionFixer:

helm install -n $n jira --values values.yaml data-center-helm-charts/jira --debug

I noticed that the nfs-fixer would time out waiting for the condition

install.go:172: [debug] Original chart version: ""
install.go:189: [debug] CHART PATH: /root/data-center-helm-charts/src/main/charts/jira
client.go:268: [debug] Starting delete for "jira-nfs-fixer" Job
client.go:297: [debug] jobs.batch "jira-nfs-fixer" not found
client.go:122: [debug] creating 1 resource(s)
client.go:477: [debug] Watching for changes to Job jira-nfs-fixer with timeout of 5m0s
client.go:505: [debug] Add/Modify event for jira-nfs-fixer: ADDED
client.go:544: [debug] jira-nfs-fixer: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:505: [debug] Add/Modify event for jira-nfs-fixer: MODIFIED
client.go:544: [debug] jira-nfs-fixer: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: failed pre-install: timed out waiting for the condition
helm.go:81: [debug] failed pre-install: timed out waiting for the condition

After scratching my head until I was bald, I noticed I could alter the pre-install value in nfs-permission-fixer.yaml

Before:

  annotations:
    "helm.sh/hook": pre-install
    "helm.sh/hook-delete-policy": "before-hook-creation,hook-succeeded"

After:

  annotations:
    "helm.sh/hook": post-install
    "helm.sh/hook-delete-policy": "before-hook-creation,hook-succeeded"

This appears to have resolved one of my problems.

The second problem was the actual command run by nfs-fixer; if others are using an EFS backed PVC, then I found the following command in your values.yaml doesn’t prevent Jira from starting:

command: "chown 2001: /shared-home"

Hopefully, this may be of help to others encountering the same!

[bianchi2]

{{- if .Values.volumes.sharedHome.persistentVolumeClaim.create }}

shared home PVC template has this, and it’s weird Helm did not create it first for you. I’ll check it in a local cluster once again.

[pbruski]

Well, as long as keep it configurable, we can make it a part of the python startup script on the image.