[ClusterLabs] SLES 12 SP2 HAE

Thu Apr 6 04:16:03 EDT 2017

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.coltro at 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 <users at clusterlabs.org>; Cristiano Coltro <Cristiano.Coltro at microfocus.com>

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.coltro at microfocus.com<mailto:cristiano.coltro at microfocus.com

> >

> mobile: +39 335 1435589

> phone +39 02 36634936

> ______________

> [microfocus-logo]

>

>

>

>

> _______________________________________________

> Users mailing list: Users at 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20170406/222bc928/attachment-0003.html>