Re: [ClusterLabs] cloned resources ordering and remote nodes problem

2017-04-06 Thread Ken Gaillot 
On 04/06/2017 09:32 AM, Radoslaw Garbacz wrote:
> Hi,
> 
> 
> I have a question regarding resources order settings.
> 
> Having cloned resources: "res_1-clone", "res_2-clone",
>  and defined order:  first "res_1-clone" then "res_2-clone"
> 
> When I have a monitoring failure on a remote node with "res_1" (an
> instance of "res_1-clone") which causes all dependent resources to be
> restarted, only instances on this remote node are being restarted, not
> the ones on other nodes.
> 
> Is it an intentional behavior and if so, is there a way to make all
> instances of the cloned resource to be restarted in such a case?

That is controlled by a clone's "interleave" meta-attribute. The default
(false) actually gives your desired behavior. I'm guessing you have
interleave=true configured.

> I can provide more details regarding the CIB configuration when needed.
> 
> Pacemaker 1.1.16-1.el6
> OS: Linux CentOS 6
> 
> 
> Thanks in advance,
> 
> -- 
> Best Regards,
> 
> Radoslaw Garbacz
> XtremeData Incorporated


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] cloned resources ordering and remote nodes problem

2017-04-06 Thread Radoslaw Garbacz 
Hi,


I have a question regarding resources order settings.

Having cloned resources: "res_1-clone", "res_2-clone",
 and defined order:  first "res_1-clone" then "res_2-clone"

When I have a monitoring failure on a remote node with "res_1" (an instance
of "res_1-clone") which causes all dependent resources to be restarted,
only instances on this remote node are being restarted, not the ones on
other nodes.

Is it an intentional behavior and if so, is there a way to make all
instances of the cloned resource to be restarted in such a case?

I can provide more details regarding the CIB configuration when needed.

Pacemaker 1.1.16-1.el6
OS: Linux CentOS 6


Thanks in advance,

-- 
Best Regards,

Radoslaw Garbacz
XtremeData Incorporated
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] [Problem] The crmd causes an error of xml.

2017-04-06 Thread renayama19661014 
Hi All,

I confirmed a development edition of Pacemaker.
 - 
https://github.com/ClusterLabs/pacemaker/tree/71dbd128c7b0a923c472c8e564d33a0ba1816cb5


property no-quorum-policy="ignore" \
        stonith-enabled="true" \
        startup-fencing="false"

rsc_defaults resource-stickiness="INFINITY" \
        migration-threshold="INFINITY"

fencing_topology \
        rh73-01-snmp: prmStonith1-1 \
        rh73-02-snmp: prmStonith2-1

primitive prmDummy ocf:pacemaker:Dummy \
        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="fence"

primitive prmStonith1-1 stonith:external/ssh \
        params \
        pcmk_reboot_retries="1" \
        pcmk_reboot_timeout="40s" \
        hostlist="rh73-01-snmp" \
        op start interval="0s" timeout="60s" on-fail="restart" \
        op stop interval="0s" timeout="60s" on-fail="ignore"

primitive prmStonith2-1 stonith:external/ssh \
        params \
        pcmk_reboot_retries="1" \
        pcmk_reboot_timeout="40s" \
        hostlist="rh73-02-snmp" \
        op start interval="0s" timeout="60s" on-fail="restart" \
        op stop interval="0s" timeout="60s" on-fail="ignore"

### Resource Location ###
location rsc_location-1 prmDummy \
        rule  300: #uname eq rh73-01-snmp \
        rule  200: #uname eq rh73-02-snmp



I pour the following brief crm files.
I produce the trouble of the resource in a cluster.
Then crmd causes an error.


(snip)
Apr  6 18:04:22 rh73-01-snmp pengine[5214]: warning: Calculated transition 4 
(with warnings), saving inputs in /var/lib/pacemaker/pengine/pe-warn-0.bz2
Apr  6 18:04:22 rh73-01-snmp crmd[5215]:   error: XML Error: Entity: line 1: 
parser error : Specification mandate value for attribute 
CRM_meta_fail_count_prmDummy
Apr  6 18:04:22 rh73-01-snmp crmd[5215]:   error: XML Error: rh73-01-snmp" 
on_node_uuid="3232238265">

pe-warn-0.bz2
Description: Binary data
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Antw: Re: SLES 12 SP2 HAE

2017-04-06 Thread Kai Dupke 
On 04/06/2017 08:34 AM,  Ulrich Windl  wrote:
> Can one file SLES bugs in bugzilla? I thought you can only file openSUSE bugs?

Every customer can file bugs for SLES, which is called an Service
Request for our customers.

Christiano however is a colleague of SUSE, so he can directly file a bug
without an SR.

And finally some SUSE engineers and others are on this list and will
engage out of band where appropriate.

regards,
kai

-- 
Sell not virtue to purchase wealth, nor liberty to purchase power.
Phone:  +49-(0)5102-9310828 Mail: kdu...@suse.com
Mobile: +49-(0)173-5876766  WWW:  www.suse.com

SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany)
GF:Felix Imendörffer,Jane Smithard,Graham Norton,HRB 21284 (AG Nürnberg)

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] SLES 12 SP2 HAE

2017-04-06 Thread Cristiano Coltro 
Thanks Bin!
So it's working as designed.
Thanks,
Have a nice day!
Cristiano

Cristiano Coltro
Premium Support Engineer

mail: cristiano.col...@microfocus.com
mobile: +39 335 1435589
phone +39 02 36634936
__
[microfocus-logo]

From: Bin Liu
Sent: Thursday, April 6, 2017 10:33 AM
To: users@clusterlabs.org
Subject: Re: [ClusterLabs] SLES 12 SP2 HAE

Hi, Cristiano
  pacemaker only get the cluster name from corosync on the first 
initialize. Then it will store the name in cib.
even you change the culster name in corosync.conf, pacemaker will not update it.
On 04/06/2017 04:16 PM, Cristiano Coltro wrote:

HI Zhen & Ulrich



I have tried to duplicate the issue but I wasn't able to reproduce.

Corosync is updated all the time



So I will not open any bug for the moment.

I'm sorry for the wrong heads up!



What is sure is that crm resource show do not reflect dinamically the cluster 
name.

It is written ONLY during ha-cluster-init.



If you change the cluster name while cluster is initialized you have to change 
it manually with crm configure edit



Is this working as designed?



Thanks,

Cristiano

Cristiano Coltro

Premium Support Engineer



mail: cristiano.col...@microfocus.com

mobile: +39 335 1435589

phone +39 02 36634936

__





-Original Message-

From: Zhen Ren

Sent: Thursday, April 6, 2017 4:01 AM

To: Cluster Labs - All topics related to open-source clustering welcomed 
; Cristiano Coltro 


Subject: Re: [ClusterLabs] SLES 12 SP2 HAE



Hi Cristiano,



Thanks for your report. I suggest you file a bug for this at 
https://bugzilla.suse.com so that it can be routed to the right person quickly.



On 04/05/2017 03:26 PM, Cristiano Coltro wrote:

> Hi all,

> I was noticing some behaviour on SLES 12 Sp2 HAE

>

>

>1.  Cluster Name

> If you go to yast2 > cluster and you change the cluster name, the change is 
> not reflected in /etc/corosync/corosync.conf  that shows the default name 
> "hacluster"

>

>1.  Expected votes

> With a 2 node cluster you have the corosync.conf configured like this for the 
> quorum section:

>

> provider: corosync_votequorum

>  expected_votes: 2

>  two_node: 1

>

> and it's correct

>

> If for some reason you redo an "ha-cluster-init"on the same first node

> WITHOUT overwriting the corosync.conf and then you perform an

> "ha-cluster-join" on the second node the corosync.conf changes like

> this

>

>provider: corosync_votequorum

>  expected_votes: 3

>  two_node: 0

>

>  so it seems that cluster do not check the number of nodes 
> but simply add a +1 every join you perform IF you DON'T overwrite the 
> original corosync.conf.

>

> Are 1 & 2 expected behaviour? Any experience on that?

It's probably a bug to fix, I think, so don't mix yast and HA bootstrap scripts 
to setup your cluster ATM:)



Regards,

Eric

>

> Thanks,

> Cristiano

>

>

> Cristiano Coltro

> Premium Support Engineer

>

> mail:

> cristiano.col...@microfocus.com >

> mobile: +39 335 1435589

> phone +39 02 36634936

> __

> [microfocus-logo]

>

>

>

>

> ___

> Users mailing list: Users@clusterlabs.org

> http://lists.clusterlabs.org/mailman/listinfo/users

>

> Project Home: http://www.clusterlabs.org Getting started:

> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf

> Bugs: http://bugs.clusterlabs.org








___

Users mailing list: Users@clusterlabs.org

http://lists.clusterlabs.org/mailman/listinfo/users



Project Home: http://www.clusterlabs.org

Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf

Bugs: http://bugs.clusterlabs.org

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] SLES 12 SP2 HAE

2017-04-06 Thread bliu 

Hi, Cristiano
  pacemaker only get the cluster name from corosync on the first 
initialize. Then it will store the name in cib.
even you change the culster name in corosync.conf, pacemaker will not 
update it.


On 04/06/2017 04:16 PM, Cristiano Coltro wrote:


HI Zhen & Ulrich

I have tried to duplicate the issue but I wasn't able to reproduce.

Corosync is updated all the time

So I will not open any bug for the moment.

_I'm sorry for the wrong heads up!_

What is sure is that crm resource show do not reflect dinamically the 
cluster name.


It is written ONLY during ha-cluster-init.

If you change the cluster name while cluster is initialized you have 
to change it manually with crm configure edit


Is this working as designed?

Thanks,

Cristiano

Cristiano Coltro

Premium Support Engineer

mail: cristiano.col...@microfocus.com

mobile: +39 335 1435589

phone +39 02 36634936

__

-Original Message-

From: Zhen Ren

Sent: Thursday, April 6, 2017 4:01 AM

To: Cluster Labs - All topics related to open-source clustering 
welcomed ; Cristiano Coltro 



Subject: Re: [ClusterLabs] SLES 12 SP2 HAE

Hi Cristiano,

Thanks for your report. I suggest you file a bug for this at 
https://bugzilla.suse.com so that it can be routed to the right person 
quickly.


On 04/05/2017 03:26 PM, Cristiano Coltro wrote:

> Hi all,

> I was noticing some behaviour on SLES 12 Sp2 HAE

>

>

>1.  Cluster Name

> If you go to yast2 > cluster and you change the cluster name, the 
change is not reflected in /etc/corosync/corosync.conf  that shows the 
default name "hacluster"


>

>1.  Expected votes

> With a 2 node cluster you have the corosync.conf configured like 
this for the quorum section:


>

> provider: corosync_votequorum

>  expected_votes: 2

>  two_node: 1

>

> and it's correct

>

> If for some reason you redo an "ha-cluster-init"on the same first node

> WITHOUT overwriting the corosync.conf and then you perform an

> "ha-cluster-join" on the second node the corosync.conf changes like

> this

>

>provider: corosync_votequorum

>  expected_votes: 3

>  two_node: 0

>

>  so it seems that cluster do not check the number of 
nodes but simply add a +1 every join you perform IF you DON'T 
overwrite the original corosync.conf.


>

> Are 1 & 2 expected behaviour? Any experience on that?

It's probably a bug to fix, I think, so don't mix yast and HA 
bootstrap scripts to setup your cluster ATM:)


Regards,

Eric

>

> Thanks,

> Cristiano

>

>

> Cristiano Coltro

> Premium Support Engineer

>

> mail:

> cristiano.col...@microfocus.com >

> mobile: +39 335 1435589

> phone +39 02 36634936

> __

> [microfocus-logo]

>

>

>

>

> ___

> Users mailing list: Users@clusterlabs.org

> http://lists.clusterlabs.org/mailman/listinfo/users

>

> Project Home: http://www.clusterlabs.org Getting started:

> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf

> Bugs: http://bugs.clusterlabs.org



___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org