kayobe/ansible/time.yml
Mark Goddard 6c54ce4d3b Introduce max fail percentage to playbooks
This allows us to continue execution until a certain proportion of hosts
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
kayobe_max_fail_percentage, and individual playbooks may define a max
failure percentage via <playbook>_max_fail_percentage.

Related Kolla Ansible patch:
https://review.opendev.org/c/openstack/kolla-ansible/+/805598

Change-Id: Ib81c72b63be5765cca664c38141ffc769640cf07
2024-06-03 16:24:29 +00:00

42 lines
972 B
YAML

---
- name: Ensure timezone is configured
hosts: seed-hypervisor:seed:overcloud:infra-vms
max_fail_percentage: >-
{{ time_max_fail_percentage |
default(host_configure_max_fail_percentage) |
default(kayobe_max_fail_percentage) |
default(100) }}
tags:
- timezone
tasks:
- import_role:
name: stackhpc.timezone
become: True
- name: Ensure ntp group exists
hosts: all
gather_facts: no
tags:
- ntp
tasks:
- name: Ensure ntp group exists
fail:
msg: >-
The 'ntp' group does not exist in the Ansible inventory.
run_once: true
when:
- "'ntp' not in groups"
- name: Ensure Chrony is installed and configured
hosts: ntp
max_fail_percentage: >-
{{ time_max_fail_percentage |
default(host_configure_max_fail_percentage) |
default(kayobe_max_fail_percentage) |
default(100) }}
tags:
- ntp
tasks:
- import_role:
name: ntp