)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"a3363d6e1b835bfd0b6431a3c2c5aeda41bab5e5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"a07165d9_dbd744ec","updated":"2022-08-03 10:17:12.000000000","message":"This is failing because batch mode seems to be having an effect on the MySQL backend and is resulting a \"create new table, rename tables, drop old table\" pattern, which should be only needed for SQLite (which doesn\u0027t support the ALTER statement). This doesn\u0027t align with my understanding on batch mode, which I thought would only affect the SQLite backend. I need to investigate this.","commit_id":"2a3c7cc7411568001c50786f7a18facd92cea9ea"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"ecd66636e129b403b57be7b131755c29e8450771","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"02f7895e_06b00538","in_reply_to":"a07165d9_dbd744ec","updated":"2023-03-15 12:08:08.000000000","message":"Turned out this wasn\u0027t true. I was just (incorrectly) blocking batch mode operations 🙈","commit_id":"2a3c7cc7411568001c50786f7a18facd92cea9ea"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"10b3433f6fce019de9df5a0d9982654c9fd87d84","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"42402855_5e22fd35","updated":"2023-03-15 12:23:06.000000000","message":"The \u0027TestModelsSyncPostgreSQL.test_models_sync\u0027 test in \u0027keystone.tests.unit.common.sql.test_upgrades\u0027 is failing with the following message.\n\n    AssertionError: Models and migration scripts aren\u0027t in sync:                                                                                                                                                                                                                                                                                                                                                                            \n    [ ( \u0027add_constraint\u0027,                                                                                                                                                                                                                                                                                                                                                                                                                       \n        UniqueConstraint(Column(\u0027project_id\u0027, NullType(), table\u003d\u003cproject_tag\u003e), Column(\u0027name\u0027, NullType(), table\u003d\u003cproject_tag\u003e)))]\n\nI don\u0027t know why though. The \u0027TestModelsSyncMySQL\u0027 and \u0027TestModelsSyncSQLite\u0027 equivalents are working fine, as you\u0027d expect given the fact that the unique constraint exists in both the model [1] and the initial migration [2]. Maybe it\u0027s the use of unicode? idk\n\n[1] https://github.com/openstack/keystone/blob/c08d97672d/keystone/resource/backends/sql_model.py#L121\n[2] https://github.com/openstack/keystone/blob/c08d97672d/keystone/common/sql/migrations/versions/27e647c0fad4_initial_version.py#L345","commit_id":"709d54c9d3fcc97e4cc590d2edb52babbb29d759"}]}