openstack/kolla-ansible.git/ansible/destroy.yml, branch stable/2026.1 Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1 2023-12-05T10:49:42+00:00 Support Ansible max_fail_percentage 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 Give plays in the playbooks a name 2016-12-05T15:40:56+00:00 Christian Berendt berendt@betacloud-solutions.de 2016-11-30T15:23:36+00:00 urn:sha1:4c39f2e9fc08d29a1acdee80f8130c46680db33c Change-Id: I44c2668a8ebb6dd3201a6eb4e47284871380e6d7 Change cleanup to destroy as cleanup is a misnomer 2016-08-08T17:37:10+00:00 Duane DeCapite ddecapit@cisco.com 2016-08-05T18:01:38+00:00 urn:sha1:6d45786d5992a62af08ee4bed31094b6834daf41 The cleanup command in the external API is a misnomer and should be called destroy. Change-Id: I083e80699e09bb24266ce1bf549772a5de92a49e Closes-Bug: 1610364