Charts: [stable/openldap] tls enabled return error

[brunowego]

Describe the bug

Not are running with SSL enabled. After install a error are showing in the logs.

Version of Helm and Kubernetes:
Client: v1.15.3
Server: v1.15.2

Which chart: Open LDAP

What happened:

kubectl logs $(kubectl get pod -l 'app=openldap' -o jsonpath='{.items[0].metadata.name}' -n openldap) -n openldap -f
*** CONTAINER_LOG_LEVEL = 3 (info)
*** Search service in CONTAINER_SERVICE_DIR = /container/service :
*** link /container/service/:ssl-tools/startup.sh to /container/run/startup/:ssl-tools
*** link /container/service/slapd/startup.sh to /container/run/startup/slapd
*** link /container/service/slapd/process.sh to /container/run/process/slapd/run
*** Set environment for startup files
*** Environment files will be proccessed in this order :
Caution: previously defined variables will not be overriden.
/container/environment/99-default/default.startup.yaml
/container/environment/99-default/default.yaml

To see how this files are processed and environment variables values,
run this container with '--loglevel debug'
*** Running /container/run/startup/:ssl-tools...
*** Running /container/run/startup/slapd...
Start OpenLDAP...
Waiting for OpenLDAP to start...
Add TLS config...
*** /container/run/startup/slapd failed with status 80

*** Killing all processes...

How to reproduce it:

kubectl create namespace openldap

kubectl create secret tls openldap.tls-secret \
  --cert='/etc/ssl/certs/example/ca.crt' \
  --key='/etc/ssl/certs/example/ca.key' \
  -n openldap

helm install stable/openldap \
  -n openldap \
  --namespace openldap \
  --set image.tag=1.2.5 \
  --set env.LDAP_ORGANISATION='Example Inc.' \
  --set env.LDAP_DOMAIN=example.com \
  --set tls.enabled=true \
  --set tls.secret=openldap.tls-secret

[Lunik]

Same here identical parameters

[jayceeb]

Any update on this? I am also hitting this problem

[Lunik]

I have done some investigations, it seems that the rolling update is broken.
Deleting the version then reinstalling the chart with the new version seems to work.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.