Open waza-ari opened 7 months ago
Ditching the mysql init job entirely seems rather drastic, so I'm not sure that's the actual solution to your problem. Can you please provide us with the logs from the mysql init job to understand why it's failing? (be careful not to share production credentials from these logs)
Bug description
When trying to run tutor with an external MYSQL database, we're setting
RUN_MYSQL
tofalse
which prevents the pod to be created. It does however still create the MySQL init job, which is doing nothing else than creating the database for openedx.We'd prefer not to specify root credentials here, but instead specify credentials directly using:
Use case would be a centrally operated database, in our environment using a database operator within k8s.
How to reproduce When trying to bring up the platform, it will fail with the following error message:
Either
RUN_MYSQL
should also prevent the job from being created, or we may want to introduce another variable to achieve that.Environment Mac OS Sonoma 14.2.1 Tutor version
tutor, version 17.0.2