Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

[cetic/fadi] specific and hard-coded release name #41

Open
fzalila opened this issue Jun 28, 2021 · 3 comments
Open

[cetic/fadi] specific and hard-coded release name #41

fzalila opened this issue Jun 28, 2021 · 3 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@fzalila
Copy link
Contributor

fzalila commented Jun 28, 2021

Describe the bug
The current values.yaml requires that the release must be named fadi.
This install does not work with my-release release name.

Version of Helm and Kubernetes:

How to reproduce it (as minimally and precisely as possible):
Install fadi as explained here and try to access to a any service.
The access (admin/password1) will not work because the server is not found.
t=2021-06-28T13:21:50+0000 lvl=eror msg="Error while trying to authenticate user" logger=context userId=0 orgId=0 uname= error="LDAP Result Code 200 \"Network Error\": dial tcp: lookup fadi-openldap on 10.96.0.10:53: no such host" remote_addr=172.17.0.1 t=2021-06-28T13:21:50+0000 lvl=eror msg="Request Completed" logger=context userId=0 orgId=0 uname= method=POST path=/login status=500 remote_addr=172.17.0.1 time_ms=124 size=53 referer=http://192.168.99.254:32676/login

A suggestion to resolve issue:
Multiple services start withfadi- must be updated like {{ .Release.Name }}-

@fzalila fzalila added the bug Something isn't working label Jun 28, 2021
@fzalila fzalila changed the title [cetic/fadi] issue title [cetic/fadi] specific and hard-coded release name Jun 28, 2021
@AyadiAmen
Copy link
Contributor

I tried to change fadi- to {{ .Release.Name }}- in the values.yaml file but it doesn't work, some services ( jupyterHub, zabbix, airflow ) don't accept {{ .Release.Name }} in the values and postgresql gives the error

 LOG:  authentication option not in name=value format: .Release.Name
2021-09-28 07:52:16.119 UTC [1] CONTEXT:  line 1 of configuration file "/var/lib/postgresql/conf/pg_hba.conf"
2021-09-28 07:52:16.119 UTC [1] LOG:  authentication option not in name=value format: .Release.Name
2021-09-28 07:52:16.119 UTC [1] CONTEXT:  line 2 of configuration file "/var/lib/postgresql/conf/pg_hba.conf"
2021-09-28 07:52:16.119 UTC [1] FATAL:  could not load pg_hba.conf
2021-09-28 07:52:16.119 UTC [1] LOG:  database system is shut down

so i suggest we keep the default release-name fadi.

@banzo
Copy link
Contributor

banzo commented Sep 28, 2021

Do you know why?

@AyadiAmen
Copy link
Contributor

I think it works on the resources files ( Deployment, configmap ... ) but not in the values file. there are others who faced the same issue :
https://stackoverflow.com/questions/59222503/use-release-name-in-values-yaml-in-helm , helm/helm#3558
but they didn't find a solution yet.

@fzalila fzalila added the enhancement New feature or request label Apr 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants