tinglink opened a new issue, #16063: URL: https://github.com/apache/dolphinscheduler/issues/16063
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened When there are multiple tenants in the dolphinscheduler.t_ds_tenant table in v3.1.8, the binding relationship between admin and default tenant is not updated when upgrading to v3.2.1. Cause admin login to return. the tenant of the current login user is not specified. ### What you expected to happen To resolve the issue where the admin user is not associated with the default tenant after upgrading DolphinScheduler from v3.1.8 to v3.2.1, you indeed need to ensure that the admin user is properly associated with the default tenant. ``` UPDATE `t_ds_user` SET `tenant_id` = '-1' WHERE (`user_name` = 'admin') AND (`tenant_id` = '0'); ``` ### How to reproduce 1. Create multiple tenants in DS v3.1.8; 2. Upgrade DS from v3.1.8 to v3.2.1; 3. After the upgrade is complete, exit the current login and log in again. ### Anything else _No response_ ### Version 3.2.x ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
