Files
grenade/playbooks/grenade.yaml
Yatin Karel d4e4bb37b8 [CI] Fail the playbook when any node setup fails
Currently on the multinode jobs, job continue to run even
if devstack setup fails on any of the node and then fails later
when required conditions are not met.
This patch changes it to fail if any of the node setup fails using
any_errors_fatal: true.

Change-Id: I9dc8e8862dcf81bf5c5c953668fa0085118032ea
Signed-off-by: Yatin Karel <ykarel@redhat.com>
2025-10-03 17:14:23 +05:30

38 lines
1.3 KiB
YAML

- hosts: all
any_errors_fatal: true
strategy: linear
roles:
- role: orchestrate-devstack
devstack_base_dir: "{{ devstack_bases.old }}"
devstack_data_base_dir: "{{ devstack_bases.shared }}"
- hosts: controller
roles:
- configure-grenade-branches
- role: write-grenade-conf
base_dir: "{{ devstack_bases.shared }}"
grenade_base_dir: "{{ devstack_bases.new }}"
grenade_plugins: "{{ devstack_plugins|default({}) }}"
# run-grenade is configured to run also tempest smoke tests
# on the old node by default.
- role: run-grenade
base_dir: "{{ devstack_bases.shared }}"
grenade_base_dir: "{{ devstack_bases.new }}"
# Copied (with minimal changes) from tempest.git:playbooks/devstack-tempest.yaml
# We run tests only on one node, regardless how many nodes are in the system,
# after grenade completes.
- hosts: tempest
environment:
# This enviroment variable is used by the optional tempest-gabbi
# job provided by the gabbi-tempest plugin. It can be safely ignored
# if that plugin is not being used.
GABBI_TEMPEST_PATH: "{{ gabbi_tempest_path | default('') }}"
vars:
devstack_base_dir: "{{ devstack_bases.new }}"
roles:
- setup-tempest-run-dir
- setup-tempest-data-dir
- acl-devstack-files
- run-tempest