Dne 18.4.2017 v 19:52 Scott Greenlese napsal(a):
My thanks to both Ken Gaillot and Tomas Jelinek for the workaround. The
procedure(s) worked like a champ.
I just have a few side comments / observations ...
First - Tomas, in the bugzilla you show this error message on your
cluster remove command
Hi,
my resources are virtual machines. If booting of them is not succesful, i'd
like to monitor the boot procedure. To see where/when/why they stop booting.
The vm's are created with qemu and kvm.
Using virtual machine manager to monitor boot procedure is difficult. I don't
know on which node th
Tomas,
Yes, I have an IBM internal build we're using for KVM on System Z.I
tried the --force option and, while it didn't complain,
it didn't work either (as expected, as per bug
https://bugzilla.redhat.com/show_bug.cgi?id=1225423), so
maybe it is a valid option.
[root@zs95kj VD]# date; pcs cl
On 19/04/17 02:38 AM, Ulrich Windl wrote:
Digimer schrieb am 18.04.2017 um 19:08 in Nachricht
> <26e49390-b384-b46e-4965-eba5bfe59...@alteeve.ca>:
>> On 18/04/17 11:07 AM, Lentes, Bernd wrote:
>>> Hi,
>>>
>>> i'm currently establishing a two node cluster. Each node is a HP server
> with
>> a
On 18/04/17 15:40, Ken Gaillot wrote:
On 04/18/2017 09:14 AM, lejeczek wrote:
On 18/04/17 14:45, Digimer wrote:
On 18/04/17 07:31 AM, lejeczek wrote:
.. device_block & device_unblock in dmesg.
and I see that the LVM resource would fail.
This to me seems to happen randomly, or I fail to spo
On 18/04/17 15:52 +0200, Jan Pokorný wrote:
> On 17/04/17 09:51 -0500, Ken Gaillot wrote:
>> On 04/13/2017 07:04 AM, Jan Pokorný wrote:
>>> On 03/04/17 09:47 -0500, Ken Gaillot wrote:
With a group, you could reproduce most of this functionality, though it
would be more verbose: you'd need
Should have gone to the list...
Digimer schrieb am 19.04.2017 um 17:20 in Nachricht
> <600637f1-fef8-0a3d-821c-7aecfa398...@alteeve.ca>:
> > On 19/04/17 02:38 AM, Ulrich Windl wrote:
> > Digimer schrieb am 18.04.2017 um 19:08 in
Nachricht
> >> <26e49390-b384-b46e-4965-eba5bfe59...@altee