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 2023.1 with upstream #643
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
As our CI is ipv6 only and using cirros for tests. Therefore we need to set force_config_drive = true. Change-Id: I07058a4b30d0de1aaf8e82656024c5f6a99b290b (cherry picked from commit 11685a8)
When kolla VIP address is changed the cell0 database connection is now updated to the new address. Closes-bug: #1915302 Change-Id: I35be54efb5aaa230702d0cebaae04f1e64c3bca3 Signed-off-by: Roman Krček <[email protected]> (cherry picked from commit ab6eb98)
The variable kolla_same_external_internal_vip in group_vars/all.yml was set to true or false depending on the jinja2 equality operator - == - which only checks if two objects are the same. This is problematic because IPs can be the same but have different string representations, e.g. leading zeroes in some octets, but still repesent the same instance of an IP. Example: 192.168.1.1 and 192.168.001.001 are the same. Fix this, by using the ansible.utils.ipaddr() jinja2 filter instead to increase robustness. Closes-Bug: #2076889 Introduced-By: https://review.opendev.org/c/openstack/kolla/+/285005 Signed-off-by: Sven Kieske <[email protected]> Change-Id: Ied43b9d0c4b33bb514d367f3f99c2e30e104d139 (cherry picked from commit a5f0e16)
check if generated prometheus config is valid via promtool. This should help prevent bugs like: https://bugs.launchpad.net/kolla-ansible/+bug/2076660 prior art: haproxy config validation: https://review.opendev.org/c/openstack/kolla-ansible/+/922840 also add some basic documentation for the `kolla-ansible validate-config` command. Signed-off-by: Sven Kieske <[email protected]> Change-Id: Ief90861b2c422e0e6c2dd9cb605c94e86c0f2ba1 (cherry picked from commit e38ca5c)
Followup on Ib69fc0017b3bfbc8da4dfd4301710fbf88be661a. This change adds the ability to provide the NTP (time source) server for multiple DHCP ranges in the Ironic Inspector DHCP server. Change-Id: I4bbfef3a391b8582ae73cbe06138715b43584dec Signed-off-by: Maksim Malchuk <[email protected]> (cherry picked from commit 5a37bd6)
The zed series has migrated to unmaintained status, stop running upgrade testing. Change-Id: I54909f90ac11d43b46053fff6b0f48f5542dec35
As version-check.yml is added to deploy.yml, we must make sure the tasks are only run when the rabbitmq container exists. Change-Id: Iaa31bae739110094affb5e402ed9ac40b153ac3d (cherry picked from commit f5ad782)
Closes-Bug: #2086171 Change-Id: I4001ddad198dcf40f71e9196e126cc78a19d1437 (cherry picked from commit fa54e69)
Existing container was out of date and did not work for the db restore example. Updates to a rocky-9 example. Change-Id: I5f57467a18d3e42e0c71826cc3a7740110162af7 (cherry picked from commit 3564f9d)
This patch removes the nova_libvirt_secret container volume because it is a complete antipattern, and during testing, I found that it causes problems. When it was necessary to copy libvirt secrets from /etc/kolla/nova-libvirt/secrets, the container logs reported that the resource is busy - precisely because it was a mounted container volume. This, of course, is unnecessary because the secrets are copied to the kolla host in /etc/kolla/nova-libvirt/secrets. NOTE: Module name in this backported patch was changed from kolla_container to kolla_docker and removed unsupported container_engine for this version. Closes-Bug: #2073678 Change-Id: I715a6a95f9d32d62a8199727ddbaddd0dd7baa2d (cherry picked from commit 82a642e)
This patch resolves an issue where ProxySQL could not bind due to incorrectly formatted IPv6 addresses in the `mysql_ifaces` configuration. The kolla's `put_address_in_context` filter is now used, ensuring the addresses are properly enclosed in square brackets for correct binding. Closes-Bug: #2081106 Change-Id: Ic166b8d9a500023c8d23ec9fee03b28b268b26e7 (cherry picked from commit 12eeccd) (cherry picked from commit 99e1495)
…er" into stable/2023.1
priteau
approved these changes
Dec 2, 2024
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 2023.1 from upstream stable/2023.1.