[ovirt-users] Re: New failure Gluster deploy: Set granual-entry-heal on --> Bricks down

2021-01-08 Thread Ritesh Chikatwar
Hello, Can you try once cleaning the gluster deployment you can do this by running this command on one of the hosts. ansible-playbook /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_cleanup.yml -i /etc/ansible/hc_wizard_inventory.yml And then rerun the Ansible

[ovirt-users] Re: New failure Gluster deploy: Set granual-entry-heal on --> Bricks down

2021-01-08 Thread Strahil Nikolov via Users
What is the output of 'rpm -qa | grep vdo' ? Most probably the ansible flow is not deploying kvdo , but it's necessary at a later stage.Try to overcome via "yum search kvdo" and then 'yum install kmod-kvdo" (replace kmod-kvdo with the package for EL8). Also, I think that you can open a github

[ovirt-users] Re: New failure Gluster deploy: Set granual-entry-heal on --> Bricks down

2021-01-08 Thread Charles Lam
Dear Strahil, I have rebuilt everything fresh, switches, hosts, cabling - PHY-SEC shows 512 for all nvme drives being used as bricks. Name resolution via /etc/hosts for direct connect storage network works for all hosts to all hosts. I am still blocked by the same "vdo: ERROR - Kernel

[ovirt-users] [ANN] Async release for ovirt-engine is now available

2021-01-08 Thread Sandro Bonazzola
The oVirt Team has just released a new version of ovirt-engine package (4.4.4.7) that fixes a few important bugs: - [BZ 1894454](https://bugzilla.redhat.com/1894454) - VM fails to boot when moved to a cluster with a different chipset - [BZ 1908643](https://bugzilla.redhat.com/1908643) -

[ovirt-users] Re: 2021 first ovirt network question

2021-01-08 Thread carl langlois
Hi, Let me share our experience with VDI and spice. First I do not have a solution to make the spice server more reactive. Here is our current infra: 12 hosts with Xeon processor with 10G port and a couple of hundreds of memory per host. This runs around 55 VMs 40 of them are servers vms and 15

[ovirt-users] Re: QEMU error qemuDomainAgentAvailable in /var/log/messages

2021-01-08 Thread souvaliotimaria
Thank you very much for your answer. The service is up and running in the engine but it is only loaded on the nodes. Should I start it (enabling also?) on the nodes to? There is one VM that I have not installed the guest agent on and it is running on the arbitrary host. Also, about the

[ovirt-users] Re: [ovirt-devel] CentOS Stream support

2021-01-08 Thread Sandro Bonazzola
Il giorno mar 5 gen 2021 alle ore 17:12 lejeczek via Users ha scritto: > Hi guys, > > Is supported and save to transition with > 4.4 to Centos > Stream, now when "Stream" is the only way to the future? Any > knows for certain? > We moved oVirt Node and oVirt Appliance to CentOS Stream for the

[ovirt-users] Re: not able to upload disks, iso - Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser.

2021-01-08 Thread Vojtech Juranek
Hi, > We are unning with 4.4.3.12-1.el8 version and so far working fine, but today > users complained they are unable to upload new disks and upon checking > found "Connection to ovirt-imageio service has failed. Ensure that > ovirt-engine certificate is registered as a valid CA in the browser"