Synchronise 2024.1 with upstream #630
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Volumes with a mode specifier were causing the container to fail to start with the error: "Wrong format of volume". ironic-dnsmasq was one services affected by this issue, but you could also hit this issue when using the volume customisation variables. Closes-Bug: #2054834 Change-Id: I848bd2838a17756f1c71b07befe1e3d966f5b6c2 (cherry picked from commit 9b3428c)
These were added in I20e65a6771ebeee462a3aaaabaa5f0596bdd0581 but not used in the final version of the changeset. Change-Id: I4fca47e16e87db8b655ff5571fba568ef4edb95c (cherry picked from commit 8709db2)
If not using --limit, each host runs the setup module for itself only. Hosts should be able to fail at this point and drop out of execution without affecting others. However, there is a bug that causes us to hit the --limit code path for an unreachable host and therefore become subject to its limitations. These include the use of delegated fact gathering, and failing the delegated host when the delegating host is unreachable. This change fixes the issue by reversing the order of two tasks in the gather-facts.yml playbook, ensuring that we check the ansible_play_batch variable before any hosts have had a chance to fail. Change-Id: I4b1da63e8f0cc2774f1a9ab2e0414746108f7e12 Closes-Bug: #2041859 (cherry picked from commit 7f01f47)
This reverts commit 5b431f0. Reason for revert: the any_errors_fatal play parameter is not templated by Ansible (tested up to ansible-core 2.15.9). This behaviour is demonstrated in [1]. This means that "{{ kolla_ansible_setup_any_errors_fatal }}" is always interpreted as 'true', regardless of the value of kolla_ansible_setup_any_errors_fatal. This is particularly bad because the default value of kolla_ansible_setup_any_errors_fatal is false. We now have gather_facts_max_fail_percentage which can be set to 0 to provide the same functionality. [1] https://github.com/markgoddard/ansible-experiments/tree/master/15-fatal-errors Change-Id: I2e0ea49701b5900eae26434bcdb6b1bb44507ee7 (cherry picked from commit 9cebdb5)
When using dnsmasq as a DHCP server, unless you use the noping option (and that is not recommended), the NET_RAW capabilty is required so that dnsmasq can send ICMP packets. These are used to check an address is not currently in use[1]. Docker enables this capability by default. Podman runs containers with a minimal set of capabilities[3]. [1] https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2019q1/012840.html [2] https://docs.docker.com/engine/containers/run/#runtime-privilege-and-linux-capabilities [3] https://github.com/rhatdan/common/blob/f39f2a3f8c7680b9e456b9d235570e511807d6c6/docs/containers.conf.5.md?plain=1#L84-L101 Closes-Bug: #2055282 Change-Id: Ib3a1313df680d91c7f008063937ca7d37e82f690 (cherry picked from commit f61fafa)
We don't use dots in the image name Change-Id: I29172448c14a1ca9a5fa23abe701366f875959e0 (cherry picked from commit 07312e6)
Change-Id: I7934bda26a134fe38a63716f9878a27b4f3819ce (cherry picked from commit f8807b4)
Given we bump the RabbitMQ version each release, there is a manual upgrade to an intermediary RabbitMQ version needed before a skip-level upgrade can be performed. Change-Id: Id8a5ebe19a50ebdc59d12667889472c803b8d7c8
Closes-bug: #2077511 Change-Id: Icd15e8d04771cf50bc704f0c40006a8ac0aeb3ef (cherry picked from commit 28ed506)
Change-Id: I972608b81edb2f5c118cf9a2f734f83ea399a849 (cherry picked from commit e4bfdd8)
… into stable/2024.1
Since [1] Neutron puts requested-chassis entry with a name taken from the agent, which results in FQDN-based name on FQDN-based deployments. It does not match what we set in hostname in OVS. [1]: I4e3c001dd3bb37b86fda8b9495a3c5178c3e736d Closes-Bug: #2080552 Change-Id: I3ae03aa2e09bc445f0f5a95a43bf210f06685cc1 (cherry picked from commit 35e59ef)
priteau
approved these changes
Oct 11, 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 2024.1 from upstream stable/2024.1.