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:
ocf::heartbeat:apache does not check the testurl and do not move the resource group to another node.

Version-Release number of selected component (if applicable):
pacemaker-1.1.15-11.el7_3.5.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Create resource:
pcs resource create APACHE apache configfile="/etc/httpd/conf/httpd.conf" \
statusurl="http://127.0.0.1/server-status" client="curl" \
testurl="http://hacluster" testregex10="CLUSTER.EXAMPLE.COM"
2.Block port 80 where the webserver is served:
firewall-cmd --remove-service=80
3.Check if status url is accessible from the other nodes:
curl http://hacluster

Actual results:
Nothing.

Expected results:
Move the resource (or entire group) to another cluster node

Additional info:
'ocf::heartbeat:apache' does not start without the "statusurl" option, so they need to be used together

In step 2 the actual command is:
firewall-cmd --remove-service=http

It seems that the "bug"  is not a bug.Here is the actual working resource:
pcs resource create APACHE apache params \
configfile="/etc/httpd/conf/httpd.conf" testurl="/" \
testregex="CLUSTER.EXAMPLE.COM" op monitor interval=120s timeout=10s \
start-delay=5s OCF_CHECK_LEVEL=10

The testurl check is run from the same node that is running the apache resource (not from other cluster nodes), so it will succeed as long as the page is accessible locally. Most firewall configurations always allow local connections, even if the port if blocked to other hosts.

And as you figured out, a monitor must be configured with OCF_CHECK_LEVEL=10 for the apache resource agent to run the testurl check.