You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using sentry helm chart
I'm on sentry helm release: version: 26.9.1
appVersion: 24.9.0
On trying to upgrade to sentry helm release 26.10.0, app version - 24.10.0
snuba migrations failed probably because in this release clickhouse version is bumped from appVersion: "23.3.19.32" to appVersion: "23.8.16.16"
and sentry-snuba-migrate pod log says:
{"module": "snuba.migrations.connect", "event": "Snuba has only been tested on Clickhouse versions up to 23.8.11.29 (sentry-clickhouse:9000 - 24.5.1.1763). Higher versions might not be supported.", "severity": "warning", "timestamp": "2025-01-21T05:15:16.418161Z"}
Steps to Reproduce
Running 26.9.1 helm chart version
Update to 26.10.0 helm chart version
Expected Result
migration completes successfully and helm upgrade is successful
Actual Result
migrations failed
so still stuck on helm chart version 26.9.1
The text was updated successfully, but these errors were encountered:
Environment
Using sentry helm chart
I'm on sentry helm release: version: 26.9.1
appVersion: 24.9.0
On trying to upgrade to sentry helm release 26.10.0, app version - 24.10.0
snuba migrations failed probably because in this release clickhouse version is bumped from appVersion: "23.3.19.32" to appVersion: "23.8.16.16"
and sentry-snuba-migrate pod log says:
{"module": "snuba.migrations.connect", "event": "Snuba has only been tested on Clickhouse versions up to 23.8.11.29 (sentry-clickhouse:9000 - 24.5.1.1763). Higher versions might not be supported.", "severity": "warning", "timestamp": "2025-01-21T05:15:16.418161Z"}
Steps to Reproduce
Running 26.9.1 helm chart version
Update to 26.10.0 helm chart version
Expected Result
migration completes successfully and helm upgrade is successful
Actual Result
migrations failed
so still stuck on helm chart version 26.9.1
The text was updated successfully, but these errors were encountered: