- Users - oVirt List Archives

async release for oVirt 4.4.4 is now available
by Lev Veyde 08 Feb '21

08 Feb '21

On February 8th the oVirt project released an async update to the following packages: - ovirt-release44-4.4.4.1 - ovirt-node-ng-installer ISO 4.4.4.1 (4.4.4-2021020810) - imgbased-1.2.16 Fixing the following security issues: - [BZ 1917684 <https://bugzilla.redhat.com/show_bug.cgi?id=1917684>] - CVE-2021-3156 <https://access.redhat.com/security/cve/CVE-2021-3156> sudo: Heap buffer overflow in argument parsing - [RHSA-2021:0150 <https://access.redhat.com/errata/RHSA-2021:0150>] - Multiple vulnerabilities within dnsmasq As well as, fixing the following bugs: - [BZ 1903777 <https://bugzilla.redhat.com/1903777>] - chronyd is disabled after upgrading RHV-H 4.4.2 -> 4.4.3 - [BZ 1909782 <https://bugzilla.redhat.com/1909782>] - /etc/openvswitch permissions broken after upgrade - [BZ 1921553 <https://bugzilla.redhat.com/1921553>] - RHVH upgrade to the latest 4.4.4-1 build will fail due to FileNotFoundError -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

The he_fqdn proposed for the engine VM resolves on this host - error?
by lejeczek 07 Feb '21

07 Feb '21

hi chaps, a newcomer here. I use cockpit to deploy hosted engine and I get this error/warning message: "The he_fqdn proposed for the engine VM resolves on this host" I should mention that if I remove the IP to which FQDN resolves off that iface(plain eth no vlans) then I get this: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The selected network interface is not valid"} All these errors seem bit too cryptic to me. Could you shed bit light on what is oVirt saying exactly and why it's not happy that way? many thanks, L.

4 7

Future of oVirt as RHV is converging with OpenShift
by andrew.prowse＠gmail.com 06 Feb '21

06 Feb '21

What is the future of oVirt with RHV 4.4 being the last RHV release? - see https://access.redhat.com/support/policy/updates/rhev With the release of RHV 4.4 Red Hat continues to invest in and support customers with a production-ready virtualization portfolio. The latest addition to this portfolio is OpenShift with OpenShift Virtualization, which provides continuity and roadmap delivery for the KVM-based virtualization stack currently managed by RHV. Moving forward the RHV management feature set will be converged with OpenShift and OpenShift Virtualization providing customers with requirements for containers and VMs a migration path and a common platform for deploying and managing both.

5 7

[ANN] oVirt 4.4.5 Fourth Release Candidate is now available for testing
by Lev Veyde 05 Feb '21

05 Feb '21

oVirt 4.4.5 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Fourth Release Candidate for testing, as of February 4th, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://www.ovirt.org/release/4.4.5/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.5/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

uploading ang .OVA image
by Ariez Ahito 04 Feb '21

04 Feb '21

hi guys, i just want to ask if you can just upload an .OVA file to ovirt just like uploading ISO? without setting up virt-v2v and export domain? thanks

3 2

Upgrade from 4.4.3 to 4.4.4 (oVirt Node) - vdsmd.service/start failed with result 'dependency'
by Marco Fais 04 Feb '21

04 Feb '21

Hi all, I have just upgraded one of my oVirt nodes from 4.4.3 to 4.4.4. After the reboot, the 4.4.4 image is correctly loaded but vdsmd is not starting due to this error: vdsmd.service: Job vdsmd.service/start failed with result 'dependency'. Looks like it has a dependency on mom-vdsm, and this as well has a dependency issue: mom-vdsm.service: Job mom-vdsm.service/start failed with result 'dependency'. After some investigation looks like mom-vdsm has a dependency on ovsdb-server, and this is the unit creating the problem: ovs-delete-transient-ports.service: Starting requested but asserts failed. Assertion failed for Open vSwitch Delete Transient Ports Failed to start Open vSwitch Database Unit. Details below: -- Unit ovsdb-server.service has begun starting up. Dec 24 12:21:57 LAB-CNVirt-H04.ngv.eircom.net chown[13658]: /usr/bin/chown: cannot access '/var/run/openvswitch': No such file or directory Dec 24 12:21:57 LAB-CNVirt-H04.ngv.eircom.net ovs-ctl[13667]: /etc/openvswitch/conf.db does not exist ... (warning). Dec 24 12:21:57 LAB-CNVirt-H04.ngv.eircom.net ovsdb-tool[13714]: ovs|00001|lockfile|WARN|/etc/openvswitch/.conf.db.~lock~: failed to open lock file: Permission denied Dec 24 12:21:57 LAB-CNVirt-H04.ngv.eircom.net ovs-ctl[13667]: Creating empty database /etc/openvswitch/conf.db ovsdb-tool: I/O error: /etc/openvswitch/conf.db: failed to lock lockfile (Resource temporarily unavailable) Dec 24 12:21:57 LAB-CNVirt-H04.ngv.eircom.net ovsdb-tool[13714]: ovs|00002|lockfile|WARN|/etc/openvswitch/.conf.db.~lock~: failed to lock file: Resource temporarily unavailable Dec 24 12:21:57 LAB-CNVirt-H04.ngv.eircom.net ovs-ctl[13667]: [FAILED] Dec 24 12:21:57 LAB-CNVirt-H04.ngv.eircom.net systemd[1]: ovsdb-server.service: Control process exited, code=exited status=1 Dec 24 12:21:57 LAB-CNVirt-H04.ngv.eircom.net systemd[1]: ovsdb-server.service: Failed with result 'exit-code'. -- Subject: Unit failed Any suggestions? Thanks, Marco

4 6

ovirt AD issue
by Jason Keltz 04 Feb '21

04 Feb '21

A while back, I had reconfigured my oVirt engine to auth based on my Samba AD server, and everything was working perfectly fine. oVirt version 4.3.10.4-1. Today, I tried to login with my account into engine and I see: server_error: The connection reader was unable to successfully complete TLS negotiation: SSLHandshakeException(sun.security.validator.ValidatorException: No trusted certificate found), ldapSDKVersion=4.0.7, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58 I recently added a secondary domain controller with Samba, and I realize now that there is an error. Since I didn't pre-initialize samba with a TLS certificate, it generated a new CA, and certificate and key for the second server. Since I'm not using the same CA as the first server, ovirt engine (which only has the CA of the first server) won't be able to talk to the second server... no problem.... I will fix that eventually. However, when I re-ran "ovirt-engine-extension-aaa-ldap-setup", and followed the exact steps I did before, ovirt is connecting to the first server, failing with the above error, then connecting to the second server, and the same error. The CA hasn't changed for the first server, nor has the certificate/key. I verified that the CA certificate that I am giving ovirt is matching with the exact CA certificate of the first server. How can I debug further? Jason.

1 0

Recovery from power outage
by Roderick Mooi 04 Feb '21

04 Feb '21

Hi! We had a power outage and all our servers (oVirt hosts) went down. When they started up neither the hosted-engine nor VMs were started. hosted-engine --vm-status says: You must run deploy first I tried running deploy with various options but ultimately get stuck at: The Host ID is already known. Is this a re-deployment on an additional host that was previously set up (Yes, No)[Yes]? ... [ ERROR ] Failed to execute stage 'Closing up': <urlopen error [Errno 113] No route to host> OR The specified storage location already contains a data domain. Is this an additional host setup (Yes, No)[Yes]? No [ ERROR ] Re-deploying the engine VM over a previously (partially) deployed system is not supported. Please clean up the storage device or select a different one and retry. NOTES: 1. This is oVirt v3.6 (legacy install, I know...) 2. We do have daily engine backups (.bak files) [till the day the power failed] Any advice/assistance appreciated. Thanks! Roderick

3 13

self hosted-engine deploy fails on network
by Nardus Geldenhuys 03 Feb '21

03 Feb '21

Hi oVirt land Hope you are well. Running into this issue, I hope you can help. Centos7 and it is updated. Ovirt 4.3, latest packages. My network config: [root@mob-r1-d-ovirt-aa-1-01 ~]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 00:90:fa:c2:d2:48 brd ff:ff:ff:ff:ff:ff 3: ens1f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether 00:90:fa:c2:d2:48 brd ff:ff:ff:ff:ff:ff 4: enp11s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:90:fa:c2:d2:50 brd ff:ff:ff:ff:ff:ff 5: enp11s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:90:fa:c2:d2:54 brd ff:ff:ff:ff:ff:ff 21: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:90:fa:c2:d2:48 brd ff:ff:ff:ff:ff:ff inet6 fe80::290:faff:fec2:d248/64 scope link valid_lft forever preferred_lft forever 22: bond0.1131@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:90:fa:c2:d2:48 brd ff:ff:ff:ff:ff:ff inet 172.18.206.184/23 brd 172.18.207.255 scope global bond0.1131 valid_lft forever preferred_lft forever inet6 fe80::290:faff:fec2:d248/64 scope link valid_lft forever preferred_lft forever [root@mob-r1-d-ovirt-aa-1-01 network-scripts]# cat ifcfg-bond0 BONDING_OPTS='mode=1 miimon=100' TYPE=Bond BONDING_MASTER=yes PROXY_METHOD=none BROWSER_ONLY=no IPV6INIT=no NAME=bond0 UUID=c11ef6ef-794f-4683-a068-d6338e5c19b6 DEVICE=bond0 ONBOOT=yes [root@mob-r1-d-ovirt-aa-1-01 network-scripts]# cat ifcfg-bond0.1131 DEVICE=bond0.1131 VLAN=yes ONBOOT=yes MTU=1500 IPADDR=172.18.206.184 NETMASK=255.255.254.0 GATEWAY=172.18.206.1 BOOTPROTO=none MTU=1500 DEFROUTE=yes NM_CONTROLLED=no IPV6INIT=yes DNS1=172.20.150.10 DNS2=172.20.150.11 I get the following error: [ INFO ] TASK [ovirt.hosted_engine_setup : Generate output list] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Validate selected bridge interface if management bridge does not exists] [ INFO ] skipping: [localhost] Please indicate a nic to set ovirtmgmt bridge on: (bond0, bond0.1131) [bond0.1131]: Please specify which way the network connectivity should be checked (ping, dns, tcp, none) [dns]: .. .. .. .. .. [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Validate selected bridge interface if management bridge does not exists] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The selected network interface is not valid"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook [ INFO ] Stage: Clean up And if I create the ifcfg-ovirtmgmt as a bridge it fails later. What is the correct network setup for my bond configuration to do a self hosted-engine setup ? Regards Nar

2 1

Changes between Node NG 4.4.3 and 4.4.4
by Shantur Rathore 03 Feb '21

03 Feb '21

Hi, I have a node 4.4.3 install and it works perfectly for PCI passthrough. After I upgraded to Node NG 4.4.4 the PCI passthrough leads to server resets. There are no logs in the kernel messages just before reset apart from vfio-pci enabling the device. So, I assume there is some change related to the kernel or vfio-pci driver in the newer 4.4.4 version. How / Where can I see the differences between Node NG releases? Thanks, Shantur

1 1