[Question][Module Name] Question title . Migration scripts needed

[wrldcup2003-sudo]

Question

Installed devlake on my RHOS cluster in a K8 namespace. I see all pods running. Lake, UI and mysql. PVC is bound to my storage class. Did not use Helm. Rather used 'oc apply -f' individual YAML for lake, ui, statefulset, mysql service, cluster service and route. I can login to Mysql. i see db and all tables. When i try to access UI, i get database migration scripts needed. I am not able to proceed even if i try to use CURL Post to the path. it keeps coming back with same error. When i checked migration history table it is blank. I am using v1.0.2 and MySQL8. Not sure what is going on, I tried deleting everything and reinstalling. Same issue. Note that i am using http and not set TLS since I am just starting

Screenshots

If applicable, add screenshots to help explain.

Additional context

Add any other context here.

[dosubot[bot]]

Hi @wrldcup2003-sudo! I'm Dosu and I’m helping the incubator-devlake team.

The "database migration scripts needed" message means DevLake hasn't run its required database migrations yet, which is why your migration_history table is blank. Normally, the UI provides a button to trigger migration, which calls the /proceed-db-migration API endpoint. If you get the same error even when using CURL to this endpoint, it suggests the backend service is stuck waiting for migration confirmation or isn't able to execute migrations.

DevLake's migrator loads migration scripts and tracks their execution in the migration_history table. If the table is empty, all migrations are pending and must be applied for the UI to work properly. The backend blocks access until migrations are confirmed and executed via the API or UI button. You can review the migration logic and API endpoint in the backend code for more details:

• Migrator implementation
• API migration endpoint
• UI migration prompt

Since you deployed manually (not with Helm), double-check that the lake backend pod has the right permissions and environment variables to connect to MySQL and execute migrations. Also, check the lake pod logs for any migration errors or permission issues. If the pod can't write to the database or is missing config, migrations won't run.

Recent migration script changes have improved MySQL compatibility, so if you're using v1.0.2, you should be covered, but make sure your deployment matches the expected setup for DevLake. If you continue to see the migration prompt and can't proceed, focus on the lake pod logs and MySQL connectivity/configuration.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[klesh]

Can you share the devlake container logs for diagnosis?

[github-actions[bot]]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.