Skip to content
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

Synchronise master with upstream #679

Merged
merged 21 commits into from
Feb 3, 2025
Merged

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Feb 3, 2025

This PR contains a snapshot of master from upstream master.

mnasiadka and others added 21 commits January 9, 2025 07:05
We're often observing:
2025-01-08 19:27:29 MySQL_Monitor.cpp:2314:monitor_galera_thread(): [ERROR] Timeout on Galera health check for 192.0.2.3:3306 after 1001ms. If the server is overload, increase mysql-monitor_galera_healthcheck_timeout.

Change-Id: I5c63192ab78e0c50a05d72abd754e99e7cf83976
Closes-Bug: #2093335
Change-Id: I7061aa65673a3b8d2e95e43f124587546e21b715
The Oslo.messaging project implemented a nice feature called Queue
Manager. This means that instead of using random queue names in
RabbitMQ, it uses queue names composed of hostname, process-name and a
counter. For proper functioning, the code stores some informations in
/dev/shm. This is needed to avoid creating queues with the same name.
We'd otherwise hit this where multiple services run under mod_wsgi, or
with services such as Magnum just within a single container as it needs
to create multiple "reply" queues.

This patch mounts /dev/shm in containers where oslo_messaging is used.

This is enabled when ``om_enable_queue_manager`` is set to ``True``.
Queue Manager will be supported in a follow-up patch.

Change-Id: Ib85ce252374fae917d329e1824800a288c6bc9f1
Update GLOBAL_VARIABLE_MAP to include OPENSTACK_RELEASE which is the
release name as returned by openstackdocstheme.ext._get_series_name().

Also mark 2023.1 (Antelope) as unmaintained and remove yoga and zed.

Change-Id: I2d8393856249d2f999acb1a22424f6ef200f6e2d
Fix URL by switching from KOLLA_OPENSTACK_RELEASE to OPENSTACK_RELEASE
introduced in [1]. This replaces `master` by `latest` in the URL.

The link was also not rendered correctly because of a syntax error.

[1] https://review.opendev.org/c/openstack/kolla-ansible/+/937440

Change-Id: Ie8c90ff5c8682aec07e851909bc820cba7602bec
This option was deleted from Nova in the 2024.1 release [1].

[1] https://review.opendev.org/c/openstack/nova/+/903339

Change-Id: I26827322199365a4466f180a1abba50ca6a1515f
Disable CI jobs as well - those have been failing for some time
and there's no volunteer to fix them.

Change-Id: I13dc1822f2b803b5a4dbc99cc63ab05ce6016613
Closes-Bug: #2095607
Change-Id: Ie1372ce307011c6f2560c7f1fcd520187810fab8
(cherry picked from commit fec66c1)
(cherry picked from commit 1845fb8)
(cherry picked from commit 81c2d07)
This allows operators quickly diagnose all containers across
all hosts by running kolla-ansible check. It returns a list
of containers that are missing, not running or in unhealthy
state for each OpenStack service.

Change-Id: I36119ccdeb264aa3de928ec2254d6ff4cc955bfb
Implements: blueprint check-containers
Co-Authored-By: Roman Krček <[email protected]>
Needed to set log_file because logs ended up with following name:
<frozen importlib._bootstrap>.log

Change-Id: I706adef8efbd44e6d9f82f67f5a3cdb529f02fff
The Oslo.messaging project implemented a nice feature
called Queue Manager. This means that instead of using
random queue names in RabbitMQ, it uses queue names composed
of hostname, process-name and some integer. For proper
functioning, the code using lockutils from oslo_concurrency
and it's failing if lock_path is not set.

This patch simply set lock_path of oslo_concurrency for
services which can potentionally use Queue Manager.

This is enabled when ``om_enable_queue_manager`` is set to ``True``.
Queue Manager will be supported in a follow-up patch.

Change-Id: Ided3b2bce03ea11fb34820fc40b4a3d694b8b44c
@priteau priteau merged commit 890d3b7 into stackhpc/master Feb 3, 2025
3 checks passed
@priteau priteau deleted the upstream/master-2025-02-03 branch February 3, 2025 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants