Skip to content
This repository has been archived by the owner on Aug 25, 2021. It is now read-only.

When using 'extraVolumes' to mount secrets, Consul errors on start with 'data_dir is empty' #26

Closed
thisLambo opened this issue Oct 8, 2018 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@thisLambo
Copy link

When using the extraVolumes configuration option in the values.yaml, the Helm chart fails to start Consul correctly with the error data_dir is empty.

All secrets exist and when tested by telling the chart by setting them to load: false Consul starts correctly.

Upon further investigation the issue appears to be a missing \ in the loop that adds the extra config directories for the statefulset and the daemonset:

https://github.com/hashicorp/consul-helm/blob/master/templates/server-statefulset.yaml#L91
https://github.com/hashicorp/consul-helm/blob/master/templates/client-daemonset.yaml#L77

I would submit a Pull Request but the company I work for currently doesn't have a policy in place for contributing to open source software.

@thisLambo thisLambo changed the title When using extraVolumes to mount secrets, Consul errors on start with 'data_dir is empty' When using 'extraVolumes' to mount secrets, Consul errors on start with 'data_dir is empty' Oct 8, 2018
@adilyse adilyse added the bug Something isn't working label Oct 16, 2018
@adilyse adilyse self-assigned this Oct 16, 2018
@adilyse
Copy link
Contributor

adilyse commented Oct 16, 2018

Good catch! The fix is now merged, so it will be available in the next release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants