persistentvolumeclaim "nextcloud-nextcloud-nextcloud" not found.

Hi! I have an issue that can not fix, I activate persistence and allways get on nextcloud-setup-apps pod:

0/4 nodes are available: 4 persistentvolumeclaim "nextcloud-nextcloud-nextcloud" not found.

I run the chart with:

helm install --wait nextcloud nextcloud-onlyoffice/nextcloud-onlyoffice --values nextcloud-onlyoffice.yaml -n nextcloud

Any advice is wellcome,

Thank you in advance!!

changed milestone to %0.8.2

added 1 deleted label

Hi @juanpablofava, can you please provide the nextcloud-onlyoffice.yaml values file (please make sure to take out any secrets you have in there). With this we could try to reproduce the issue.

Information about your nodes and default storage class would be welcome:

kubectl get node
kubectl get storageclasses.storage.k8s.io

assigned to @juanpablofava

I think there is an issue with templating somewhere specifically when you give the helmrelease the name "nextcloud". Could you try running the same command, but with a different name (for example nc)?

helm install --wait nc nextcloud-onlyoffice/nextcloud-onlyoffice --values nextcloud-onlyoffice.yaml -n nextcloud

This solve the issue! Thank you @maarten and @varac for your time. So, helmrelease can not be named "nextcloud"

You're welcome. It's a pretty weird and stupid limitation, because everybody's going to try this. We'll at least document the limitation in the readme. There are also ways of solving this nowadays, although we would limit the helm version to one newer than 3.7. But the nextcloud subchart already contains that limitation, so I guess that's fine.

removed 1 deleted label

added QA label

mentioned in merge request !157 (merged)

Todo:

• document the limitation in the readme

Can't we also just reject release names containing 'nextcloud' using helm, i.e. in a helper function ?

I don't think I know what a helper function is. How would that work?

I at least added the documentation in !169 (merged), but I propose we keep this issue open (but with a later milestone) to really fix the problem. We should use the template function from the child chart to determine the pvc name instead of hardcoding it inside this chart.

I don't think I know what a helper function is. How would that work?

I was referring to a template function we could use in templates/_helpers.tpl

OK, it was actually super easy to fix. The fix is in !169 (merged)

I propose we merge !157 (merged) first, though, so we can properly test the fix in the pipeline.

added User feedback label

created branch 1026-persistentvolumeclaim-nextcloud-nextcloud-nextcloud-not-found to address this issue

mentioned in merge request !169 (merged)

mentioned in commit f917e0a2

closed with merge request !169 (merged)