Mistery solved:
Never put:
[ "${2}" = release ] && crm resource stop VMA_${1}
inside
/etc/libvirt/hooks/qemu
Very wrong decision.
On Monday 07 December 2015 16:49:01 emmanuel segura wrote:
> the next time show your full config unless your config have something
> special that you can't show.
>
Hi Ken,
The comments are in the text.
On 4.12.2015 19:06, Ken Gaillot wrote:
On 12/04/2015 10:22 AM, Klechomir wrote:
Hi list,
My issue is the following:
I have very stable cluster, using Corosync 2.1.0.26 and Pacemaker 1.1.8
(observed the same problem with Corosync 2.3.5 & Pacemaker
Hi,
Sorry didn't get your point.
The xml of the VM is on a active-active drbd drive with ocfs2 fs on it
and is visible from both nodes.
The live migration is always successful.
On 4.12.2015 19:30, emmanuel segura wrote:
I think the xml of your vm need to available on both nodes, but your
On 12/04/2015 10:22 AM, Klechomir wrote:
> Hi list,
> My issue is the following:
>
> I have very stable cluster, using Corosync 2.1.0.26 and Pacemaker 1.1.8
> (observed the same problem with Corosync 2.3.5 & Pacemaker 1.1.13-rc3)
>
> Bumped on this issue when started playing with VirtualDomain
Hi list,
My issue is the following:
I have very stable cluster, using Corosync 2.1.0.26 and Pacemaker 1.1.8
(observed the same problem with Corosync 2.3.5 & Pacemaker 1.1.13-rc3)
Bumped on this issue when started playing with VirtualDomain resources,
but this seems to be unrelated to the RA.
