pacemaker_status

Role Documentation

Welcome to the “pacemaker_status” role documentation.

Role Defaults

This section highlights all of the defaults and variables set within the “pacemaker_status” role.

null
...

Role Variables: main.yml

metadata:
  name: Check the status of the pacemaker cluster
  description: >
    This runs `pcs status` and checks for any failed actions.

    A failed status post-deployment indicates something is not configured
    correctly. This should also be run before upgrade as the process will
    likely fail with a cluster that's not completely healthy.

    This validation fails if pacemaker service is found failed or inactive.
  groups:
  - post-deployment

Molecule Scenarios

Molecule is being used to test the “pacemaker_status” role. The following section highlights the drivers in service and provides an example playbook showing how the role is leveraged.

Scenario: default

Driver: podman:

Molecule Platform(s)

- name: centos
  hostname: centos
  image: centos/centos:stream8
  registry:
    url: quay.io
  dockerfile: ../../../../.config/molecule/Dockerfile
  pkg_extras: python*-setuptools python*-pyyaml
  volumes:
  - /etc/ci/mirror_info.sh:/etc/ci/mirror_info.sh:ro
  privileged: true
  environment:
    http_proxy: "{{ lookup('env', 'http_proxy') }}"
    https_proxy: "{{ lookup('env', 'https_proxy') }}"
  ulimits:
  - host

Molecule Inventory

hosts:
  all:
    hosts:
      centos:
        ansible_python_interpreter: /usr/bin/python3

Example default playbook

- name: Converge
  hosts: all
  gather_facts: false

  tasks:
  - name: Warn developers about the lack of molecule testing
    fail:
      msg: >-
        This role needs molecule tests!