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.

Bug 1005924

Summary: Detect correct apache default config in the apache resource agent.
Product: Red Hat Enterprise Linux 7 Reporter: David Vossel <dvossel>
Component: resource-agentsAssignee: David Vossel <dvossel>
Status: CLOSED CURRENTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.0CC: agk, cluster-maint, fdinitto, mnovacek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: resource-agents-3.9.5-13.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 12:18:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Vossel 2013-09-09 16:51:24 UTC
Description of problem:
The pacemaker Apache resource-agent does not default to the correct apache configuration file shipped in rhel7.

How reproducible:
always

Steps to Reproduce:
1. configure apache resource without configfile option set

Actual results:
apache resource fails.

Expected results:
apache agent should start and detect the correct default configuration location.

Comment 1 David Vossel 2013-09-09 16:57:04 UTC
A patch exists for this upstream.

https://github.com/davidvossel/resource-agents/commit/3cafd1e5dd73e61af80aca1c77e58f7813456b35

Comment 3 David Vossel 2013-09-09 22:12:45 UTC
built and ready for testing

Comment 6 michal novacek 2014-03-28 14:27:26 UTC
I have verified that apache resource can be started without configfile
parameter given in resource-agents-3.9.5-26.el7.x86_64.

-----

[root@duck-03 ~]# rpm -q resource-agents
resource-agents-3.9.5-26.el7.x86_64:

[root@duck-03 ~]# pcs resource create webserver ocf:heartbeat:apache

[root@duck-03 ~]# pcs status
...
Online: [ duck-03 ]

Full list of resources:

 virt-fencing   (stonith:fence_ipmilan):        Started duck-03 
 webserver      (ocf::heartbeat:apache):        Started duck-03 

[root@duck-03 ~]# pcs resource show webserver
 Resource: webserver (class=ocf provider=heartbeat type=apache)
  Operations: start interval=0s timeout=40s (webserver-start-timeout-40s)
              stop interval=0s timeout=60s (webserver-stop-timeout-60s)
              monitor interval=10 timeout=20s (webserver-monitor-interval-10)

Comment 7 Ludek Smid 2014-06-13 12:18:21 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.