pcmk__native_allocate: vg.bv_sanlock:1 allocation score on node2: -INFINITY
Transition Summary:
Executing cluster transition:
On Wed, Dec 9, 2020 at 10:33 PM Pavel Levshin wrote:
See the file attached. This one has been produced and tested with
pacemaker 1.1.16 (RHEL 7).
--
Pavel
08.12.2020 10:14
as well.
On Mon, Dec 7, 2020 at 10:40 PM Pavel Levshin wrote:
Hello.
Despite many years of Pacemaker use, it never stops fooling me...
This time, I have faced a trivial problem. In my new setup, the cluster
consists of several identical nodes. A clone resource (vg.sanlock) is started
Hello.
Despite many years of Pacemaker use, it never stops fooling me...
This time, I have faced a trivial problem. In my new setup, the cluster
consists of several identical nodes. A clone resource (vg.sanlock) is
started on every node, ensuring it has access to SAN storage. Almost all
Hello.
I've just expiriensed a fault in my pacemaker-based cluster. Seriously,
I'm completely disoriented after this. Hopefully someone can give me a
hint...
Two-node cluster runs few VirtualDomains along with their common
infrastructure (libvirtd, NFS and so on). It is Pacemaker 1.1.16
11.10.2016 17:40, Ken Gaillot:
On 10/11/2016 07:06 AM, Pavel Levshin wrote:
Hi!
In continuation of prevoius mails, now I have more complex setup. Our
hardware are capable of two STONITH methods: ILO and SCSI persistent
reservations on shared storage. First method works fine, nevertheless
Hi!
In continuation of prevoius mails, now I have more complex setup. Our
hardware are capable of two STONITH methods: ILO and SCSI persistent
reservations on shared storage. First method works fine, nevertheless,
sometimes in the past we faced problems with inaccessible ILO devices or
stop just by killing the process. At least this could save
us a fencing.
Still I do not understand why optional constraint has not effect when
both VM and libvirtd are scheduled to stop, if there is live migration
in place. It looks like a bug.
--
Pavel Levshin
10.10.2016 20:58, Klaus
10.10.2016 15:11, Klaus Wenninger:
On 10/10/2016 02:00 PM, Pavel Levshin wrote:
10.10.2016 14:32, Klaus Wenninger:
Why are the order-constraints between libvirt & vms optional?
If they were mandatory, then all the virtual machines would be
restarted when libvirtd restarts. This is not des
able to restart VM in
absence of working libvirtd.
You are right, when the constraint is mandatory, live migration works fine.
--
Pavel Levshin
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users
Project Home:
