[Pacemaker] [Enhancement] Change of the "globally-unique" attribute of the resource.

[renayama19661014 at ybb.ne.jp]

Hi Andrew,

Sorry....

This problem is a thing of Pacemaker1.0.
On Pacemaker1.1.11, the resource did movement to stop definitely.

When "globally-unique" attribute changed somehow or other in Pacemaker1.1, Pacemkaer seems to carry out the reboot of the resource.

(snip)
Jan 15 18:29:40 rh64-2744 pengine[3369]:  warning: process_rsc_state: Detected active orphan prmClusterMon running on rh64-2744
Jan 15 18:29:40 rh64-2744 pengine[3369]:     info: clone_print:  Clone Set: clnClusterMon [prmClusterMon] (unique)
Jan 15 18:29:40 rh64-2744 pengine[3369]:     info: native_print:      prmClusterMon:0#011(ocf::pacemaker:ClusterMon):#011Stopped
Jan 15 18:29:40 rh64-2744 pengine[3369]:     info: native_print:      prmClusterMon:1#011(ocf::pacemaker:ClusterMon):#011Stopped
Jan 15 18:29:40 rh64-2744 pengine[3369]:     info: native_print: prmClusterMon#011(ocf::pacemaker:ClusterMon):#011 ORPHANED Started rh64-2744
Jan 15 18:29:40 rh64-2744 pengine[3369]:   notice: DeleteRsc: Removing prmClusterMon from rh64-2744
Jan 15 18:29:40 rh64-2744 pengine[3369]:     info: native_color: Stopping orphan resource prmClusterMon
Jan 15 18:29:40 rh64-2744 pengine[3369]:     info: RecurringOp:  Start recurring monitor (10s) for prmClusterMon:0 on rh64-2744
Jan 15 18:29:40 rh64-2744 pengine[3369]:     info: RecurringOp:  Start recurring monitor (10s) for prmClusterMon:1 on rh64-2744
Jan 15 18:29:40 rh64-2744 pengine[3369]:   notice: LogActions: Start   prmClusterMon:0#011(rh64-2744)
Jan 15 18:29:40 rh64-2744 pengine[3369]:   notice: LogActions: Start   prmClusterMon:1#011(rh64-2744)Jan 15 18:29:40 rh64-2744 pengine[3369]:   notice: LogActions: Stop    prmClusterMon#011(rh64-2744)

(snip)

Best Regards,
Hideo Yamauchi.

--- On Wed, 2014/1/15, renayama19661014 at ybb.ne.jp <renayama19661014 at ybb.ne.jp> wrote:

> Hi Andrew,
> 
> Thank you for comment.
> 
> > > But, the resource does not stop because PID file was changed as for the changed resource of the "globally-unique" attribute.
> > 
> > I'd have expected the stop action to be performed with the old attributes.
> > crm_report tarball?
> 
> Okay.
> 
> I register this topic with Bugzilla.
> I attach the log to Bugzilla.
> 
> Best Regards,
> Hideo Yamauchi.
> --- On Wed, 2014/1/15, Andrew Beekhof <andrew at beekhof.net> wrote:
> 
> > 
> > On 14 Jan 2014, at 7:26 pm, renayama19661014 at ybb.ne.jp wrote:
> > 
> > > Hi All,
> > > 
> > > When a user changes the "globally-unique" attribute of the resource, a problem occurs.
> > > 
> > > When it manages the resource with PID file, this occurs, but this is because PID file name changes by "globally-unique" attribute.
> > > 
> > > (snip)
> > > if [ ${OCF_RESKEY_CRM_meta_globally_unique} = "false" ]; then
> > >    : ${OCF_RESKEY_pidfile:="$HA_VARRUN/ping-${OCF_RESKEY_name}"}
> > > else
> > >    : ${OCF_RESKEY_pidfile:="$HA_VARRUN/ping-${OCF_RESOURCE_INSTANCE}"}
> > > fi
> > > (snip)
> > 
> > This is correct.  The pid file cannot include the instance number when globally-unique is false and must do so when it is true.
> > 
> > > 
> > > 
> > > The problem can reappear in the following procedure.
> > > 
> > > * Step1: Started a resource.
> > > (snip)
> > > primitive prmPingd ocf:pacemaker:pingd \
> > >        params name="default_ping_set" host_list="192.168.0.1" multiplier="200" \
> > >        op start interval="0s" timeout="60s" on-fail="restart" \
> > >        op monitor interval="10s" timeout="60s" on-fail="restart" \
> > >        op stop interval="0s" timeout="60s" on-fail="ignore"
> > > clone clnPingd prmPingd
> > > (snip)
> > > 
> > > * Step2: Change "globally-unique" attribute.
> > > 
> > > [root]# crm configure edit
> > > (snip)
> > > clone clnPingd prmPingd \
> > >    meta clone-max="2" clone-node-max="2" globally-unique="true"
> > > (snip)
> > > 
> > > * Step3: Stop Pacemaker
> > > 
> > > But, the resource does not stop because PID file was changed as for the changed resource of the "globally-unique" attribute.
> > 
> > I'd have expected the stop action to be performed with the old attributes.
> > crm_report tarball?
> > 
> > 
> > > 
> > > I think that this is a known problem.
> > 
> > It wasn't until now.
> > 
> > > 
> > > I wish this problem is solved in the future
> > > 
> > > Best Regards,
> > > Hideo Yamauchi.
> > > 
> > > _______________________________________________
> > > Pacemaker mailing list: Pacemaker at 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 at 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
>