Auth migration issues

[kumar-tiger]

Issues Policy acknowledgement

• [X] I have read and agree to submit bug reports in accordance with the issues policy

Where did you encounter this bug?

Local machine

Willingness to contribute

No. I cannot contribute a bug fix at this time.

MLflow version

• Client: 2.10.0
• Tracking server: 2.10.0

System information

• OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
• Python version: python 3.9
• yarn version, if running the dev UI:

Describe the problem

HI, The migration of basic auth app will not work in case of mysql database. In sqllite db everything works fine. https://github.com/mlflow/mlflow/blob/master/mlflow/server/auth/db/migrations/versions/8606fa83a998_initial_migration.py#L33 https://github.com/mlflow/mlflow/blob/master/mlflow/server/auth/db/migrations/versions/8606fa83a998_initial_migration.py#L43 both have the name as fk_user_id so one of the name has to be change. Thanks

Tracking information

Code to reproduce issue

You can reproduce the issue by providing the database uri in basic_auth.ini file. then try to run the mlflow server.

Stack trace

Other info / logs

What component(s) does this bug affect?

• [ ] area/artifacts: Artifact stores and artifact logging
• [ ] area/build: Build and test infrastructure for MLflow
• [ ] area/deployments: MLflow Deployments client APIs, server, and third-party Deployments integrations
• [ ] area/docs: MLflow documentation pages
• [ ] area/examples: Example code
• [ ] area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
• [ ] area/models: MLmodel format, model serialization/deserialization, flavors
• [ ] area/recipes: Recipes, Recipe APIs, Recipe configs, Recipe Templates
• [ ] area/projects: MLproject format, project running backends
• [ ] area/scoring: MLflow Model server, model deployment tools, Spark UDFs
• [X] area/server-infra: MLflow Tracking server backend
• [ ] area/tracking: Tracking Service, tracking client APIs, autologging

What interface(s) does this bug affect?

• [ ] area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
• [ ] area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
• [X] area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
• [ ] area/windows: Windows support

What language(s) does this bug affect?

• [ ] language/r: R APIs and clients
• [ ] language/java: Java APIs and clients
• [ ] language/new: Proposals for new client languages

What integration(s) does this bug affect?

• [ ] integrations/azure: Azure and Azure ML integrations
• [ ] integrations/sagemaker: SageMaker integrations
• [ ] integrations/databricks: Databricks integrations

[BenWilson2]

Hi @kumar-tiger thanks for letting us know about this limitation. We'll likely need to create a migration script for other DBs and to update the initial table creation for MySQL. We'll work on this. cc @gabrielfu - any thoughts here?

[github-actions[bot]]

@mlflow/mlflow-team Please assign a maintainer and start triaging this issue.

[hadaney]

Duplicate of https://github.com/mlflow/mlflow/issues/9642

[robsonyeg]

I got same error when using Postgres as the backend database. Can Postgres be fixed too?