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
On 14 Jan 2014, at 7:26 pm, renayama19661...@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.
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
On 15 Jan 2014, at 12:06 pm, renayama19661...@ybb.ne.jp wrote:
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
