ion repeat i writing about it. Thanks for
On 15 Aug 2017, at 14:35, Yedidyah Bar David
On Mon, Aug 14, 2017 at 12:04 PM, Spickiy Nikita
Hi, in advance s
Hi, in advance sorry, i beginner. I try setting HA on oVirt. I install
hosted-engine on host and after adding two hosts in web portal. When i install
hosts then select DEPLOY in hosted-engine. But when i shutdown node, on which
run hosted-engine, and hosted-engine is not start on other hosts
Hi, i try install oVirt hosted-engine. For storage i use iscsi target
(Infotrend DS1012RE). I make install, but have error to service
ovirt-ha-broker.service and vdsmd.service:
systemctl -l status ovirt-ha-broker.service
● ovirt-ha-broker.service - oVirt Hosted Engine High Availability
Hi. I try setting hosted-engine. I make cluster of two node. I run installation
step by step as written in ovirt documentation. I add storage, iso domain, etc.
Then i create VM. Everything working, all right. Now i shutdown hosted-engine
and my VM also not avaliable. It normal behavior? Or i
Hi, i use engine 220.127.116.11-1.el7 version. When i try opening setting Storage >
Volumes > MyVolume i get error at the top of the screen.
In log UI https://paste.fedoraproject.org/paste/---B4tGrLbAVYpl1TvR0sg/raw.
How to fix it?
Users mailing list --
Hi, i upgraded oVirt node to 18.104.22.168 version. After upgrade I can not migrate
VM or run VM on the node. After viewing logs file i find several errors. One
2018-06-07 15:52:20,536+07 ERROR
Disable EPEL repo and repeat update
On 19 Jun 2018, at 22:26, Jacob Green
I just did not know where to look for the errors, I now see that it is telling
me it is failing on this package "collectd"
So when I go to my host and I run yum list collectd I see
Hi, i try install oVirt node, but getting errors on step post-install script.
Screen error in attachment.
Hi, i have oVirt instance (22.214.171.124-1.el7.centos). So, i have cluster with
gluster. Hosts periodically non response and VM's is not responding. Usually it
happens after get message "command GetGlusterVolumeHealInfoVDS failed: Message
timeout which can be caused by communication issues".
884+0300 ERROR (migmon/f52e8e78) [root] FINISH thread
On 17 Oct 2018, at 14:42, Sahina Bose
On Tue, Oct 16, 2018 at 11:39 PM Spickiy Nikita
Hi, i have oVirt instance (126.96.36.199-1.el7.
Mail list logo