Created attachment 912761 [details] [R|W separation][admin] Write and read are separate, there is a select action occurred in master db when user remove build. Description of problem: as summary. Version-Release number of selected component (if applicable): v3.8.9-1 on test server. How reproducible: 100% Steps to Reproduce: 1.Admin login tcms, click 'admin-builds' to enter build list page. 2.Choose a build, then click link on build_id to enter build detail page. https://tcms-test.app.eng.nay.redhat.com/admin/management/testbuild/ 2.Delete the build. 3.Inspect the sql executed in master db. Actual results: There is a select sql occurred in master db, like: SELECT `test_case_runs`.`case_run_id`, `test_case_runs`.`assignee_id`, `test_case_runs`.`tested_by_id`, `test_case_runs`.`case_text_version`, `test_case_runs`.`running_date`, `test_case_runs`.`close_date`, `test_case_runs`.`notes`, `test_case_runs`.`iscurrent`, `test_case_runs`.`sortkey`, `test_case_runs`.`run_id`, `test_case_runs`.`case_id`, `test_case_runs`.`case_run_status_id`, `test_case_runs`.`build_id`, `test_case_runs`.`environment_id` FROM `test_case_runs` WHERE `test_case_runs`.`build_id` IN (6451) Expected results: The select sql occurred in slave db. Additional info:
all of delete operations in ADMIN menu will be done in the same database, and can not separate into different databases. These features is supported by Django framework, we can not modify the source code, so this bug will not be fixed. And it will be considered as the correct behavior.
Confirm with dev, can not modify the source code, so close the issue.