Inconsistent PVC naming between geoip PVC and sentry cleanup CronJob (claimName vs hardcoded name) #1980
Description
Issue submitter TODO list
- I've searched for an already existing issues here
Describe the bug (actual behavior)
In Sentry Helm chart, the PVC created for GeoIP and the PVC name expected by the sentry cleanup CronJob use different naming schemes.
File: charts/sentry/templates/geoip/pvc-geoip.yaml
Creates a PersistentVolumeClaim with a hardcoded name for GeoIP data.
File: charts/sentry/templates/sentry/cleanup/cronjob-sentry-cleanup.yaml
The cleanup CronJob uses:
claimName: {{ template "sentry.fullname" . }}-data
This leads to error in cleanup and other deployments.
k logs sentry-eks-sentry-cleanup-29435490-nv5zs
Error opening GeoIP database: /usr/share/GeoIP/GeoLite2-City.mmdb
Error opening GeoIP database: /usr/share/GeoIP/GeoLite2-City.mmdb
Error opening GeoIP database in Rust: /usr/share/GeoIP/GeoLite2-City.mmdb
Error opening GeoIP database in Rust: /usr/share/GeoIP/GeoLite2-City.mmdb
Expected behavior
All templates should consistently use {{ template "sentry.fullname" . }}-data (or another single, well-defined helper) for the data PVC name, or the cleanup CronJob should reference the same PVC name and helper used by the geoip PVC.
values.yaml
filestore:
filesystem:
persistence:
enabled: true
size: 10Gi
accessMode: ReadWriteMany
persistentWorkers: true
storageClass: "efs-standard"
Helm chart version
sentry v27.8.1
Steps to reproduce
when updated the above mentioned values.yaml file values along with sentry.cleanup.enabled=true,
in the launched sentry cleanup job pod logs, we could see mentioned error.
Screenshots
No response
Logs
Error opening GeoIP database: /usr/share/GeoIP/GeoLite2-City.mmdb
Error opening GeoIP database: /usr/share/GeoIP/GeoLite2-City.mmdb
Error opening GeoIP database in Rust: /usr/share/GeoIP/GeoLite2-City.mmdb
Error opening GeoIP database in Rust: /usr/share/GeoIP/GeoLite2-City.mmdb
Additional context
Proposed fix
Update pvc-geoip.yaml to use {{ template "sentry.fullname" . }}-data (or whatever is the canonical data PVC helper), or
Update cronjob-sentry-cleanup.yaml to reference the same PVC name helper used by the geoip PVC template, so the claimName matches the created PVC.