Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1 2026-03-19T12:17:03+00:00 2026-03-19T12:17:03+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-12-12T08:37:56+00:00 urn:sha1:21013949cdae545dbb797d149d7e4bcfa1378ea7 Also add all failed roles into ignore and these will be removed in subsequent patches Change-Id: Ifa6f2725cfa93cb14d72daf27448bd58f186acfd Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 2025-11-28T09:06:26+00:00 Michal Nasiadka mnasiadka@gmail.com 2025-11-12T14:24:01+00:00 urn:sha1:78f3c2b5de0470c0b1d350d0865663bb6f17f49e Normalize quotes and some other easy fixes done by ansible-lint --fix Also drop etc from excludes and ignore comment check in etc/kolla/globals.yml Pinning to ansible-lint<25.11.0 because 25.11.1 is breaking without any messages Change-Id: I7dee3866191cef84cd12b1816cdab0a02380ec7f Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com> 2025-02-05T23:15:53+00:00 Mark Goddard mark@stackhpc.com 2024-01-26T14:27:33+00:00 urn:sha1:94b4adae2f0f9ed85e4dc3ffd56ff6c9ef13d6a3 When Kolla Ansible is executed with a '--limit' argument, the scope of an operation is limited to the hosts in the limit. For example: kolla-ansible deploy --limit control Due to the nature of configuring clustered software services, there are cases where we need to know information about other hosts. Most often this is related to their hostname or network addresses. To make this work, Kolla Ansible gathers facts for hosts outside of the limit using delegated fact gathering [1]. By default, Kolla Ansible gathers facts for all hosts. Because delegated facts are gathered serially in batches by the active hosts, this can take a long time when there are not many hosts in the limit. This change makes it possible to reduce the set of hosts eligible for delegated fact gathering by setting 'kolla_ansible_delegate_facts_hosts' to a list of hosts. [1] https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_delegation.html#delegating-facts Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/899615 Change-Id: Id0bda00b81b5bc6a9a870e231335c33d9828e95f 2024-08-23T13:52:21+00:00 Zuul zuul@review.opendev.org 2024-08-23T13:52:21+00:00 urn:sha1:c5a941dc91c80f0e70da61c509e1e6642e170eac 2024-08-22T10:24:42+00:00 Zuul zuul@review.opendev.org 2024-08-22T10:24:42+00:00 urn:sha1:a8bf891ba9e00384627aff4924bfa907bf5d19b1 2024-08-21T11:22:43+00:00 Zuul zuul@review.opendev.org 2024-08-21T11:22:43+00:00 urn:sha1:3a6b9f3d9fc668c51024fab67e66967909db45ee 2024-08-21T11:22:37+00:00 Zuul zuul@review.opendev.org 2024-08-21T11:22:37+00:00 urn:sha1:5fddabaf55dd301e123aa434dc6ccfda53b982e4 2024-05-16T10:32:47+00:00 Mark Goddard mark@stackhpc.com 2024-02-29T10:48:40+00:00 urn:sha1:9cebdb5d9eb46b5ae28a52ef86e5bb50342c3648 This reverts commit 5b431f0f7f932293362a01703673ee05d0a5bd8d. 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 2024-03-08T14:36:40+00:00 Mark mark@stackhpc.com 2024-03-08T14:33:55+00:00 urn:sha1:0d238e479b74ca618daefd73ad913b4664f2ce7a Previously, during fact gathering when using the '--limit' argument if a host inside the limit fails to gather facts, this would cause another host to fail during delegated fact gathering. This is because the ansible_facts variable would not be populated for the host. This change fixes the issue by avoiding delegated fact gathering for hosts inside the limit. Partial-Bug: #2041860 Change-Id: I8e321469089f0eb80420b788b51e6d028c7fef4d 2023-12-05T10:49:42+00:00 Mark Goddard mark@stackhpc.com 2021-08-16T16:03:22+00:00 urn:sha1:af6e1ca4fd3366c1ae936d225b2835e95a4191fc This allows us to continue execution until a certain proportion of hosts to fail. This can be useful at scale, where failures are common, and restarting a deployment is time-consuming. The default max failure percentage is 100, keeping the default behaviour. A global max failure percentage may be set via kolla_max_fail_percentage, and individual services may define a max failure percentage via <service>_max_fail_percentage. Note that all hosts in the inventory must be reachable for fact gathering, even those not included in a --limit. Closes-Bug: #1833737 Change-Id: I808474a75c0f0e8b539dc0421374b06cea44be4f