On Wed, Apr 16, 2008 at 3:45 PM, Steinhauer Juergen <[EMAIL PROTECTED]> wrote: > Andrew Beekhof schrieb: > > > > > > > > > > > actually it is implemented - just not that way > > > > > > > > you have to advertise the reload function in the RA (see the Dummy > RA). > > > > you also have to set unique=0 for any attribute that causes a reload > > > > instead of a restart when changed. > > > > > > > > then, to cause a reload, just change the attribute you indicated > > > > > > > > > > > > > > > > > > > I implemented a "reload" function in the OCF agent, but if I set the > > > target_role to "reload" nothing happens (beside a CIB update). > > > > > > > > > > Ok, now I understand. I've to add a new attribute (e.g. "reload_trigger") > and every time I change this attribute, the resource is not restarted, but > reloaded. > > I've added following parameter to the OCF: > > <parameter name="reload_trigger" unique="0" required="0"> > <longdesc lang="en"> > The Reload Trigger String gives the date of the last reload. > </longdesc> > <shortdesc lang="en">Reload Trigger String</shortdesc> > <content type="string" default="not yet" /> > </parameter> > > But whenever I change a parameter, no matter if unique is set to zero or > not, the resource is always restarted. > > Any idea?
You added the reload operation to the RA (and the metadata)? Maybe restart the node... I think we cache the metadata at some point. If neither of those work... use hb_report to create a tarball and attach it to a bug. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
