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.

For RHEL 7, we added a procedure to the GFS2 manual on configuring GFS2 with Pacemaker. Since Pacemaker is supported in RHEL 6, we should add this procedure to the RHEL 6 document as well. There are, however, some differences -- specifically the fact that clvmd be started directly using the init service (service clvmd start/stop/status, or chkconfig clvmd on).

There is a Portal article on this topic:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Global_File_System_2/ch-clustsetup-GFS2.html

This should be made clear (quoring Frank Danapfel):

-------
> The resource created in https://access.redhat.com/solutions/530223 is a volume group, not one for managing clvmd.

IMHO, this is not apparently clear when reading the kbase, since the
text of the kbase the whole time talks about clvmd, and even mentions at
the end that it would be possible to use clvmd as a resource:

"NOTE: If the clvmd service is managed by a Pacemaker resource, as
opposed to being started on boot by the init service, the resource
monitor interval should not be set too low."

Therefore it would be great if the kbase article could be improved to
make it clear that clvmd must be started by init on RHEL6 even with
pacemaker.
-----------------

Since this is now on the Portal I'm closing this BZ:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Global_File_System_2/ch-clustsetup-GFS2.html