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.

Description of problem:

This bug is intended to track all bugs encountered in HA Apache deployment scenario testing for RHEL 7.

Testplan: TBA

Draft of HA Apache webfarm deployment scenario: 
http://rhel-ha.etherpad.corp.redhat.com/PRD-HA-webfarm

Did this happen?  Can it be closed or do we need to bump to 7.2?

I have tested that it is possible to create and run apache in active/active
mode as described in comment 1. Pages served by apache are being kept on shared
gfs2 filesystem. I have used haproxy to loadbalance queries to both apache
instances equally.

Manually I have done the following functional testing:

    * Create and start apache, clusterfs and haproxy according to comment 1

    * Downloaded several hunderds of pages from ip address where haproxy
        listens and verified that both nodes served about the same amount of
        queries.

    * While the download was running I hard rebooted one of the apache nodes
        and checked that there were no disturbance in pages downloading and 
        once the rebooted node joined back the cluster it started replying
        to the queries again.


I do not have the tests automated yet and did not run it over longer period of
time.

Is the testing in Comment 2 considered sufficient to close this bz?