forked from openstack/kolla-ansible
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
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
approved these changes
Feb 3, 2025
Alex-Welsh
approved these changes
Feb 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains a snapshot of master from upstream master.