On 21 May 2014, at 3:13 pm, K Mehta wrote:
> Andrew,
> 1. Is there a workaround for this issue ? '
For now its basically just "retry the command"
> 2. Also, can let me know if there are more issues with old versions in
> deleting multistate resource as mentioned in
> http://www.gossamer-thr
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
On 8 May 2014, at 12:38 am, K Mehta wrote:
> I created a multi state resource ms-2be6c088-a1fa-464a-b00d-f4bccb4f5af2
> (vha-2be6c088-a1fa-464a-b00d-f4bccb4f5af2).
>
> Here is the configuration:
> ==
> [root@vsanqa11 ~]# pcs config
> Cluster Name: vsanqa11_12
> Corosync
I created a multi state resource ms-2be6c088-a1fa-464a-b00d-f4bccb4f5af2
(vha-2be6c088-a1fa-464a-b00d-f4bccb4f5af2).
Here is the configuration:
==
[root@vsanqa11 ~]# pcs config
Cluster Name: vsanqa11_12
Corosync Nodes:
Pacemaker Nodes:
vsanqa11 vsanqa12
Resources:
Maste
