On Thu, Nov 24, 2011 at 4:03 PM, Vladislav Bogdanov <bub...@hoster-ok.com> wrote: > 24.11.2011 07:37, Andrew Beekhof wrote: >> On Wed, Nov 23, 2011 at 7:30 PM, Vladislav Bogdanov >> <bub...@hoster-ok.com> 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 >> >> Looks like some part of the PE wants to do a reload... oh, this is a >> recurring action - those don't result in the whole resource being >> reloaded, just the monitor op. >> >> Did the change not also affect the start action? > > Nothing in logs, but my expectations if I add new parameter to a > resource definition that it should be reloaded/restarted.
Me too. I'll check why the start action wasn't compared when you send through the tarball > I will check > if reload works on parameter change, not addition. > Now it "works" exactly the same way like I posted in that thread which I > referenced in a parallel reply to Andreas. > >> >>> 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) >>> >>> It worked some time ago after it has been fixed by Andrew. >>> Hopefully that can be fixed again. >>> >>> Fell free to ask me for hb_report if it is needed. >> >> it will be, sorry. >> strange that our regression tests are not catching these. > > Will do in few hours. > >> >>> >>> btw, isn't CRIT is too strong for that log message? >> >> yes, left over from the last time i was debugging aparently :( >> >>> >>> Best, >>> Vladislav >>> >>> >>> _______________________________________________ >>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>> >>> Project Home: http://www.clusterlabs.org >>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>> Bugs: http://bugs.clusterlabs.org >>> >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org