[bitnami/jupyterhub] chart externalDatabase Error: UPGRADE FAILED: template

alekseytivonchik commented 9 months ago

Name and Version

bitnami/jupyterhub 4.0.2 (appVersion)

What architecture are you using?

amd64

What steps will reproduce the bug?

Open values.yaml

Set:

postgresql:
enabled: false
...
externalDatabase:
host: "postgresql.postgresql.svc.cluster.local"

Run: helm upgrade --install jupyterhub -n jupyter -f values.yaml .

Get error:

Error: UPGRADE FAILED: template: jupyterhub/templates/hub/deployment.yaml:82:20: executing "jupyterhub/templates/hub/deployment.yaml" at <include "common.images.image" (dict "imageRoot" .Values.postgresql.image "global" .Values.global)>: error calling include: template: jupyterhub/charts/common/templates/_images.tpl:12:31: executing "common.images.image" at <.imageRoot.registry>: nil pointer evaluating interface {}.registry

Are you using any custom parameters or values?

values.yaml customization

What is the expected behavior?

Success upgrade/install application

alekseytivonchik commented 8 months ago

Hi! Any ideas how to fix this?

fevisera commented 8 months ago

Hi @alekseytivonchik,

Thank you for bringing this issue to our attention. It appears to be the same as the one reported at https://github.com/bitnami/charts/issues/22983.

I have reproduced the issue by executing the following command:

$ helm install jupyterhub bitnami/jupyterhub --set postgresql.enabled=false

The installation failed with the following error:

Error: INSTALLATION FAILED: template: jupyterhub/templates/hub/deployment.yaml:82:20: executing "jupyterhub/templates/hub/deployment.yaml" at <include "common.images.image" (dict "imageRoot" .Values.postgresql.image "global" .Values.global)>: error calling include: template: jupyterhub/charts/common/templates/_images.tpl:12:31: executing "common.images.image" at <.imageRoot.registry>: nil pointer evaluating interface {}.registry

It appears that there might be an issue with the template when PostgreSQL is deactivated.

I will create an internal task to address this issue. Unfortunately, I am unable to provide an estimated time for the implementation of the fix at this moment.

If you have any additional findings or insights you would like to share, please feel free to do so.

Thanks again.

carrodher commented 8 months ago

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Expan75 commented 5 months ago

Hey ya! Also ran into this when reusing an existing database. Any update on potential fixes? @carrodher

Cheers,

javsalgar commented 5 months ago

Hi,

I'm afraid it is still in our backlog. As soon as there are updates on our side, we will update the ticket.

Kratemis commented 3 months ago

We are also affected by this problem. Do you think there would be an estimated date for its resolution?

bitnami / charts