aboutsummaryrefslogtreecommitdiff
path: root/docker/openstack-base
diff options
context:
space:
mode:
authorMichal Arbet <michal.arbet@ultimum.io>2025-06-04 09:40:03 +0200
committerMichal Arbet <michal.arbet@ultimum.io>2025-06-04 10:24:54 +0200
commitb643e8f9fd3e9d8e881e112e53183db743f1e5d3 (patch)
tree3da2ff045d02c9c16bc0440db40380f087055f1f /docker/openstack-base
parent9a5315e9d250ca520a8bc38f67013e0b632de08e (diff)
downloadkolla-b643e8f9fd3e9d8e881e112e53183db743f1e5d3.tar.gz
kolla-b643e8f9fd3e9d8e881e112e53183db743f1e5d3.zip
Fix ProxySQL rule sanity check to support username-based routing
Kolla Ansible now generates ProxySQL query rules not only based on the schema name (schemaname), but also on the username. This is needed to properly route queries that are executed before a database schema is selected, such as `SET AUTOCOMMIT` or `ROLLBACK`. To support this, the ProxySQL config sanity check must correctly deduplicate rules based on both `schemaname` and `username`, and avoid false positives when both types are used simultaneously. This change adjusts the logic in `kolla_proxysql_config_sync` to: - recognize rules by key `schema:<schemaname>` or `user:<username>` - assign unique rule IDs only to truly distinct rules - log and skip exact duplicates with appropriate context This fix is required to support the Kolla Ansible patch below. Needed-By: https://review.opendev.org/c/openstack/kolla-ansible/+/951599 Change-Id: I99acd1984ee555a5b6c731e6ee460a33677060d0
Diffstat (limited to 'docker/openstack-base')
0 files changed, 0 insertions, 0 deletions