Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

activation_mode=exclusive clarification

Step 1 incorrectly uses "exclusive=true" in the description. This should be "activation_mode=exclusive", which is used correctly in the code block.

"activation_mode=exclusive" is the default value and does not need to be specified at all. Additionally, vg_access_mode=system_id and vg_access_mode=tagging force exclusive activation. So while it's fine to be explicit, it's unnecessary for those two reasons.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html/configuring_and_managing_high_availability_clusters/assembly_configuring-active-passive-http-server-in-a-cluster.adoc-configuring-and-managing-high-availability-clusters#annotations:52011a4b-08a4-49b7-a4b9-0cba12a9b863

There is at least one other instance of this (in Chapter 5).

The instance in Chapter 5 also includes the incorrect parameter within the command.

This is actually fixed in the latest version of the document:

https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_high_availability_clusters/#proc_configuring-resources-for-http-server-in-a-cluster-configuring-ha-http

But the second procedure has not been updated so I'm leaving this open until I can address that.

In the meantime I'm moving this to MODIFIED to indicate that we are working on this.

This is being addressed in this BZ as well:

https://bugzilla.redhat.com/show_bug.cgi?id=1674426