Directory /var/opt/jfrog/artifactory has bad permissions for user 'artifactory' about charts HOT 9 CLOSED

@marianteodorescu I had to do following to deploy Artifactory:

helm repo add ibm https://registry.bluemix.net/helm/ibm
helm repo add ibm-charts https://registry.bluemix.net/helm/ibm-charts

helm install ibm/ibmcloud-block-storage-plugin

kubectl get pod -n kube-system | grep block

kubectl get storageclasses | grep block

kubectl patch storageclass ibmc-block-bronze -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'

kubectl patch storageclass ibmc-file-bronze -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"false"}}}'

kubectl get storageclass

from charts.

Did you try upgrading over the failing deployment? This might be due to an already deployed postgresql that has a randomly generated password. You must extract it and pass it with --set postgresql.postgresPassword=${DB_PASSWORD}.
Extract the current password with

export DB_PASSWORD=$(kubectl get $(kubectl get secret -o name artifactory-postgresql) -o jsonpath="{.data.postgres-password}" | base64 --decode)

I guess we should improve documentation on this...

from charts.

Hi @marianteodorescu . What K8s are you deploying to?
Seems the PVC created uses a volume that does not have write permissions for others.
You can try passing --set artifactory.persistence.enabled=false to see it works without persistency.

from charts.

Hi @eldada . I am deploying to the IBM Cloud K8s. I will try reinstalling again with --set artifactory.persistence.enabled=false. Is there a way to modify the the volume and grant permission manually?

from charts.

I'm not familiar with IBM Cloud K8s, but I suspect that the default StorageClass is the root cause.
You can also create your own PV + PVC with the needed permissions and pass it to Artifactory with --set artifactory.persistence.existingClaim=PVC_NAME.
@jainishshah17 - do you have ideas about the IBM default StorageClass and permissions?

from charts.

I have tried starting it --set artifactory.persistence.enabled=false and it would not start, I got FATAL: password authentication failed for user "artifactory", I have attached the full log below.
logs-from-artifactory-in-artifactory-artifactory-0.txt

from charts.

It was a clean install, I used the helm delete --purge then I made sure that all pods and volumes were clean.

from charts.

@marianteodorescu did you clear PVC after helm delete --purge?

from charts.

Thank you, it works!

from charts.