-
Notifications
You must be signed in to change notification settings - Fork 291
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
Error when updating to v1.3.48 with django migration script #3222
Comments
Can confirm experiencing the same issue when updating, having to stick on 1.3.43 currently |
Still here 4 minor releases later
|
# What this PR does Fixes bd migration ## Which issue(s) this PR fixes Closes #3222 ## Checklist - [ ] Unit, integration, and e2e (if applicable) tests updated - [x] Documentation added (or `pr:no public docs` PR label added if not required) - [x] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not required)
👋 thanks for reporting this, a fix for this was added in #3260. Keep an eye out for the next release which should come out (hopefully) before the end of the week |
thanks 👍 |
hi there, a fix for this was included in v1.3.53 (just released). Feel free to open a separate issue if you're still running into this. |
What went wrong?
Hello!
When updating the oncall-engine deployement to v1.3.48, I get this error trace on the django database migrations job
command : python manage.py migrate
I think this is due to this PR : #3103
Grafana OnCall Version
v1.3.48
Product Area
Other
Grafana OnCall Platform?
Kubernetes
User's Browser?
No response
Anything else to add?
No response
The text was updated successfully, but these errors were encountered: