Is it true that adding/removing a monitor operation in the resource configuration requites a "reload" operation in the RA to prevent the resource from being restarted? I doubt it...
>>> Ferenc Wagner <wf...@niif.hu> schrieb am 15.05.2013 um 11:29 in Nachricht <87li7g6160....@lant.ki.iif.hu>: > Andrew Beekhof <and...@beekhof.net> writes: > >> On 15/05/2013, at 5:19 PM, Ferenc Wagner <wf...@niif.hu> wrote: >> >>> I learnt that it's possible to change non-unique parameters of a >>> resource without restarting it if the agent implements the reload >>> action. On the other hand, adding a monitor operation does not seem to >>> have an effect until the resource is restarted. >> >> Thats not normal. >> >>> Is there a good reason for this, or am I doing something wrong? >> >> Hard to say without more info. > > Got it: adding a monitor operation online apparently also requires an > implemented reload action. It was implemented, but some resources were > not restarted since then, so Pacemaker didn't know about it. After > restarting all my resources, the reload action got recognised, and it > became possible to add the monitor operations online. > -- > Thanks, > Feri. > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
