-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-system-roles-1.92.0-0.1.el9
-
None
-
FutureFeature
-
rhel-sst-system-roles
-
0
-
Dev ack
-
False
-
-
Yes
-
None
-
Requested
-
None
-
Enhancement
-
-
Proposed
-
None
This is a clone of issue RHEL-46219 to use for version rhel-9.6
–
Original description:
Goal
- As an ha_cluster role user, I want to be able to export corosync configuration and other essential pieces of existing cluster setup so that when running the exported configuration as a ha_cluster role playbook I am able to recreate the same cluster.
- In this step no pacemaker, sbd, qnetd or other configuration is expected to be exported
Acceptance Criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- There is a way to export corosync configuration into a variables / playbook
- Other necessary parts of configuration are handled as well:
- ha_cluster_hacluster_password
- ha_cluster_start_on_boot
- ha_cluster_corosync_key_src
- ha_cluster_pacemaker_key_src
- ha_cluster_fence_virt_key_src
- ha_cluster_regenerate_keys
- The result can be run as a playbook and creates a bare running cluster with no resources. However, the whole corosync configuration is recreated.
- clones
-
RHEL-46219 [RFE] rhel_system_roles.ha_cluster - export corosync configuration
- Integration
- links to
-
RHEA-2024:143087 rhel-system-roles bug fix and enhancement update