-
Notifications
You must be signed in to change notification settings - Fork 535
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
Cannot startup dev lake when using Microsoft azure mysql flexible server due to missing columns #6958
Closed
2 of 3 tasks
Comments
Thanks for reporting the problem. @d4x1 is working on it. |
4 tasks
@michaelawarren It has taken effect in v0.20.0-beta4 version |
I'm still seeing this issue in version 0.20.0-beta4
|
ahh i see the link is for 0.21.0-beta4 not 20. I'll try that. |
confirming 0.21.0-beta4 does work. Thank you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
What happened
I'm trying to run Dev lake in an azure kubernetes cluster using azure flexible server mysql (my sql version 8.0) I'm using helm 0.19.0 (also tried 0.21.0-beta3). When i start up it prompts me to do a db migration. when i do that i get the following error. Error is specific to 0.19.0. I get a different but similar error on 0.21.0-beta3). I'm starting with a fresh install.
slack link to where question was asked and bug report asked for https://devlake-io.slack.com/archives/C03APJ20VM4/p1707867572707049
What do you expect to happen
For the service to start up and work properly.
How to reproduce
created an azure mysql flexible server via azure (must start with at least 2 cpus)
disable require_secure_transport and sql_generate_invisible_primary_key
deploy dev lake via helm to kube cluster
attempt to go to the devlake-ui
it will prompt for migration
select ok
error will occur
(i pulled error from logs)
Anything else
No response
Version
v0.19.0 and v0.21.0-beta3
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: