[Pacemaker] Reload does not work with current github tree (2d8fad5)

Vladislav Bogdanov bubble at hoster-ok.com
Wed Nov 23 05:38:36 EST 2011

Hi Andreas,

23.11.2011 13:13, Andreas Kurz wrote:
> On 11/23/2011 09:30 AM, Vladislav Bogdanov wrote:
>> Hi Andrew, all
>> Just noticed that reload action does not happen when resource definition
>> change:
>> Nov 23 08:16:08 v03-a pengine: [2091]: CRIT: check_action_definition:
>> Parameters to c5-x64-devel.vds-ok.com-vm_monitor_10000 on v03-b changed:
>> recorded 94f8fd587de8d9dd8454443
>> cbde11b4e vs. f37a02aea4d5fa7b1fbb54d458eaf8c1 (reload:3.0.5)
>> 0:0;350:43:0:001c4c10-8c18-482a-9eeb-42bcdac32719
>> Nov 23 08:16:08 v03-a pengine: [2091]: notice: RecurringOp:  Start
>> recurring monitor (10s) for c5-x64-devel.vds-ok.com-vm on v03-b
>> Nov 23 08:16:08 v03-a pengine: [2091]: notice: LogActions: Leave
>> c5-x64-devel.vds-ok.com-vm#011(Started v03-b)
> What did you change where you expected a reload to happen?

I changed primitive parameters, notably added one more parameter.

Reload worked before changes Andrew did with history (hg f59d7460bdde,
see thread at
http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg09324.html), then
it stopped to work after that commit, and then Andrew fixed it again.
Some changes in near past (1-2 months I suspect) broke that again. Can't
say right now if it worked with 1.1.6.


More information about the Pacemaker mailing list