Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Volume mount name for log storage is incorrect #60

Closed
dintorf opened this issue Sep 9, 2024 · 1 comment · Fixed by #70
Closed

[Bug]: Volume mount name for log storage is incorrect #60

dintorf opened this issue Sep 9, 2024 · 1 comment · Fixed by #70
Assignees

Comments

@dintorf
Copy link

dintorf commented Sep 9, 2024

Contact Details

No response

What happened?

The volume mount name for the log storage claim is incorrect. It points to the lib storage claim.

https://github.com/memgraph/helm-charts/blob/main/charts/memgraph/templates/statefulset.yaml#L181-L184

          {{- if .Values.persistentVolumeClaim.createLogStorage }}
            - name: {{ include "memgraph.fullname" . }}-lib-storage # here is the incorrect line
              mountPath: /var/log/memgraph
          {{- end }}

Should be changed to

          {{- if .Values.persistentVolumeClaim.createLogStorage }}
            - name: {{ include "memgraph.fullname" . }}-log-storage # should be log-storage here instead of lib-storage
              mountPath: /var/log/memgraph
          {{- end }}

Chart type

Standalone

Chart version

0.1.x

Environment

My environment is not listed

Relevant log output

No response

@dintorf dintorf changed the title [BUG] Volume mount name for log storage is incorrect [Bug] Volume mount name for log storage is incorrect Sep 9, 2024
@dintorf dintorf changed the title [Bug] Volume mount name for log storage is incorrect [Bug]: Volume mount name for log storage is incorrect Sep 9, 2024
@antejavor
Copy link
Collaborator

Hi @dintorf, thanks for letting me know about this, we will fix it! 🚀

@antejavor antejavor self-assigned this Sep 10, 2024
@antejavor antejavor linked a pull request Nov 7, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants