- Users - oVirt List Archives

Ovirt node Virus scan
by marcel d'heureuse 29 Apr '22

29 Apr '22

Hi, I have to scan our 18 nodes with a virus scanner and I have to provide the report to our ito. This nodes have no internet connection and they will not get it. Which software I should use? Clamav? I can shutdown each single node and can scan but I would prefer to have it as cmd running and generate monthly or weekly reports. I don't want to have the daemon running. How did you do this? Br Marcel

2 1

4.5.0.1 ovirt hosted-engine deployment fails
by Mohamed Roushdy 29 Apr '22

29 Apr '22

Hello, I’ve researched a bit about this problem, but none of the proposed solutions fixed it. I’m trying to deploy Ovirt 4.5.0.1 in my lab, and the installation fails with the following error: [cid:image001.png@01D85BDF.87978B40] I’ve even tried to delete the default network bridge (as suggested in some articles), but this didn’t help either. The node has 3 network interfaces, and the hosts file points only to the management interface. Thank you,

1 0

I'm having problems deploying hosted-engine ovirt4.3 on oracle linux 7.9 OS.
by natchawi28＠gmail.com 29 Apr '22

29 Apr '22

I'd like to attach a picture for you to look at. message in log ======================================== TASK [ovirt.engine-setup : Run engine-setup with answerfile] changed: [localhost -> engine.testlab.local] TASK [ovirt.engine-setup : Make sure `ovirt-engine` service is running] ok: [localhost -> engine.testlab.local] TASK [ovirt.engine-setup : Check if Engine health page is up] ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost -> engine.testlab.local]: FAILED! => {"attempts": 12, "changed": false, "msg": "Failed to validate the SSL certificate for localhost:443. Make sure your managed systems have a valid CA certificate installed. You can use validate_certs=False if you do not need to confirm the servers identity but this is unsafe and not recommended. Paths checked for this platform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org, /etc/ansible. The exception msg was: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618).", "status": -1, "url": "http://localhost/ovirt-engine/services/health"} Is there anything that I need to change Or what do I need to prepare? Thank.

2 1

unable to upgrade engine to 4.4.10 from 4.4.8
by Diggy Mc 29 Apr '22

29 Apr '22

I am unable to upgrade my hosted engine from version 4.4.8 to 4.4.10. I suspect the problem is because of the obsolescence of CentOS Linux 8. DNF gives me the following error: CentOS Linux 8 - AppStream Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist This is the list of repositories on my engine: appstream CentOS Linux 8 - AppStream baseos CentOS Linux 8 - BaseOS extras CentOS Linux 8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-advanced-virtualization Advanced Virtualization packages for x86_64 ovirt-4.4-centos-ceph-pacific Ceph packages for x86_64 ovirt-4.4-centos-gluster8 CentOS-8 - Gluster 8 ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-openstack-victoria OpenStack Victoria Repository ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL powertools CentOS Linux 8 - PowerTools Your guidance on how to proceed is much appreciated. Thanks.

4 10

Cannot perform ovirt engine upgrade from ovirt 4.4.10 to 4.5 (ansible conflict)
by ralmeida＠prefecturaloja.gob.ec 29 Apr '22

29 Apr '22

OS: centos stream 8.6 after safe procedure: dnf install -y centos-release-ovirt45 dnf update -y --nobest engine-setup have many errors: nothing provides ansible-core >= 2.12.0 needed by ovirt-engine-4.5.0.5-1.el8.noarch - nothing provides scap-security-guide >= 0.1.60-4 needed by ovirt-engine-4.5.0.5-1.el8.noarch - nothing provides fapolicyd >= 1.1 needed by ovirt-engine-4.5.0.5-1.el8.noarch and i can't finish the engine upgrade... I see many sites like: https://access.redhat.com/solutions/5480561, but not work Please your help pd. logs: https://filedn.com/lYVRQ0f0QUTQVmMCo3Bk7DY/ovirt-engine-setup-2022042612332…

2 1

Q: Cluster compatibility Level and Old v4.2 Nodes
by Andrei Verovski 28 Apr '22

28 Apr '22

Hi, I have quite old nodes from early 4.x era (with CentOS 7.6, cluster compatibility 4.2 level), and oVirt Engine 4.4. 2 nodes have ovirt-release42. Upgrade to oVirt Engine 4.5 engine required cluster compatibility >= 4.3 level. Nodes have been installed with stock CentOS 7.6, not oVirt node image, their upgrade is quite problematic right now. Is it possible to upgrade to cluster compatibility 4.3 while having old 4.2 nodes? Thanks in advance. Andrei

2 1

Storage Domain cloned on iscsi storage and import into oVirt
by Gianluca Gargiulo 28 Apr '22

28 Apr '22

Hi, we have this problem: - Storage Domain iSCSI with a lot of VMs - on iSCSI SAN there is a iSCSI Target with LUN, snapshotted We need to revert only one VM from snapshot. If i revert the snapshot on LUN we revert also other VMs. If i clone the snapshot in the other LUN and attach it to another iscsi target, oVirt can't import "new" storage domain, becouse the VolumeGroupID is same, also

1 0

oVirt Engine Deployment, Networking and Nested Virtualization with VMware Fusion 12.x
by mail＠sunilpatel.co.uk 28 Apr '22

28 Apr '22

Hello, I'm just writing my experiences in case others have come across similar issues or have a similar configuration. I have a single PC, well iMac, home lab environment with VMware Fusion 12.x for Virtualisation. I have tried to setup oVirt 4.5 as a self-hosted engine, deployed on an oVirt 4.5.0 node VM (with nested virtualisation) and the engine deployment fails at this point: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get local VM IP] [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 90, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3e:36:90:88 | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.052065", "end": "2022-04-27 21:12:08.176323", "msg": "", "rc": 0, "start": "2022-04-27 21:12:08.124258", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} This seems to be the point where the oVirt Engine has gone though an initial deployment and Ansible is trying to get the IP of the ovirt engine to resume configuration and testing. I believe the VM is running on the oVirt node at this point and there is a Linux bridge between the oVirt node and engine VM. The oVirt node itself has two vNICs, one as the oVirt management network and a second unconfigured NIC to be used for Gluster storage. I access oVirt nodes and Cockpit via a "client" linux VM also on the oVirt management network. It feels like it's this Linux bridge and networking which is not working correctly and causing the deployment to fail. This could be due to the fact that I'm using a virtualised NIC and while promiscuous mode and perhaps some other features are sort-of supported, features needed for this kind of complex networking are not. This is despite the network I'm using being an internal one without the iMAC host connected. WAN connections for oVirt are via a NAT gateway/firewall VM that has the LAN side on the oVirt management network and the WAN side using a bridge with the hosts's NIC (wifi in my case). I did get similar results when I tried to set up OpenStack Neutron Networking; I could not get traffic to cross the Linux Bridge from one Compute Node VM to another. There are a small handful of results of other people coming across this same issue/error and many of them are also using nested Virtualisation either in ESXi, VirtualBox etc The Linux Bridge created by the oVirt engine deployment is (from Cockpit): virbr0Bridge 52:54:00:8F:28:3A Status 192.168.222.1/24, fe80:0:0:0:5054:ff:fe8f:283a/64, fd00:1234:5678:900:0:0:0:1/64 Carrier Yes General Connect automatically IPv4 Address 192.168.222.1/24 IPv6 Address fd00:1234:5678:900:0:0:0:1/64 Bridge Spanning tree protocol Forward delay 2 I have actually seen traffic cross this bridge while watching the stats as the engine was being deployed. If anyone has experienced this problem before and is certain it is due to having a virtualised network, then please let me know. Alternatively, if there is a workaround, that would be great, otherwise I can do more troubleshooting on request but it does feel like this is ultimately a problem related to the platform I'm using - which would not be encountered in a production environment. Thanks

1 0

Q: Non-Operational Node Hosts - Ghost Network Problem
by Andrei Verovski 28 Apr '22

28 Apr '22

Hi, I run into nasty and unexpected problem (oVirt 4.4.7.6-1.el8 ) and 2 non-operational node hosts, which seem relate to ghost network glitch. Everything worked fine for a very long time until I did the following. 1) Made a backup of several VMs which have network “CloudLink-ISP2”. 2) Moved VM disks into another node hosts, which don’t have link “CloudLink-ISP2”, and forgot (preliminary to move) to re-configure network interface (remove link to “CloudLink-ISP2”) as I did before.. 3) Now I have 2 hosts in non-operational mode which is a really big problem - there are only 3 nodes total in a cluster. I tried to fix this by adding 3rd network “CloudLink-ISP2” to each non-operational hosts, and connected ethernet interfaces to a switch. Unfortunately, it didn’t helped either because for whatever reason link did not go up. How I can remove any reference to “CloudLink-ISP2” from node11 and node14? They don’t have any VMs needed that “CloudLink-ISP2”. I edited even inactive VMs and removed “CloudLink-ISP2”. May be there is an option to ignore missing or downed links whn activating node hosts? Thanks in advance for any help. —————————— Logs: 2022-04-27 11:16:59,769+03 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [5ab20328] Host 'node14' is set to Non-Operational, it is missing the following networks: 'CloudLink-ISP2' 2022-04-27 11:16:59,790+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [5ab20328] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node14 does not comply with the cluster ClusterRiga11 networks, the following networks are missing on host: 'CloudLink-ISP2' 2022-04-27 11:16:59,884+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [55610e1e] EVENT_ID: VDS_DETECTED(13), Status of host node14 was set to NonOperational. 2022-04-27 11:16:59,907+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [5d6ef791] Host 'node14'(aa871d44-94e2-4fdb-aeb3-ca0ae8dc568f) is already in NonOperational status for reason 'NETWORK_UNREACHABLE'. SetNonOperationalVds command is skipped. 2022-04-27 11:12:26,050+03 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [5400352e] Host 'node11' is set to Non-Operational, it is missing the following networks: 'CloudLink-ISP2' 2022-04-27 11:12:26,070+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [5400352e] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node11 does not comply with the cluster ClusterRiga11 networks, the following networks are missing on host: 'CloudLink-ISP2' 2022-04-27 11:12:26,192+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [57d79e54] EVENT_ID: VDS_DETECTED(13), Status of host node11 was set to NonOperational. 2022-04-27 11:12:26,214+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [151821e3] Host 'node11'(3c854f9c-2cdd-423e-bca0-37964ba76702) is already in NonOperational status for reason 'NETWORK_UNREACHABLE'. SetNonOperationalVds command is skipped. 2022-04-27 11:51:10,539+03 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] Clearing domains data for host node14 2022-04-27 11:51:10,539+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] Host 'node14' moved to Non-Operational state because interface/s which are down are needed by required network/s in the current cluster: 'eno3 (CloudLink-ISP2)' 2022-04-27 11:51:10,569+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] EVENT_ID: VDS_SET_NONOPERATIONAL_IFACE_DOWN(603), Host node14 moved to Non-Operational state because interfaces which are down are needed by required networks in the current cluster: 'eno3 (CloudLink-ISP2)'.

2 2

renewing hosts certs when they have expired
by Nathanaël Blanchet 28 Apr '22

28 Apr '22

Hello, I have read some posts about renewing ovirt CA on the engine when it has expired with engine-setup --offline, but nothing about renewing hosts certificates when they have expired. In such a case, we can't interact anymore with hosts and vms are in an unknown state. The formal solution is to put the concerned host into maintenance and enroll certificate, but it implies to stop vms. Here are some messages we can find For those who are concerned, I wrote an ansible role following https://access.redhat.com/solutions/3532921 https://galaxy.ansible.com/natman/ovirt_renew_certs Let me know if it fits to your needs. -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

1 0