RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1893743 - [8.4] [RFE] Release Ansible role for cluster HA in rhel-system-roles
Summary: [8.4] [RFE] Release Ansible role for cluster HA in rhel-system-roles
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.4
Assignee: Pavel Cahyna
QA Contact: michal novacek
Eliane Ramos Pereira
URL:
Whiteboard: role:clusterha
Depends On: 1841019
Blocks: 1894575
TreeView+ depends on / blocked
 
Reported: 2020-11-02 13:55 UTC by Pavel Cahyna
Modified: 2022-04-28 18:17 UTC (History)
7 users (show)

Fixed In Version: rhel-system-roles-1.0.0-28.el8
Doc Type: Enhancement
Doc Text:
.Full Support for HA Cluster RHEL System Role The High Availability Cluster (HA Cluster) role, previously available as a Technology Preview, is now fully supported. The following notable configurations are available: * Configuring fence devices, resources, resource groups, and resource clones including meta attributes and resource operations * Configuring resource location constraints, resource colocation constraints, resource order constraints, and resource ticket constraints * Configuring cluster properties * Configuring cluster nodes, custom cluster names and node names * Configuring multi-link clusters * Configuring whether clusters start automatically on boot Running the role removes any configuration not supported by the role or not specified when running the role. The HA Cluster System Role does not currently support SBD.
Clone Of:
Environment:
Last Closed: 2021-05-18 16:02:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pcahyna: mirror+


Attachments (Terms of Use)

Description Pavel Cahyna 2020-11-02 13:55:58 UTC

Comment 10 michal novacek 2021-02-20 21:01:24 UTC
I have verified that rhel-system-roles.ha_cluster from rhel-system-roles-1.0.0-29.el8 works correctly in the following scenarios:

  * custom cluster name
  * disabling cluster autostart
  * custom sequential node names that are different from hostnames

on one and three node cluster.

Comment 21 errata-xmlrpc 2021-05-18 16:02:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (rhel-system-roles bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1909


Note You need to log in before you can comment on or make changes to this bug.