Skip to content

Synchronise master with upstream #736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 14 commits into from
Jun 16, 2025
Merged

Conversation

github-actions[bot]
Copy link

This PR contains a snapshot of master from upstream master.

sdemircan and others added 14 commits May 19, 2025 14:38
Closes-Bug: #2088197
Change-Id: I3bebfb0946477458fcd84831d2aa661215e48844
This is required for OpenSearch upgrade to 3.x

Change-Id: I1f47d285cd6c17d1c92fbe4e6981420322ceee2b
Avoid using `drain` when only one RabbitMQ host is targeted, as it's meaningless
outside of clustered setups. Use `stop` for single-node, and `drain` otherwise.

Closes-Bug: #2111916
Change-Id: I0b9e97421c78fcb215cc203af12de50ee5cd794f
Our CI environment runs all services (including qemu, libvirt, etc.)
on a single node with only 8 GB RAM. The default MariaDB configuration
is too memory-heavy for such constrained resources.

This change introduces a mariadb-overrides.j2 file that limits key
memory-consuming options:

- max_connections = 300 (instead of 10000)
- innodb_buffer_pool_size = 1024M
- tmp_table_size / max_heap_table_size = 32M

These limits help avoid OOM kills during testing and prevent
unnecessary RAM consumption.

This change is CI-specific and does not impact kolla-ansible user
deployments.

Change-Id: I9a59b2f7c5dafdfeb147eb93d89039e98988049f
Change-Id: Ie3893b002bcc9150143060a229cefbad48600d46
Stop repeating the same code (actually 158 times).

Change-Id: I2fd04e6ed72f3702eb41fe5cf172f47a33e93bbd
Remove yamllint usage - it duplicates what reno lint/ansible-lint do.

Change-Id: If8ad229281b2dca565570d651065779c2c871528
Some queries (e.g. SET AUTOCOMMIT, ROLLBACK) may be executed before
schema is selected, causing them to be routed to hostgroup 0, which
does not exist if user using different `mariadb_default_shard_id`.
This change sets default_hostgroup (shard_id) for users to ensure
correct routing even when schema is not specified.

Also adjusts nova-cell user generation logic to include shard assignment,
so queries from nova_<cell> users are properly routed, even if schema is
not used directly.

This avoids silent misrouting and improves reliability in multi-shard
deployments.

Note: These errors are not visible in CI because
mariadb_default_shard_group_id = 0 and ProxySQL routes to hostgroup 0
by default when no routing rule matches.

Depends-On: https://review.opendev.org/c/openstack/kolla/+/951741
Closes-Bug: #2112339

Change-Id: I4f3380a83fa992c3413e82a4692c26a07b25d57f
This patch enables testing with a runtime virtualenv on Debian and Ubuntu
in CI jobs and without for RHEL derivatives.

Summary:
- Deployments on Debian/Ubuntu now test virtualenv creation logic.

Change-Id: I5d4c5d960441025da1fc1b6f197b03476b1be1a9
Change-Id: I7d45ba8687fca53505af771046fabc0186774acc
@github-actions github-actions bot added automated Automated action performed by GitHub Actions synchronisation labels Jun 16, 2025
@github-actions github-actions bot requested a review from a team as a code owner June 16, 2025 06:23
@github-actions github-actions bot added automated Automated action performed by GitHub Actions synchronisation labels Jun 16, 2025
@priteau priteau closed this Jun 16, 2025
@priteau priteau reopened this Jun 16, 2025
@priteau priteau merged commit 8aa212b into stackhpc/master Jun 16, 2025
4 checks passed
@priteau priteau deleted the upstream/master-2025-06-16 branch June 16, 2025 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated Automated action performed by GitHub Actions synchronisation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants