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.

Description of problem:
Based on requirements stated in Bug 532976, ensure that content in this
document aligns with those requirements.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Since this has a doc-Cluster-Administration component, I'm reassigning it to me, but I will not be able to complete this for RHEL 6.1 (since I'm just looking at it now) so I'm moving it to RHEL 6.2.

This may be an issue for the revamped Cluster Overview, or it may well have been addressed by a technical note for RHEL 6.0, but this cannot be determined in the time frame to complete this by 6.1.

This is something that is most likely another example to include in the Configuration Example - Highly Available Virtualization document that is scheduled for completion in the RHEL 6.2 timeframe. So I'm moving this BZ to 6.3, to assess whether we'll be able to add this information to the next revision of that document.

The new HA VM document is tracked in BZ#616637.

The HA VM document is still out for review, pending some personnel/resource issues. When that gets resolved I'll return to addressing this bug.

Status unchanged -- moving to 6.4.

*** Bug 616636 has been marked as a duplicate of this bug. ***