November 2023 - Users - oVirt List Archives

Please, Please Help - New oVirt Install/Deployment Failing - "Host is not up..."
by Matthew J Black 18 Jan '24

18 Jan '24

Hi Everyone, Could someone please help me - I've been trying to do an install of oVirt for *weeks* (including false starts and self-inflicted wounds/errors) and it is still not working. My setup: - oVirt v4.5.3 - A brand new fresh vanilla install of RockyLinux 8.6 - all working AOK - 2*NICs in a bond (802.3ad) with a couple of sub-Interfaces/VLANs - all working AOK - All relevant IPv4 Address in DNS with Reverse Lookups - all working AOK - All relevant IPv4 Address in "/etc/hosts" file - all working AOK - IPv6 (using "method=auto" in the interface config file) enabled on the relevant sub-Interface/VLAN - I'm not using IPv6 on the network, only IPv4, but I'm trying to cover all the bases. - All relevant Ports (as per the oVirt documentation) set up on the firewall - ie firewall-cmd --add-service={{ libvirt-tls | ovirt-imageio | ovirt-vmconsole | vdsm }} - All the relevant Repositories installed (ie RockyLinux BaseOS, AppStream, & PowerTools, and the EPEL, plus the ones from the oVirt documentation) I have followed the oVirt documentation (including the special RHEL-instructions and RockyLinux-instructions) to the letter - no deviations, no special settings, exactly as they are written. All the dnf installs, etc, went off without a hitch, including the "dnf install centos-release-ovirt45", "dnf install ovirt-engine-appliance", and "dnf install ovirt-hosted-engine-setup" - no errors anywhere. Here is the results of a "dnf repolist": - appstream Rocky Linux 8 - AppStream - baseos Rocky Linux 8 - BaseOS - centos-ceph-pacific CentOS-8-stream - Ceph Pacific - centos-gluster10 CentOS-8-stream - Gluster 10 - centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch - centos-opstools CentOS-OpsTools - collectd - centos-ovirt45 CentOS Stream 8 - oVirt 4.5 - cs8-extras CentOS Stream 8 - Extras - cs8-extras-common CentOS Stream 8 - Extras common packages - epel Extra Packages for Enterprise Linux 8 - x86_64 - epel-modular Extra Packages for Enterprise Linux Modular 8 - x86_64 - ovirt-45-centos-stream-openstack-yoga CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository - ovirt-45-upstream oVirt upstream for CentOS Stream 8 - oVirt 4.5 - powertools Rocky Linux 8 - PowerTools So I kicked-off the oVirt deployment with: "hosted-engine --deploy --4 --ansible-extra-vars=he_offline_deployment=true". I used "--ansible-extra-vars=he_offline_deployment=true" because without that flag I was getting "DNF timout" issues (see my previous post `Local (Deployment) VM Can't Reach "centos-ceph-pacific" Repo`). I answer the defaults to all of questions the script asked, or entered the deployment-relevant answers where appropriate. In doing this I double-checked every answer before hitting <Enter>. Everything progressed smoothly until the deployment reached the "Wait for the host to be up" task... which then hung for more than 30 minutes before failing. From the ovirt-hosted-engine-setup... log file: - 2022-10-20 17:54:26,285+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"} I checked the following log files and found all of the relevant ERROR lines, then checked several 10s of proceeding and succeeding lines trying to determine what was going wrong, but I could not determine anything. - ovirt-hosted-engine-setup... - ovirt-hosted-engine-setup-ansible-bootstrap_local_vm... - ovirt-hosted-engine-setup-ansible-final_clean... - not really relevant, I believe I can include the log files (or the relevant parts of the log files) if people want - but that are very large: several 100 kilobytes each. I also googled "oVirt Host is not up" and found several entries, but after reading them all the most relevant seems to be a thread from these mailing list: `Install of RHV 4.4 failing - "Host is not up, please check logs, perhaps also on the engine machine"` - but this seems to be talking about an upgrade and I didn't gleam anything useful from it - I could, of course, be wrong about that. So my questions are: - Where else should I be looking (ie other log files, etc, and possible where to find them)? - Does anyone have any idea why this isn't working? - Does anyone have a work-around (including a completely manual process to get things working - I don't mind working in the CLI with virsh, etc)? - What am I doing wrong? Please, I'm really stumped with this, and I really do need help. Cheers Dulux-Oz

8 22

Configure OVN for oVirt failing - vdsm.tool.ovn_config.NetworkNotFoundError: hostname
by huw.m＠twinstream.com 13 Jan '24

13 Jan '24

Hello, When installing the self-hosted engine using rocky 9 as a host (using nightly builds), the install gets as far as running the below ansible task from ovirt-engine - name: Configure OVN for oVirt ansible.builtin.command: > vdsm-tool ovn-config {{ ovn_central }} {{ ovn_tunneling_interface }} {{ ovn_host_fqdn }} This command gets executed as vdsm-tool ovn-config 192.168.57.4 hostname.my.project.com and fails with error "stderr" : "Traceback (most recent call last):\n File \"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\", line 117, in get_network\n return networks[net_name]\nKeyError: 'virt-1.local.hyp.twinstream.com'\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"/usr/bin/vdsm-tool\", line 195, in main\n return tool_command[cmd][\"command\"](*args)\n File \"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\", line 63, in ovn_config\n ip_address = get_ip_addr(get_network(network_caps(), net_name))\n File \"/usr/lib/python3.9/site-packages/vdsm/tool/ovn_config.py\", line 119, in get_network\n raise NetworkNotFoundError(net_name)\nvdsm.tool.ovn_config.NetworkNotFoundError: hostname.my.project.com" Running `vdsm-tool list-nets` on the host gives an empty list. `ip a` gives 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6d:16:65 brd ff:ff:ff:ff:ff:ff altname enp0s6 altname ens6 inet 192.168.121.29/24 brd 192.168.121.255 scope global dynamic noprefixroute eth0 valid_lft 2482sec preferred_lft 2482sec inet6 fe80::5054:ff:fe6d:1665/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:6b:f4:7b brd ff:ff:ff:ff:ff:ff altname enp0s7 altname ens7 inet 192.168.56.151/24 brd 192.168.56.255 scope global noprefixroute eth1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe6b:f47b/64 scope link valid_lft forever preferred_lft forever 4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 52:54:00:8f:40:45 brd ff:ff:ff:ff:ff:ff altname enp0s8 altname ens8 5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:2f:27:9d brd ff:ff:ff:ff:ff:ff altname enp0s9 altname ens9 6: eth4: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bondstorage state UP group default qlen 1000 link/ether 52:54:00:b8:9b:d7 brd ff:ff:ff:ff:ff:ff altname enp0s10 altname ens10 7: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:c2:9a:bd brd ff:ff:ff:ff:ff:ff altname enp0s11 altname ens11 8: eth6: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq_codel master bondvm state UP group default qlen 1000 link/ether 52:54:00:ed:f7:cc brd ff:ff:ff:ff:ff:ff altname enp0s12 altname ens12 9: eth7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:de:8a:48 brd ff:ff:ff:ff:ff:ff altname enp0s13 altname ens13 10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:8f:40:45 brd ff:ff:ff:ff:ff:ff inet 192.168.57.4/24 brd 192.168.57.255 scope global noprefixroute bond0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe8f:4045/64 scope link valid_lft forever preferred_lft forever 11: bondvm: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:ed:f7:cc brd ff:ff:ff:ff:ff:ff inet6 fe80::5054:ff:feed:f7cc/64 scope link valid_lft forever preferred_lft forever 12: bondstorage: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:b8:9b:d7 brd ff:ff:ff:ff:ff:ff inet 192.168.59.4/24 brd 192.168.59.255 scope global noprefixroute bondstorage valid_lft forever preferred_lft forever inet6 fe80::5054:ff:feb8:9bd7/64 scope link valid_lft forever preferred_lft forever 13: bondvm.20@bondvm: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:ed:f7:cc brd ff:ff:ff:ff:ff:ff inet6 fe80::5054:ff:feed:f7cc/64 scope link valid_lft forever preferred_lft forever 15: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:b2:5f:e2 brd ff:ff:ff:ff:ff:ff inet 192.168.222.1/24 brd 192.168.222.255 scope global virbr0 valid_lft forever preferred_lft forever 16: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master virbr0 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:34:3d:ea brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe34:3dea/64 scope link valid_lft forever preferred_lft forever 47: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 6e:27:5f:fa:e3:3a brd ff:ff:ff:ff:ff:ff 48: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 12:7c:d9:2e:cf:26 brd ff:ff:ff:ff:ff:ff 49: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether a2:35:6e:5e:4c:60 brd ff:ff:ff:ff:ff:ff bond0 was selected as the ovirtmgmt bridge NIC. It currently only has one member interface eth2 using balance-xor. In the ovirt management console I can the see host in a down state and given the rest of the playbook ran which requires ssh connectivity between hosted-engine and host, I believe the network is generally setup correctly. No other immediate errors I can. As vdsm-tool ovn-config expects a network to exist with value of the hostname, what is meant to be creating this on the host? Thanks, Huw

2 3

how to renew expired ovirt node vdsm cert manually ?
by dhanaraj.ramesh＠yahoo.com 11 Jan '24

11 Jan '24

below are the steps to renew the expired vdsm cert of ovirt node # To check CERT expired # openssl x509 -in /etc/pki/vdsm/certs/vdsmcert.pem -noout -dates 1. Backup vdsm folder # cd /etc/pki # mv vdsm vdsm.orig # mkdir vdsm ; chown vdsm:kvm vdsm # cd vdsm # mkdir libvirt-vnc certs keys libvirt-spice libvirt-migrate # chown vdsm:kvm libvirt-vnc certs keys libvirt-spice libvirt-migrate 2. Regenerate cert & keys # vdsm-tool configure --module certificates 3. Copy the cert to destination location chmod 440 /etc/pki/vdsm/keys/vdsmkey.pem chown root /etc/pki/vdsmcerts/*pem chmod 644 /etc/pki/vdsmcerts/*pem cp /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-spice/ca-cert.pem cp /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-spice/server-key.pem cp /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-spice/server-cert.pem cp /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-vnc/ca-cert.pem cp /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-vnc/server-key.pem cp /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-vnc/server-cert.pem cp -p /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/libvirt-migrate/ca-cert.pem cp -p /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/vdsm/libvirt-migrate/server-key.pem cp -p /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/vdsm/libvirt-migrate/server-cert.pem chown root:qemu /etc/pki/vdsm/libvirt-migrate/server-key.pem cp -p /etc/pki/vdsm.orig/keys/libvirt_password /etc/pki/vdsm/keys/ mv /etc/pki/libvirt/clientcert.pem /etc/pki/libvirt/clientcert.pem.orig mv /etc/pki/libvirt/private/clientkey.pem /etc/pki/libvirt/private/clientkey.pem.orig mv /etc/pki/CA/cacert.pem /etc/pki/CA/cacert.pem.orig cp -p /etc/pki/vdsm/certs/vdsmcert.pem /etc/pki/libvirt/clientcert.pem cp -p /etc/pki/vdsm/keys/vdsmkey.pem /etc/pki/libvirt/private/clientkey.pem cp -p /etc/pki/vdsm/certs/cacert.pem /etc/pki/CA/cacert.pem 3. cross check the backup folder /etc/pki/vdsm.orig vs /etc/pki/vdsm # refer to /etc/pki/vdsm.orig/*/ and set the correct owner & group permission in /etc/pki/vdsm/*/ 4. restart services # Make sure both services are up systemctl restart vdsmd libvirtd

5 4

Grafana - Origin Not Allowed
by Maton, Brett 14 Dec '23

14 Dec '23

oVirt 4.5.0.8-1.el8 I tried to connect to grafana via the monitoring portal link from the dash and all panels are failing to display any data with varying error messages, but all include 'Origin Not Allowed' I navigated to Data Sources and ran a test on the PostgreSQL connection (localhost) which threw the same Origin Not Allowed error message. Any suggestions?

6 8

Installing MS server 2022 on Software Version:4.5.3.2-1.el8
by antonio.riggio＠mail.com 05 Dec '23

05 Dec '23

Im pretty knew to ovirt we are running in our env . I am having trouble getting MS server 2022 installed I get error Boot0002 "UFEI QUMU QEMU HARDISK

2 2

Upgrading manger from 4.4 to 4.5 - repo/dependency issues
by jeremy_tourville＠hotmail.com 29 Nov '23

29 Nov '23

My system is Rocky 8.9 I am running into some issues with upgrading. I am following the guide - https://www.ovirt.org/documentation/upgrade_guide/index.html#Upgrading_the_… I also followed https://www.ovirt.org/download/install_on_rhel.html and took care of the Rocky sepecific section along with the "Common to RHEL 8.6 and derivatives" When running the upgrade 3.2. Updating the oVirt Engine, step #3 engine-setup fails with: [ ERROR ] DNF Problem 1: package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2. 14, but none of the providers can be installed - cannot install the best candidate for the job - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 2: problem with installed package ovirt-engine-4.4.10.7-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch - cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 3: problem with installed package ansible-runner-service-1.0.7-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch - cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 4: problem with installed package python3-ansible-runner-1.4.6-1.el8.noarch - cannot install the best update candidate for package python3-ansible-runner-1.4.6-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering [ INFO ] DNF Performing DNF transaction rollback [ ERROR ] Failed to execute stage 'Environment customization': Problem 1: package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2. 14, but none of the providers can be installed - cannot install the best candidate for the job - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 2: problem with installed package ovirt-engine-4.4.10.7-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch - cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 3: problem with installed package ansible-runner-service-1.0.7-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-4.4.10.7-1.el8.noarch - cannot install the best update candidate for package ansible-runner-service-1.0.7-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering Problem 4: problem with installed package python3-ansible-runner-1.4.6-1.el8.noarch - cannot install the best update candidate for package python3-ansible-runner-1.4.6-1.el8.noarch - package ovirt-engine-4.5.3.1-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.3.2-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, bu t none of the providers can be installed - package ovirt-engine-4.5.4-1.el8.noarch from centos-ovirt45 requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.1.3-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.2-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.4-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package ovirt-engine-4.5.2.5-1.el8.noarch from ovirt-45-upstream requires postgresql-jdbc >= 42.2.14, but none of the providers can be installed - package postgresql-jdbc-42.2.14-0.1.el8_6.noarch from centos-ovirt45 is filtered out by exclude filte ring - package postgresql-jdbc-42.2.27-1.el8.noarch from centos-ovirt45 is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from appstream is filtered out by exclude filtering - package postgresql-jdbc-42.2.14-2.el8.noarch from devel is filtered out by exclude filtering [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20231124095827-ytworo.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20231124100101-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed I recall running into a similar issue before with modules that were causing upgrade issues. Sometimes the easiest thing is to reset a module, but I am not sure in this case. Here is what repos I have on my system: [root@engine ~]# dnf repolist repo id repo name appstream Rocky Linux 8 - AppStream baseos Rocky Linux 8 - BaseOS centos-ceph-pacific CentOS-8-stream - Ceph Pacific centos-gluster10 CentOS-8-stream - Gluster 10 centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch centos-ovirt45 CentOS Stream 8 - oVirt 4.5 cs8-extras CentOS Stream 8 - Extras cs8-extras-common CentOS Stream 8 - Extras common packages devel Rocky Linux 8 - Devel WARNING! FOR BUILDROOT AND KOJI USE epel-debuginfo Extra Packages for Enterprise Linux 8 - x86_64 - Debug epel-modular Extra Packages for Enterprise Linux Modular 8 - x86_64 - RETIRED epel-modular-debuginfo Extra Packages for Enterprise Linux Modular 8 - x86_64 - Debug - RETIRED epel-modular-source Extra Packages for Enterprise Linux Modular 8 - x86_64 - Source - RETIRED epel-source Extra Packages for Enterprise Linux 8 - x86_64 - Source epel-testing Extra Packages for Enterprise Linux 8 - Testing - x86_64 epel-testing-debuginfo Extra Packages for Enterprise Linux 8 - Testing - x86_64 - Debug epel-testing-modular Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - RETIRED epel-testing-modular-debuginfo Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - Debug - RETIRED epel-testing-modular-source Extra Packages for Enterprise Linux Modular 8 - Testing - x86_64 - Source - RETIRED epel-testing-source Extra Packages for Enterprise Linux 8 - Testing - x86_64 - Source ha Rocky Linux 8 - HighAvailability ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-centos-advanced-virtualization CentOS-8 - Advanced Virtualization ovirt-4.4-centos-ceph-pacific CentOS-8-stream - Ceph Pacific ovirt-4.4-centos-gluster8 CentOS-8-stream - Gluster 8 ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch ovirt-4.4-centos-openstack-victoria CentOS-8 - OpenStack victoria ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-opstools-vault CentOS-8 - OpsTools - collectd - vault 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-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL ovirt-45-centos-stream-openstack-yoga CentOS Stream 8 - oVirt 4.5 - OpenStack Yoga Repository ovirt-45-upstream oVirt upstream for CentOS Stream 8 - oVirt 4.5 powertools Rocky Linux 8 - PowerTools Can anyone advise the steps to get this system to upgrade as expected?

5 7

Cannot successfully import Windows vm to new ovirt deployment
by netracerx＠mac.com 29 Nov '23

29 Nov '23

I am running into an issue that, from what little Google-fu I've been able to use, should be solved in oVirt 4.5. I'm trying to import WS2019 VMs from ESXi 7 as OVFs or even OVAs. But when I do the import and set the OS to Windows Server 2019 x64 in the admin portal, I get the error "Invalid time zone for the given OS type ". If I leave it at Other OS, the import fails with event ID 1153. I've been banging my head against this for over a week (previously couldn't get the management VM to complete setup), so any guidance is appreciated. Let me know what to pull to help me pin this down? BTW, yes this is a self hosted install as a nested VM on ESXi. Kinda have to right now to test everything (easiest for me over doing a bare metal on my old PowerEdge 2900 at the moment). Running CentOS 9 Stream.

9 37

I added a new host not show interface network
by stevenmendoza2103＠gmail.com 27 Nov '23

27 Nov '23

When I add a new host and I want to assign a logical network to the host interface, the host interface does not appear and I cannot assign the logical network. And it gives me an alert that the installation failed and has an item that says Host has not default route.

1 0

Trying to install MS server 2022 on Software Version:4.5.3.2-1.el8 Boot0002 "UFEI QEMU QEMU HARDDRISK " from pciRoot (0x0) ERROR
by antonio.riggio＠mail.com 27 Nov '23

27 Nov '23

Are there any tricks to install 2022 server on ovirt I see its on the dropdown list . When I boot the iso I get failed to loade Boot0002 "UFEI QEMU QEMU HARDDRISK " from pciRoot (0x0) I tried the different bios options too and that didnt work. Im pretty new to Ovirt so just trying to see if anyone has a trick getting this to work The iso works as I am able to install it in vmware thank you

1 0

Ovirt API: get guest current user
by Giulio Casella 22 Nov '23

22 Nov '23

Hi, is there a way to retrieve user currently logged in on a guest using API calls? I see such information in database (specifically in vm_dynamic table), but nothing in API docs. Any hints? TIA, gc

1 0