[Pacemaker] Pacemaker resource migration behaviour

James Guthrie jag at open.ch
Wed Mar 6 02:59:45 EST 2013

On Mar 6, 2013, at 7:34 AM, Andrew Beekhof <andrew at beekhof.net> wrote:

> On Wed, Feb 6, 2013 at 11:41 PM, James Guthrie <jag at open.ch> wrote:
>> Hi David,
>> Unfortunately crm_report doesn't work correctly on my hosts as we have compiled from source with custom paths and apparently the crm_report and associated tools are not built to use the paths that can be customised with autoconf.
> It certainly tries to:
>   https://github.com/beekhof/pacemaker/blob/master/tools/report.common#L99
> What does it say on your system (or, what paths did you give to autoconf)?

You are correct, it does try to - there are a few problems though:
- the hardcoded depth (-maxdepth 5) that is used to search for the files is no good on my host
- the fact that it assumes the local state did would be /var (despite what was configured in autoconf)

In my case all files are in the path /opt/OSAGpcmk/pcmk

I submitted a pull-request which I was hoping to get some comment on, but didn't.


I know that it's not a complete solution and would suggest I resubmit the pull request in two parts:
1. Using the localstatedir and exec_prefix as configured in autoconf.
2. Make the maxdepth parameter default to 5, but be overridable with a flag to crm_report.


More information about the Pacemaker mailing list