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: Any variables modified in /etc/sysconfig/pacemaker have no effect because the init script that reads this file does not subsequently export those variables before starting the daemon.  So, if you were to say enable a PCMK_debugfile, it will not be used.  In RHEL 7 this is handled for us automagically by systemd via the service unit file's 

  EnvironmentFile=-/etc/sysconfig/pacemaker

but in RHEL 6, our init script takes care of setting everything up, and so it needs to ensure that the daemon will be able to read the configured variables from the environment.  



Version-Release number of selected component (if applicable): pacemaker-1.1.12-4.el6


How reproducible: Always


Steps to Reproduce:
1. Configure PCMK_debugfile=/var/log/pacemaker1.log in /etc/sysconfig/pacemaker
2. Start pacemaker
3. Check whether /var/log/pacemaker1.log was created and is being logged to

Actual results: File is not created and logging goes to default location


Expected results: Settings from /etc/sysconfig/pacemaker are honored


Additional info:

Created attachment 974504 [details]
Export environment variables from sysconfig before starting daemon

First line of /etc/sysconfig/pacemaker:

# For non-systemd based systems, prefix export to each enabled line

I like the patch though, even nicer :-)

D'oh! Looked right past that.  Thanks for pointing it out.

No capacity for 6.7, acking for 6.8

QE ack please (since you created the patch I'm assuming you know how to test :)

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1424.html

FYI The pacemaker_remote init script is affected by this, too. Fixed upstream as of 60bf228. It may be too late to get that one into 6.8.

(In reply to Ken Gaillot from comment #13)
> FYI The pacemaker_remote init script is affected by this, too. Fixed
> upstream as of 60bf228. It may be too late to get that one into 6.8.

FYI, the pacemaker_remote equivalent did not make it into 6.8, but will be included in 6.9 via the rebase for Bug 1356727.