On Fri, Jan 18, 2019 at 8:50 PM Albrecht, Thomas C <
thomas.c.albre...@lmco.com> wrote:
> While i realize it’s not ideal, I created an NFS export on the single node
> for demonstration purposes. Very simple to do. At some point, we’ll be
> moving the storage to a NAS.
>
> Can anyone tell me why a
Thanks Simone,
I will check the broker.I didn't specify the layout correctly - it's 'replica 3
arbiter 1' which was OK last time I used this layout.
Best Regards,Strahil Nikolov
От: Simone Tiraboschi
До: hunter86bg
Копие: users
Изпратен: събота, 19 януари 2019 г. 17:42
Тема: Re:
On Sat, Jan 19, 2019 at 1:07 PM wrote:
> Hello Community,
>
> recently I managed somehow to deploy a 2 node cluster on GlusterFS , but
> after a serious engine failiure - I have decided to start from scratch.
>
2 node hyperconverged gluster is definitively a bad idea since it's not
going to
Hello Community,
recently I managed somehow to deploy a 2 node cluster on GlusterFS , but after
a serious engine failiure - I have decided to start from scratch.
What I have done so far:
1. Inctall CentOS7 from scratch
2. Add ovirt repositories, vdo,cockpit for ovirt
3. Deployed the gluster
Hello All,
it seems that the ovirt-ha-broker has some problems:Thread-8::DEBUG::2019-01-19
19:30:16,048::stompreactor::479::jsonrpc.AsyncoreClient::(send) Sending response
...skipping...
smtp-server = localhost
smtp-port = 25
source-email = root@localhost
destination-emails = root@localhost
Hi Again,
it seems that sanlock error -223 indicated sanlock lockspace error.I have
somehow reinitialize the lockspace and the engine is up and running, but I have
2 VMs defined :1. The engine itself 2. A VM called "External-HostedEngineLocal"
I'm pretty sure that there are some tasks that the
I assumed that if ovirt3.6 required older versions of CentOS7, etc, it
would not allow the yum update due to dependency. I guess that's a bad
assumption.
vdsm does not start in fact. Here's the journal when attempting to
start it.
# journalctl -xe
Jan 19 10:13:36 vmserver2
If I try to run "vdsm-tool restore-nets", which is what starting the
vdsm-network.service seems to do first, I get the following:
( a large number of lines of the first error)
..
libvirt: XML-RPC error : authentication failed: authentication failed
libvirt: XML-RPC error : authentication
So, I try to manually start vdsm-network.service and see this,
suggesting I look in upgrade.log:
# systemctl status vdsm-network.service
● vdsm-network.service - Virtual Desktop Server Manager network restoration
Loaded: loaded (/usr/lib/systemd/system/vdsm-network.service;
enabled; vendor
9 matches
Mail list logo
