Andrew,
1. Is there a workaround for this issue ?
2. Also, can let me know if there are more issues with old versions in
deleting multistate resource as mentioned in
http://www.gossamer-threads.com/lists/linuxha/pacemaker/91230
Regards,
Kiran
On Wed, May 21, 2014 at 9:44 AM, Andrew Beekhof wr
On 19 May 2014, at 5:43 pm, K Mehta wrote:
> Please see my reply inline. Attached is the crm_report output.
>
>
> On Thu, May 8, 2014 at 5:45 AM, Andrew Beekhof wrote:
>
> On 8 May 2014, at 12:38 am, K Mehta wrote:
>
> > I created a multi state resource ms-2be6c088-a1fa-464a-b00d-f4bccb4f5
[root@vsan-test2 ~]# rpm -qa | grep pcs
pcs-0.9.26-10.el6.noarch
[root@vsan-test2 ~]# rpm -qa | grep ccs
ccs-0.16.2-63.el6.x86_64
[root@vsan-test2 ~]# rpm -qa | grep pace
pacemaker-libs-1.1.8-7.el6.x86_64
pacemaker-cli-1.1.8-7.el6.x86_64
pacemaker-1.1.8-7.el6.x86_64
pacemaker-cluster-libs-1.1.8-7.e
On , Andrew Beekhof wrote:
On 19 May 2014, at 4:17 pm, Andrew Beekhof wrote:
On 16 May 2014, at 3:41 am, Ian wrote:
Doing some experiments and Reading TFM, I found this:
5.2.2. Advisory Ordering
When the kind=Optional option is specified for an order constraint,
the constraint is conside
I am not quite understand how auto_tie_breaker works.
Say we have a cluster with 2 nodes and enabled auto_tie_breaker feature.
Each node has 2 NICs. One NIC is used for cluster communication and another
one is used for providing some services from the cluster.
So the question is how the nodes will
