- Users - oVirt List Archives

Cannot restart ovirt after massive failure.
by Gilboa Davara 18 Jan '24

18 Jan '24

Hello all, During the night, one of my (smaller) setups, a single node self hosted engine (localhost NFS) crashed due to what-looks-like a massive disk failure (Software RAID6, with 10 drives + spare). After a reboot, I let the RAID resync with a fresh drive) and went on to start oVirt. However, no such luck. Two issues: 1. ovirt-ha-broker fails due to broken hosted engine state (log attached). 2. ovirt-ha-agent fails due to network test (tcp) even though both remote-host and DNS servers are active. (log attached). Two questions: 1. Can I somehow force the agent to disable the network liveliness test? 2. Can I somehow force the broker to rebuild / fix the hosted engine state? - Gilboa

4 17

Cannot open Vm Console
by Vittorio 18 Jan '24

18 Jan '24

I got few Vm on my ovirte nodes, but i cant acess to console. When i downloaded it, the error is the following : "Failed to complete haandshake Errore in the pull function."

2 1

VDSM Command DetachStorageDomainVDS Failed
by Matthew J Black 18 Jan '24

18 Jan '24

Hi All, So after having an oVirt cluster crash (no data loss (at this stage), thankfully) and rebuilding from scratch, I'm trying to import the old Storage Domains. I've been successful with three (automatically "detaching" from the old, now non-existent hosts) but one is giving me the following error from the hosted-engine GUI: ~~~ VDSM command DetachStorageDomainVDS failed: Cannot acquire host id: ('e311ddf1-7f2c-49ef-a618-050d9a2b947f', SanlockException(19, 'Sanlock lockspace add failure', 'No such device')) ~~~ I am going to assume ("make an ass out for you and me") that I can run the required command from the cli with a "-force" flag (I hope), so my Q is: What is the command, because I can't seem to find it in any doco (most probably because I'm old and my eyes are feeble :-) ). Any help gratefully appreciated - FTR: that particular Storage Domain have a bunch of VM Images on it which I'd rather import/recover than have to create from scratch. Cheers Dulux-Oz

1 0

Deployment Error: Host is not up - Looking For Some Advice/Pointers
by Matthew J Black 18 Jan '24

18 Jan '24

Hi All, So, on a fresh install on RL v9.3, we're getting a `Host is not up, please check logs, perhaps also on the engine machine` error. This comes up right after the 20min timeout (the 120sec * 10 one). No, the hosted-engine is not deployed (ie hosted-engine --check-deployed). Obviously I need to check the logs, but which ones in particular (the hosted-engine-setup logs, obviously, but which other ones), where are they if the hosted-engine is not running, and, in an effort to narrow down the volume of info to a more manageable level, what should I be looking for? Thanks in advance

1 1

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

ovirt node ng 4.5.5 fresh install fails
by Levi Wilbert 17 Jan '24

17 Jan '24

I'm attempting to update our oVirt cluster to 4.5.5 from 4.5.4, running oVirt Node NG on the hosts. When I tried updating a host through the oVirt Manager GUI, after the host reboots, it fails to start up and goes into emergency recovery mode: [ 4.534872] localhost systemd[1]: Reached target Local File Systems. [ 4.535119] localhost systemd[1]: Reached target System Initialization. [ 4.535343] localhost systemd[1]: Reached target Basic System. [ 4.536759] localhost systemd[1]: Started Hardware RNG Entropy Gatherer Daemon. [ 4.541801] localhost rngd[1512]: Disabling 7: PKCS11 Entropy generator (pkcs11) [ 4.541801] localhost rngd[1512]: Disabling 5: NIST Network Entropy Beacon (nist) [ 4.541801] localhost rngd[1512]: Disabling 9: Qrypt quantum entropy beacon (qrypt) [ 4.541801] localhost rngd[1512]: Initializing available sources [ 4.542073] localhost rngd[1512]: [hwrng ]: Initialization Failed [ 4.542073] localhost rngd[1512]: [rdrand]: Enabling RDSEED rng support [ 4.542073] localhost rngd[1512]: [rdrand]: Initialized [ 4.542073] localhost rngd[1512]: [jitter]: JITTER timeout set to 5 sec [ 4.582381] localhost rngd[1512]: [jitter]: Initializing AES buffer [ 8.309063] localhost rngd[1512]: [jitter]: Enabling JITTER rng support [ 8.309063] localhost rngd[1512]: [jitter]: Initialized [ 133.884355] localhost dracut-initqueue[1095]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 133.885349] localhost dracut-initqueue[1095]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-id\x2fmd-uuid-3f47cad8:fecb96ea:0ea37615:4e5dec4e.sh: "[ -e "/dev/disk/by-id/md-uuid-3f47cad8:fecb96ea:0ea37615:4e5dec4e" ]" [ 133.886485] localhost dracut-initqueue[1095]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-id\x2fmd-uuid-d446b801:d515c112:116ff07f:9ae52466.sh: "[ -e "/dev/disk/by-id/md-uuid-d446b801:d515c112:116ff07f:9ae52466" ]" [ 133.887619] localhost dracut-initqueue[1095]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fonn\x2fovirt-node-ng-4.5.5-0.20231130.0+1.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup(a)*.service 2>/dev/null; then [ 133.887619] localhost dracut-initqueue[1095]: [ -e "/dev/onn/ovirt-node-ng-4.5.5-0.20231130.0+1" ] [ 133.887619] localhost dracut-initqueue[1095]: fi" [ 133.888667] localhost dracut-initqueue[1095]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fonn\x2fswap.sh: "[ -e "/dev/onn/swap" ]" [ 133.890050] localhost dracut-initqueue[1095]: Warning: dracut-initqueue: starting timeout scripts [ 133.969228] localhost dracut-initqueue[7366]: Scanning devices md126p2 for LVM logical volumes onn/ovirt-node-ng-4.5.5-0.20231130.0+1 [ 133.969228] localhost dracut-initqueue[7366]: onn/swap [ 134.001560] localhost dracut-initqueue[7366]: onn/ovirt-node-ng-4.5.5-0.20231130.0+1 thin [ 134.001560] localhost dracut-initqueue[7366]: onn/swap linear [ 134.014259] localhost dracut-initqueue[7381]: /etc/lvm/profile/imgbased-pool.profile: stat failed: No such file or directory [ 134.532608] localhost dracut-initqueue[7381]: Check of pool onn/pool00 failed (status:64). Manual repair required! I then attempted installing the oVirt Node NG 4.5.5 iso to a USB stick and tried installing that way, however, after going through the GUI and setting up storage, network, hostname, etc, the install fails shortly after clicking "Begin". 22:11:32,671 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:blivet:executing action: [468] destroy device lvmthinlv onn-var_log_audit (id 216) 22:11:32,672 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet: LVMLogicalVolumeDevice.destroy: onn-var_log_audit ; status: False ; 22:11:32,673 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet: LVMLogicalVolumeDevice.teardown: onn-var_log_audit ; status: False ; controllable: False ; 22:11:32,674 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet: LVMVolumeGroupDevice.setup_parents: name: onn ; orig: True ; 22:11:32,674 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet: PartitionDevice.setup: Volume0_0p2 ; orig: True ; status: True ; controllable: True ; 22:11:32,675 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet: LVMPhysicalVolume.setup: device: /dev/md/Volume0_0p2 ; type: lvmpv ; status: False ; 22:11:32,676 WARNING org.fedoraproject.Anaconda.Modules.Storage:DEBUG:blivet: LVMLogicalVolumeDevice._destroy: onn-var_log_audit ; status: False ; 22:11:32,676 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:program:Running [97] lvm lvremove --yes onn/var_log_audit --config= log {level=7 file=/tmp/lvm.log syslog=0} --devices=/dev/md/Volume0_0p2 ... 22:11:33,104 ERR rsyslogd:imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Operation not permitted [v8.2310.0-3.el9 try https://www.rsyslog.com/e/2433 ] 22:11:33,105 ERR rsyslogd:imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Operation not permitted [v8.2310.0-3.el9 try https://www.rsyslog.com/e/2433 ] 22:11:33,105 ERR rsyslogd:imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Operation not permitted [v8.2310.0-3.el9 try https://www.rsyslog.com/e/2433 ] 22:11:33,106 ERR rsyslogd:imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Operation not permitted [v8.2310.0-3.el9 try https://www.rsyslog.com/e/2433 ] 22:11:33,106 ERR rsyslogd:imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Operation not permitted [v8.2310.0-3.el9 try https://www.rsyslog.com/e/2433 ] 22:11:33,107 ERR rsyslogd:imjournal: open() failed for path: '/var/lib/rsyslog/imjournal.state.tmp': Operation not permitted [v8.2310.0-3.el9 try https://www.rsyslog.com/e/2433 ] 22:11:33,309 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:program:stdout[97]: 22:11:33,310 WARNING org.fedoraproject.Anaconda.Modules.Storage:INFO:program:stderr[97]: /etc/lvm/profile/imgbased-pool.profile: stat failed: No such file or directory 22:11:33,310 WARNING org.fedoraproject.Anaconda.Modules.Storage: Check of pool onn/pool00 failed (status:64). Manual repair required! I'm wondering if it has to do with installing oVirt node on a RAID mirror?

1 0

Migrating from a self hosted engine to standalone
by redhat＠intheoutback.com 17 Jan '24

17 Jan '24

Hi, I am in the process of moving our oVirt environment from a self hosted engine to a standalone engine on it's own HW. I have Googled and found a procedure for standalone > self hosted, but not the other way around. My current situation is that I have 5 locations running oVirt 4.3 with 3 to 4 hypervisors and iSCSI storage backend, with a self hosted engine. All these locations are operational and short a downtime is acceptable if a must, losing a VM is NOT good. I also have 1 oVirt environment 4.3 with 2 hypervisors and iSCSI backend that is my QA/Test. All my networks are on internal networks with no outside world connections. Most importantly, we are also looking at upgrading from 4.3 to 4.4 I have not found any straightforward way to migrate from self hosted to standalone. My current plan is to do the following. 1) Create a new 4.4 standalone engine 2) Remove one hypervisor from the 4.3 cluster 3) Kickstart the hypervisor to RHEL 8.8 and configure ready for oVirt 4.4 4) Add the new host to the standalone engine. 5) Shutdown and export a number of VMs in the oVirt 4.3 and import them in to the new oVirt 4.4. 6) Repeat steps 2 > 5 until the everything is moved over. Just wanting to get your expert opinions on this method or is there a much quicker easier method that will not risk the chances of losing the cluster/VMs or an extended outage. Since we need to upgrade anyway from 4.3 to 4.4 I thought this the better method that upgrading the operational clusters. Thanks

4 3

Need to renew ovirt engine certificate
by Sachendra Shukla 17 Jan '24

17 Jan '24

Hi Team, The oVirt Engine certificate is scheduled to expire on February 1, 2024. Consequently, we need to initiate the certificate upgrade process. Could you please share the steps and process for the certificate upgrade? I have attached a snapshot below for your reference. [image: image.png] Regards, Sachendra Shukla Yagna iQ, Inc. and subsidiaries HQ Address: Yagna iQ Inc. 7700 Windrose Ave, Suite G300, Plano, TX 75024, USA 75024, Website: https://yagnaiq.com Contact Customer Support: support(a)yagnaiq.com Privacy Policy: https://www.yagnaiq.com/privacy-policy/ *This communication and any attachments may contain confidential information and/or copyright material of Yagna iQ, Inc. * All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Yagna iQ immediately by replying to the email and destroy all copies of this communication. This email has been scanned for all known viruses. The sender does not accept liability for any damage inflicted by viewing the content of this email.

3 3

Re: [ovirt-devel] Re: oVirt 4.6 OS versions
by Guillaume Pavese 16 Jan '24

16 Jan '24

Unless someone from the community steps up to take RedHat's role, there won't be any 4.6 On Fri, Jan 12, 2024 at 8:51 AM Diggy Mc <d03(a)bornfree.org> wrote: > > Isn't the oVirt 4.5 Hosted Engine built on CentOS Stream 8 ??? Stream 8 > ends in May 2024. I ask because we are still running on 4.4 and are > thinking about holding off until oVirt 4.6 before we deploy a new oVirt > environment. > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/MBQDZTC5K3R2V… > -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

1 0

oVirt 4.5.5 - Prb with qemu-kvm after upgrade
by Christophe GRENIER 14 Jan '24

14 Jan '24

Hello I have a standalone oVirt Manager 4.5.5-1.el8 and two small clusters. After upgrading ovir01001 in the "PreProd" cluster from AlmaLinux 8.8 to 8.9, the host was successfully activated but failed to take any VM. centos-release-ceph-pacific.noarch 1.0-2.el8 @cs8-extras centos-release-gluster10.noarch 1.0-1.el8s @cs8-extras-common centos-release-nfv-common.noarch 1-3.el8 @cs8-extras centos-release-nfv-openvswitch.noarch 1-3.el8 @cs8-extras centos-release-opstools.noarch 1-12.el8 @cs8-extras centos-release-ovirt45.noarch 8.9-1.el8s @cs8-extras-common centos-release-storage-common.noarch 2-2.el8 @cs8-extras centos-release-stream.x86_64 8.1-1.1911.0.7.el8 @cs8-extras centos-release-virt-common.noarch 1-2.el8 @cs8-extras vdsm.x86_64 4.50.5.1-1.el8 @centos-ovirt45 The problem has been "solved" by downgrading all qemu-* packages to the version in AlmaLinux 8.8 ie. qemu-kvm-6.2.0-40.module_el8.9.0+3681+41cbbcc0.1.alma.1 => qemu-kvm-6.2.0-33.module_el8.8.0+3612+f18d2b89.alma.1.x86_64 Please find the relevent log: - engine_when_failed.log https://pastebin.com/7MG6fYGY - engine_when_ok.log https://pastebin.com/MegqmMbg - vdsm_when_failed.log https://pastebin.com/ae4w0pix - vdsm_when_ok.log https://pastebin.com/d7P0BWDN Regards -- ,-~~-.___. ._. / | ' \ | |--------. Christophe GRENIER ( ) 0 | | | grenier(a)cgsecurity.org \_/-, ,----' | | | ==== !_!-v---v--. / \-'~; .--------. TestDisk & PhotoRec / __/~| ._-""|| | Data Recovery =( _____|_|____||________| https://www.cgsecurity.org

1 0

Add Direct LUN to VM with Rest API
by LS CHENG 13 Jan '24

13 Jan '24

Hi Anyone know how to add a Direct LUN to a VM o VM's? I am trying to clone a couple of VM's fibre channel direct lun's with SAN's snapshot technology and present those snapshots to another VM's, I would like to do this with CLI but I cannot find any example for Fibre Channel Disks and attach them to a VM. Thanks!

1 1

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

VM Unknow Status
by ankit＠eurus.net 12 Jan '24

12 Jan '24

One of node is got non-responsive suddenly and some VM stuck on Unknow Status, I am trying to change status but unable to login in DB. su - postgres psql engine psql command not found error. Can someone help me to get rid of it? Thanks, Ankit Sharma

2 6

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

Updated Ovirt Engine (4.5.5) - apache/websocket certs not renewed. (self signed) - Ive manually updated apache, how to do websocket?
by morgan cox 11 Jan '24

11 Jan '24

Hi. We have an Ovirt system, today I updated the engine to v4.5.5, the engine uses self-signed certs/CA. After the update (and engine-setup) I checked cert expiry dates ----- /etc/pki/ovirt-engine/ca.pem: Mar 24 15:10:29 2031 GMT /etc/pki/ovirt-engine/certs/apache.cer: Jan 11 15:11:58 2029 GMT /etc/pki/ovirt-engine/certs/engine.cer: May 10 11:13:51 2028 GMT /etc/pki/ovirt-engine/qemu-ca.pem Mar 24 15:10:35 2031 GMT /etc/pki/ovirt-engine/certs/websocket-proxy.cer Jun 11 11:13:52 2024 GMT /etc/pki/ovirt-engine/certs/jboss.cer May 10 11:13:51 2028 GMT /etc/pki/ovirt-engine/certs/ovirt-provider-ovn May 10 11:13:55 2028 GMT /etc/pki/ovirt-engine/certs/ovn-ndb.cer May 10 11:13:54 2028 GMT /etc/pki/ovirt-engine/certs/ovn-sdb.cer May 10 11:13:54 2028 GMT /etc/pki/ovirt-engine/certs/vmconsole-proxy-helper.cer May 26 16:27:04 2027 GMT /etc/pki/ovirt-engine/certs/vmconsole-proxy-host.cer May 26 16:27:05 2027 GMT /etc/pki/ovirt-engine/certs/vmconsole-proxy-user.cer May 26 16:27:04 2027 GMT --- I thought that Ovirt should auto update these when using engine-setup ? I manually updated apache cert using info from -> https://access.redhat.com/solutions/3329431 - i.e /usr/share/ovirt-engine/bin/pki-enroll-pkcs12.sh --name=apache --password="@PASSWORD@" --subject="${SUBJECT}" How can I update the websocket cert also ? Any help would be welcomed - thanks

1 0

hosted-engine deploy skip storage configuration
by laetitia.gilet＠bnf.fr 10 Jan '24

10 Jan '24

Hello, I'm trying to install ovirt from the command line on an ovirt 4.5.5 el9 Ovirt node. I prepared my LUN and multipath configuration and then run hosted-engine --deploy --4 The storage configuration is skipped and I am not prompted about which storage domain type I want to use. In the log the shows the few questions i've aswered : QUESTION/1/CI_APPLY_OPENSCAP_PROFILE=str:no QUESTION/1/CI_DNS=str:172.20.11.100 QUESTION/1/CI_ENABLE_FIPS=str:no QUESTION/1/CI_INSTANCE_DOMAINNAME=str:example.fr QUESTION/1/CI_INSTANCE_HOSTNAME=str:ovirt-prod.example.fr QUESTION/1/CI_ROOT_PASSWORD=str:**FILTERED** QUESTION/1/CI_ROOT_SSH_ACCESS=str:yes QUESTION/1/CI_ROOT_SSH_PUBKEY=str: QUESTION/1/CI_VM_ETC_HOST=str:yes QUESTION/1/CI_VM_STATIC_NETWORKING=str:static QUESTION/1/CLOUDINIT_VM_STATIC_IP_ADDRESS=str:172.20.82.2 QUESTION/1/DEPLOY_PROCEED=str:yes QUESTION/1/DIALOGOVEHOSTED_NOTIF/destEmail=str:admin@example.fr QUESTION/1/DIALOGOVEHOSTED_NOTIF/smtpPort=str:25 QUESTION/1/DIALOGOVEHOSTED_NOTIF/smtpServer=str:smtp.example.fr QUESTION/1/DIALOGOVEHOSTED_NOTIF/sourceEmail=str:noreply-ovirt@example.fr QUESTION/1/ENGINE_ADMIN_PASSWORD=str:**FILTERED** QUESTION/1/OVEHOSTED_GATEWAY=str:172.20.82.1 QUESTION/1/OVEHOSTED_NETWORK_TEST=str:dns QUESTION/1/OVEHOSTED_VMENV_OVF_ANSIBLE=str: QUESTION/1/OVESETUP_NETWORK_FQDN_first_HE=str:kvm.example.fr QUESTION/1/ovehosted_bridge_if=str:bond1 QUESTION/1/ovehosted_cluster_name=str:PC_Crise QUESTION/1/ovehosted_datacenter_name=str:Ovirt-prod QUESTION/1/ovehosted_enable_keycloak=str:no QUESTION/1/ovehosted_vmenv_cpu=str:4 QUESTION/1/ovehosted_vmenv_mac=str:00:16:3e:71:7e:ed QUESTION/1/ovehosted_vmenv_mem=str:16384 QUESTION/2/CI_ROOT_PASSWORD=str:**FILTERED** QUESTION/2/ENGINE_ADMIN_PASSWORD=str:**FILTERED** ... otopi.dialog.human dialog.__logString:204 DIALOG:SEND 2024-01-10 15:26:40,556+0100 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND --== STORAGE CONFIGURATION ==-- 2024-01-10 15:26:40,556+0100 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND 2024-01-10 15:26:40,557+0100 DEBUG otopi.context context._executeMethod:124 Stage customization METHOD otopi.plugins.otopi.dialog.cli.Plugin._customize 2024-01-10 15:26:40,557+0100 DEBUG otopi.context context._executeMethod:134 otopi.plugins.otopi.dialog.cli.Plugin._customize condition False 2024-01-10 15:26:40,558+0100 DEBUG otopi.context context._executeMethod:124 Stage customization METHOD otopi.plugins.gr_he_common.core.titles.Plugin._storage_end 2024-01-10 15:26:40,559+0100 DEBUG otopi.context context._executeMethod:124 Stage customization METHOD otopi.plugins.gr_he_common.core.titles.Plugin._network_start 2024-01-10 15:26:40,559+0100 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND 2024-01-10 15:26:40,55 My host see the LUN and multipath -ll result is OK Can you help me to configure the vm engine storage to FC please ? Laetitia

1 0

Usage Of More Up-To-Date Versions Of The "kojihub" rpm Files
by Matthew J Black 10 Jan '24

10 Jan '24

Hi All, When installing the latest version of oVirt on RHEL 9 the doco says to grab a couple of rpm files from `kojihub.stream.centos.org`. The files to grab are for v2.0.0. I'm wondering, because there are newer files on the server, if the doco might be a couple of months(?) out of date and we can instead grab the newer versions (or not, as the case may be)? Could one (or more) of the "main" oVirt devs jump in with an answer, please? For the record, when I get 5 minutes to scratch my butt I want to spin of a test cluster and try this (and other things) ou for myself, with the idea of reporting back to the Community - but I need to get a PROD cluster up and running ASAP and so don't have the luxury of "experimenting" right at this moment - hence my question. Thanks in advance Cheers Dulux-Oz

1 2

oVirt Self-Hosted Engine Deployment Error
by Matthew J Black 10 Jan '24

10 Jan '24

Hi Guys, New oVirt install using latest versions on a Rocky Linux v9.3 host. We're getting the following error in the setup logs: ~~~ 2024-01-09 17:14:53,977+1100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["ip", "rule", "add", "from", "192.168.1.1/255.255.255.0", "priority", "101", "table", "main"], "delta": "0:00:00.002702", "end": "2024-01-09 17:14:53.680933", "msg": "non-zero return code", "rc": 2, "start": "2024-01-09 17:14:53.678231", "stderr": "RTNETLINK answers: File exists", "stderr_lines": ["RTNETLINK answers: File exists"], "stdout": "", "stdout_lines": []} ~~~ So, which file "RTNETLINK answers: File exists" and can I simply manually delete that file and re-run `hosted-engine --deploy`? Cheers Dulux-Oz

3 3

Upgrading EL9 host from 4.5.4 to 4.5.5
by Devin A. Bougie 08 Jan '24

08 Jan '24

Hi, All. When upgrading an EL9 host from 4.5.4 to 4.5.5, I've found I need to exclude the following packages to avoid the errors shown below: *openvswitch*,*ovn*,centos-release-nfv-common Is that to be expected, or am I missing a required repo or other upgrade step? I just wanted to clarify, as the docs seem a little outdated at least WRT comments about nmstate? https://ovirt.org/download/install_on_rhel.html Thanks, Devin ------ [root@lnxvirt01 ~]# rpm -qa |grep -i openvswitch openvswitch-selinux-extra-policy-1.0-31.el9s.noarch ovirt-openvswitch-ovn-2.17-1.el9.noarch openvswitch2.17-2.17.0-103.el9s.x86_64 python3-openvswitch2.17-2.17.0-103.el9s.x86_64 openvswitch2.17-ipsec-2.17.0-103.el9s.x86_64 ovirt-openvswitch-ovn-host-2.17-1.el9.noarch ovirt-openvswitch-ipsec-2.17-1.el9.noarch ovirt-python-openvswitch-2.17-1.el9.noarch ovirt-openvswitch-2.17-1.el9.noarch ovirt-openvswitch-ovn-common-2.17-1.el9.noarch centos-release-nfv-openvswitch-1-5.el9.noarch [root@lnxvirt01 ~]# dnf update 173 files removed CLASSE oVirt Packages - x86_64 988 kB/s | 9.6 kB 00:00 CLASSE Packages - x86_64 45 MB/s | 642 kB 00:00 CentOS-9-stream - Ceph Pacific 561 kB/s | 557 kB 00:00 CentOS-9-stream - Gluster 10 245 kB/s | 56 kB 00:00 CentOS-9 - RabbitMQ 38 392 kB/s | 104 kB 00:00 CentOS Stream 9 - NFV OpenvSwitch 709 kB/s | 154 kB 00:00 CentOS-9 - OpenStack yoga 11 MB/s | 3.0 MB 00:00 CentOS Stream 9 - OpsTools - collectd 175 kB/s | 51 kB 00:00 CentOS Stream 9 - Extras packages 57 kB/s | 15 kB 00:00 CentOS Stream 9 - oVirt 4.5 2.7 MB/s | 1.0 MB 00:00 oVirt upstream for CentOS Stream 9 - oVirt 4.5 932 B/s | 7.5 kB 00:08 AlmaLinux 9 - AppStream 84 MB/s | 8.1 MB 00:00 AlmaLinux 9 - BaseOS 75 MB/s | 3.5 MB 00:00 AlmaLinux 9 - BaseOS - Debug 12 MB/s | 2.2 MB 00:00 AlmaLinux 9 - CRB 67 MB/s | 2.3 MB 00:00 AlmaLinux 9 - Extras 1.5 MB/s | 17 kB 00:00 AlmaLinux 9 - HighAvailability 30 MB/s | 434 kB 00:00 AlmaLinux 9 - NFV 70 MB/s | 2.0 MB 00:00 AlmaLinux 9 - Plus 3.2 MB/s | 29 kB 00:00 AlmaLinux 9 - ResilientStorage 14 MB/s | 446 kB 00:00 AlmaLinux 9 - RT 70 MB/s | 1.9 MB 00:00 AlmaLinux 9 - SAP 846 kB/s | 9.7 kB 00:00 AlmaLinux 9 - SAPHANA 1.3 MB/s | 13 kB 00:00 Error: Problem 1: package ovirt-openvswitch-2.17-1.el9.noarch from @System requires openvswitch2.17, but none of the providers can be installed - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-103.el9s.x86_64 from @System - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-103.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-108.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-109.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-115.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-120.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-15.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-31.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-51.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-52.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-55.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-57.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-60.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-62.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-63.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-67.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-68.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-71.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-72.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-76.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-77.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-85.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-87.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-92.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-93.el9s.x86_64 from centos-nfv-openvswitch - package rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes openvswitch2.17 < 3.1 provided by openvswitch2.17-2.17.0-95.el9s.x86_64 from centos-nfv-openvswitch - cannot install the best update candidate for package ovirt-openvswitch-2.17-1.el9.noarch - cannot install the best update candidate for package openvswitch2.17-2.17.0-103.el9s.x86_64 Problem 2: package python3-rdo-openvswitch-2:3.1-2.el9s.noarch from centos-openstack-yoga obsoletes python3-openvswitch2.17 < 3.1 provided by python3-openvswitch2.17-2.17.0-120.el9s.x86_64 from centos-nfv-openvswitch - package openvswitch2.17-ipsec-2.17.0-120.el9s.x86_64 from centos-nfv-openvswitch requires python3-openvswitch2.17 = 2.17.0-120.el9s, but none of the providers can be installed - cannot install the best update candidate for package python3-openvswitch2.17-2.17.0-103.el9s.x86_64 - cannot install the best update candidate for package openvswitch2.17-ipsec-2.17.0-103.el9s.x86_64 Problem 3: package ovirt-openvswitch-ovn-common-2.17-1.el9.noarch from @System requires ovn22.09, but none of the providers can be installed - package rdo-ovn-2:22.12-2.el9s.noarch from centos-openstack-yoga obsoletes ovn22.09 < 22.12 provided by ovn22.09-22.09.0-31.el9s.x86_64 from @System - package rdo-ovn-2:22.12-2.el9s.noarch from centos-openstack-yoga obsoletes ovn22.09 < 22.12 provided by ovn22.09-22.09.0-11.el9s.x86_64 from centos-nfv-openvswitch - package rdo-ovn-2:22.12-2.el9s.noarch from centos-openstack-yoga obsoletes ovn22.09 < 22.12 provided by ovn22.09-22.09.0-22.el9s.x86_64 from centos-nfv-openvswitch - package rdo-ovn-2:22.12-2.el9s.noarch from centos-openstack-yoga obsoletes ovn22.09 < 22.12 provided by ovn22.09-22.09.0-31.el9s.x86_64 from centos-nfv-openvswitch - cannot install the best update candidate for package ovn22.09-22.09.0-31.el9s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.17-1.el9.noarch Problem 4: package ovirt-openvswitch-ovn-host-2.17-1.el9.noarch from @System requires ovn22.09-host, but none of the providers can be installed - package rdo-ovn-host-2:22.12-2.el9s.noarch from centos-openstack-yoga obsoletes ovn22.09-host < 22.12 provided by ovn22.09-host-22.09.0-31.el9s.x86_64 from @System - package rdo-ovn-host-2:22.12-2.el9s.noarch from centos-openstack-yoga obsoletes ovn22.09-host < 22.12 provided by ovn22.09-host-22.09.0-11.el9s.x86_64 from centos-nfv-openvswitch - package rdo-ovn-host-2:22.12-2.el9s.noarch from centos-openstack-yoga obsoletes ovn22.09-host < 22.12 provided by ovn22.09-host-22.09.0-22.el9s.x86_64 from centos-nfv-openvswitch - package rdo-ovn-host-2:22.12-2.el9s.noarch from centos-openstack-yoga obsoletes ovn22.09-host < 22.12 provided by ovn22.09-host-22.09.0-31.el9s.x86_64 from centos-nfv-openvswitch - cannot install the best update candidate for package ovn22.09-host-22.09.0-31.el9s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-ovn-host-2.17-1.el9.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@lnxvirt01 ~]# yum --exclude=kernel*,*openvswitch*,*ovn*,centos-release-nfv-common update Last metadata expiration check: 0:13:54 ago on Mon 08 Jan 2024 02:51:41 PM EST. Dependencies resolved. ======================================================================================================================================================================================================================================== Package Architecture Version Repository Size ======================================================================================================================================================================================================================================== Upgrading: NetworkManager-libreswan x86_64 1.2.14-2.el9_3.alma.1 appstream 124 k centos-release-ceph-pacific noarch 1.0-2.el9s c9s-extras-common 7.4 k centos-release-cloud noarch 1-1.el9s c9s-extras-common 7.9 k centos-release-gluster10 noarch 1.0-2.el9s c9s-extras-common 8.8 k centos-release-messaging noarch 1-4.el9s c9s-extras-common 8.4 k centos-release-openstack-yoga noarch 1-4.el9s c9s-extras-common 8.0 k centos-release-opstools noarch 1-12.el9s c9s-extras-common 8.4 k centos-release-ovirt45 noarch 9.2-1.el9s c9s-extras-common 18 k centos-release-rabbitmq-38 noarch 1-4.el9s c9s-extras-common 7.4 k centos-release-storage-common noarch 2-5.el9s c9s-extras-common 8.3 k centos-release-virt-common noarch 1-4.el9s c9s-extras-common 7.9 k ceph-common x86_64 2:16.2.14-1.el9s centos-ceph-pacific 20 M firefox x86_64 115.6.0-1.el9_3.alma appstream 110 M glusterfs x86_64 10.5-1.el9s centos-gluster10 606 k glusterfs-cli x86_64 10.5-1.el9s centos-gluster10 184 k glusterfs-client-xlators x86_64 10.5-1.el9s centos-gluster10 854 k glusterfs-fuse x86_64 10.5-1.el9s centos-gluster10 137 k libcephfs2 x86_64 2:16.2.14-1.el9s centos-ceph-pacific 657 k libgfrpc0 x86_64 10.5-1.el9s centos-gluster10 53 k libgfxdr0 x86_64 10.5-1.el9s centos-gluster10 28 k libglusterd0 x86_64 10.5-1.el9s centos-gluster10 11 k libglusterfs0 x86_64 10.5-1.el9s centos-gluster10 300 k libqb x86_64 2.0.8-1.el9 centos-ovirt45 91 k librados2 x86_64 2:16.2.14-1.el9s centos-ceph-pacific 3.2 M libradosstriper1 x86_64 2:16.2.14-1.el9s centos-ceph-pacific 469 k librbd1 x86_64 2:16.2.14-1.el9s centos-ceph-pacific 3.0 M librgw2 x86_64 2:16.2.14-1.el9s centos-ceph-pacific 3.4 M libvirt x86_64 9.5.0-7.el9_3.alma.2 appstream 22 k libvirt-client x86_64 9.5.0-7.el9_3.alma.2 appstream 426 k libvirt-daemon x86_64 9.5.0-7.el9_3.alma.2 appstream 168 k libvirt-daemon-common x86_64 9.5.0-7.el9_3.alma.2 appstream 129 k libvirt-daemon-config-network x86_64 9.5.0-7.el9_3.alma.2 appstream 25 k libvirt-daemon-config-nwfilter x86_64 9.5.0-7.el9_3.alma.2 appstream 30 k libvirt-daemon-driver-interface x86_64 9.5.0-7.el9_3.alma.2 appstream 174 k libvirt-daemon-driver-network x86_64 9.5.0-7.el9_3.alma.2 appstream 212 k libvirt-daemon-driver-nodedev x86_64 9.5.0-7.el9_3.alma.2 appstream 194 k libvirt-daemon-driver-nwfilter x86_64 9.5.0-7.el9_3.alma.2 appstream 210 k libvirt-daemon-driver-qemu x86_64 9.5.0-7.el9_3.alma.2 appstream 909 k libvirt-daemon-driver-secret x86_64 9.5.0-7.el9_3.alma.2 appstream 171 k libvirt-daemon-driver-storage x86_64 9.5.0-7.el9_3.alma.2 appstream 22 k libvirt-daemon-driver-storage-core x86_64 9.5.0-7.el9_3.alma.2 appstream 229 k libvirt-daemon-driver-storage-disk x86_64 9.5.0-7.el9_3.alma.2 appstream 33 k libvirt-daemon-driver-storage-iscsi x86_64 9.5.0-7.el9_3.alma.2 appstream 30 k libvirt-daemon-driver-storage-logical x86_64 9.5.0-7.el9_3.alma.2 appstream 34 k libvirt-daemon-driver-storage-mpath x86_64 9.5.0-7.el9_3.alma.2 appstream 28 k libvirt-daemon-driver-storage-rbd x86_64 9.5.0-7.el9_3.alma.2 appstream 38 k libvirt-daemon-driver-storage-scsi x86_64 9.5.0-7.el9_3.alma.2 appstream 30 k libvirt-daemon-kvm x86_64 9.5.0-7.el9_3.alma.2 appstream 22 k libvirt-daemon-lock x86_64 9.5.0-7.el9_3.alma.2 appstream 58 k libvirt-daemon-log x86_64 9.5.0-7.el9_3.alma.2 appstream 62 k libvirt-daemon-plugin-lockd x86_64 9.5.0-7.el9_3.alma.2 appstream 33 k libvirt-daemon-plugin-sanlock x86_64 9.5.0-7.el9_3.alma.2 crb 44 k libvirt-daemon-proxy x86_64 9.5.0-7.el9_3.alma.2 appstream 166 k libvirt-libs x86_64 9.5.0-7.el9_3.alma.2 appstream 4.8 M otopi-common noarch 1.10.4-1.el9 centos-ovirt45 92 k ovirt-ansible-collection noarch 3.2.0-1.el9 centos-ovirt45 279 k ovirt-engine-setup-base noarch 4.5.5-1.el9 centos-ovirt45 111 k ovirt-hosted-engine-ha noarch 2.5.1-1.el9 centos-ovirt45 312 k ovirt-hosted-engine-setup noarch 2.7.1-1.el9 centos-ovirt45 221 k ovirt-vmconsole noarch 1.0.9-3.el9 centos-ovirt45 38 k ovirt-vmconsole-host noarch 1.0.9-3.el9 centos-ovirt45 21 k python3-ceph-argparse x86_64 2:16.2.14-1.el9s centos-ceph-pacific 46 k python3-ceph-common x86_64 2:16.2.14-1.el9s centos-ceph-pacific 98 k python3-cephfs x86_64 2:16.2.14-1.el9s centos-ceph-pacific 193 k python3-os-brick noarch 5.2.4-1.el9s centos-openstack-yoga 1.1 M python3-oslo-config noarch 2:8.8.1-1.el9s centos-openstack-yoga 216 k python3-otopi noarch 1.10.4-1.el9 centos-ovirt45 105 k python3-ovirt-engine-lib noarch 4.5.5-1.el9 centos-ovirt45 31 k python3-rados x86_64 2:16.2.14-1.el9s centos-ceph-pacific 343 k python3-rbd x86_64 2:16.2.14-1.el9s centos-ceph-pacific 314 k python3-rgw x86_64 2:16.2.14-1.el9s centos-ceph-pacific 106 k selinux-policy noarch 38.1.29-1.el9 el-classe-ovirt 56 k selinux-policy-targeted noarch 38.1.29-1.el9 el-classe-ovirt 6.5 M tigervnc x86_64 1.13.1-3.el9_3.3.alma.1 appstream 297 k tigervnc-icons noarch 1.13.1-3.el9_3.3.alma.1 appstream 33 k tigervnc-license noarch 1.13.1-3.el9_3.3.alma.1 appstream 13 k vdsm x86_64 4.50.5.1-1.el9 centos-ovirt45 337 k vdsm-api noarch 4.50.5.1-1.el9 centos-ovirt45 101 k vdsm-client noarch 4.50.5.1-1.el9 centos-ovirt45 23 k vdsm-common noarch 4.50.5.1-1.el9 centos-ovirt45 130 k vdsm-http noarch 4.50.5.1-1.el9 centos-ovirt45 14 k vdsm-jsonrpc noarch 4.50.5.1-1.el9 centos-ovirt45 30 k vdsm-network x86_64 4.50.5.1-1.el9 centos-ovirt45 209 k vdsm-python noarch 4.50.5.1-1.el9 centos-ovirt45 1.2 M vdsm-yajsonrpc noarch 4.50.5.1-1.el9 centos-ovirt45 39 k vivaldi-stable x86_64 6.5.3206.50-1 el-classe 103 M Transaction Summary ======================================================================================================================================================================================================================================== Upgrade 86 Packages Total download size: 267 M Is this ok [y/N]: N Operation aborted. ------

1 0

Error: GPG check FAILED
by juan.gabriel1786＠gmail.com 07 Jan '24

07 Jan '24

Hello oVirt Support Team, I am experiencing a GPG key verification issue on my oVirt Node when attempting to update packages. The error persists even after the GPG keys have been imported and seems to be related to package verification. System Details: Operating System: oVirt Node 4.5.4 CPE OS Name: cpe:/o:centos:centos:9 Kernel: Linux 5.14.0-202.el9.x86_64 Architecture: x86-64 Hardware Vendor: Supermicro Hardware Model: X9DRL-3F/iF Steps to Reproduce: Imported the GPG key with the command: bash Copy code rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 Ran dnf update, which led to the following error: The GPG keys listed for the "oVirt upstream for CentOS Stream 9 - oVirt 4.5" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository. Failing package is: ovirt-node-ng-image-update-4.5.5-1.el9.noarch Error: GPG check FAILED The GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 (0x24901D0C) is reported to be already installed, but it does not seem to match the packages being updated. Could you please advise on how to resolve this GPG key verification failure? I am following standard update procedures, and this issue is preventing me from maintaining the system's security and stability. Thank you for your time and assistance. Best regards,

1 0

Cannot get Ovirt 4.5 to work, how ever I try. Virgin install: no pki ca-cert gen, restoring: no OVN connection
by julian.steiner＠conesphere.com 04 Jan '24

04 Jan '24

1 3

Disk upload: EngineException: java.lang.NullPointerException (Failed with error ENGINE and code 5001)
by goestin＠intert00bz.nl 03 Jan '24

03 Jan '24

Hi All, after adding an oVirt node as a local storage machine I am unable to upload a disk to the datastore. The button "test connection" shows: "Connection to ovirt-imageio was successful.". Version: 4.5.4-1.el8 OS: AlmaLinux 8.9 (Midnight Oncilla) Below a excerpt from the engine.log showing the entire upload session. Note 1: The machine "kvm-sandbox-qm7" is the machine for the localstorage cluster. The machine "kvm-sandbox-gcz" is a machine from the other "default cluster" and I was under the impression that the two clusters would be completely separate things and should not interfere with each other. But I am not sure about that. --- snip --- 2024-01-03 10:05:26,898Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] Lock Acquired to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2024-01-03 10:05:26,938Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] Running command: TransferDiskImageCommand internal: false. Entities affected : ID: 95dfc5bc-2a31-405c-ada0-6015edd281da Type: StorageAction group CREATE_DISK with role type USER 2024-01-03 10:05:26,938Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] Creating ImageTransfer entity for command 'ec704c40-89bc-4fdf-a44a-607dd7b9b2f7', proxyEnabled: true 2024-01-03 10:05:26,940Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] Starting image transfer: ImageTransfer:{id='ec704c40-89bc-4fdf-a44a-607dd7b9b2f7', phase='Initializing', type='Upload', active='false', lastUpdated='Wed Jan 03 10:05:26 UTC 2024', message='null', vdsId='null', diskId='null', imagedTicketId='null', proxyUri='null', bytesSent='null', bytesTotal='697434112', clientInactivityTimeout='60', timeoutPolicy='legacy', imageFormat='COW', transferClientType='Transfer via browser', shallow='false'} 2024-01-03 10:05:26,940Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] Creating disk image 2024-01-03 10:05:26,953Z INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] Running command: AddDiskCommand internal: true. Entities affected : ID: 95dfc5bc-2a31-405c-ada0-6015edd281da Type: StorageAction group CREATE_DISK with role type USER 2024-01-03 10:05:26,961Z INFO [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] Running command: AddImageFromScratchCommand internal: true. Entities affected : ID: 95dfc5bc-2a31-405c-ada0-6015edd281da Type: Storage 2024-01-03 10:05:26,981Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] START, CreateVolumeVDSCommand( CreateVolumeVDSCommandParameters:{storagePoolId='4c5f1e92-239b-471c-9db0-970029129a62', ignoreFailoverLimit='false', storageDomainId='95dfc5bc-2a31-405c-ada0-6015edd281da', imageGroupId='13dcaf25-6b58-4c79-85a7-0aecd153fb59', imageSizeInBytes='10737418240', volumeFormat='COW', newImageId='6b80fba5-c2ae-4b68-a24d-21d7f657da8f', imageType='Sparse', newImageDescription='{"DiskAlias":"aaa","DiskDescription":""}', imageInitialSizeInBytes='0', imageId='00000000-0000-0000-0000-000000000000', sourceImageGroupId='00000000-0000-0000-0000-000000000000', shouldAddBitmaps='false', legal='true', sequenceNumber='1', bitmap='null'}), log id: b4c79ef 2024-01-03 10:05:27,406Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, CreateVolumeVDSCommand, return: 6b80fba5-c2ae-4b68-a24d-21d7f657da8f, log id: b4c79ef 2024-01-03 10:05:27,409Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command 'a6f3ff83-daa4-4799-908a-07029ff8f6ef' 2024-01-03 10:05:27,410Z INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] CommandMultiAsyncTasks::attachTask: Attaching task '5a29a235-b61c-4efb-959a-f29ae7f863be' to command 'a6f3ff83-daa4-4799-908a-07029ff8f6ef'. 2024-01-03 10:05:27,427Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] Adding task '5a29a235-b61c-4efb-959a-f29ae7f863be' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2024-01-03 10:05:27,435Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] BaseAsyncTask::startPollingTask: Starting to poll task '5a29a235-b61c-4efb-959a-f29ae7f863be'. 2024-01-03 10:05:27,449Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] EVENT_ID: ADD_DISK_INTERNAL(2,036), Add-Disk operation of 'aaa' was initiated by the system. 2024-01-03 10:05:27,457Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [7855db64-635d-430f-9de8-21b1983e43a0] EVENT_ID: TRANSFER_IMAGE_INITIATED(1,031), Image Upload with disk aaa was initiated by [[redacted user]]@[[redacted]]@[[redacted]]. 2024-01-03 10:05:27,866Z INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-95) [7855db64-635d-430f-9de8-21b1983e43a0] Command 'AddDisk' (id: 'dfe023fa-0a96-40e8-9934-fb94a156bff6') waiting on child command id: 'a6f3ff83-daa4-4799-908a-07029ff8f6ef' type:'AddImageFromScratch' to complete 2024-01-03 10:05:27,869Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-95) [7855db64-635d-430f-9de8-21b1983e43a0] Waiting for disk to be added for image transfer 'ec704c40-89bc-4fdf-a44a-607dd7b9b2f7' 2024-01-03 10:05:29,872Z INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-16) [7855db64-635d-430f-9de8-21b1983e43a0] Command 'AddDisk' (id: 'dfe023fa-0a96-40e8-9934-fb94a156bff6') waiting on child command id: 'a6f3ff83-daa4-4799-908a-07029ff8f6ef' type:'AddImageFromScratch' to complete 2024-01-03 10:05:29,875Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-16) [7855db64-635d-430f-9de8-21b1983e43a0] Waiting for disk to be added for image transfer 'ec704c40-89bc-4fdf-a44a-607dd7b9b2f7' 2024-01-03 10:05:30,014Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-46) [] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now 2024-01-03 10:05:30,019Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-46) [] SPMAsyncTask::PollTask: Polling task '5a29a235-b61c-4efb-959a-f29ae7f863be' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'success'. 2024-01-03 10:05:30,019Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-46) [] BaseAsyncTask::onTaskEndSuccess: Task '5a29a235-b61c-4efb-959a-f29ae7f863be' (Parent Command 'AddImageFromScratch', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended successfully. 2024-01-03 10:05:30,021Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-46) [] CommandAsyncTask::endActionIfNecessary: All tasks of command 'a6f3ff83-daa4-4799-908a-07029ff8f6ef' has ended -> executing 'endAction' 2024-01-03 10:05:30,022Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-46) [] CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: 'a6f3ff83-daa4-4799-908a-07029ff8f6ef'): calling endAction '. 2024-01-03 10:05:30,022Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2956) [] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction 'AddImageFromScratch', 2024-01-03 10:05:30,027Z INFO [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] Command [id=a6f3ff83-daa4-4799-908a-07029ff8f6ef]: Updating status to 'SUCCEEDED', The command end method logic will be executed by one of its parent commands. 2024-01-03 10:05:30,027Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'AddImageFromScratch' completed, handling the result. 2024-01-03 10:05:30,027Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'AddImageFromScratch' succeeded, clearing tasks. 2024-01-03 10:05:30,027Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] SPMAsyncTask::ClearAsyncTask: Attempting to clear task '5a29a235-b61c-4efb-959a-f29ae7f863be' 2024-01-03 10:05:30,028Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='4c5f1e92-239b-471c-9db0-970029129a62', ignoreFailoverLimit='false', taskId='5a29a235-b61c-4efb-959a-f29ae7f863be'}), log id: af95363 2024-01-03 10:05:30,028Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] START, HSMClearTaskVDSCommand(HostName = kvm-sandbox-qm7, HSMTaskGuidBaseVDSCommandParameters:{hostId='9fb846b0-58cf-41ab-875c-3e3118a24b89', taskId='5a29a235-b61c-4efb-959a-f29ae7f863be'}), log id: 52de524b 2024-01-03 10:05:30,044Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, HSMClearTaskVDSCommand, return: , log id: 52de524b 2024-01-03 10:05:30,044Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, SPMClearTaskVDSCommand, return: , log id: af95363 2024-01-03 10:05:30,050Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] BaseAsyncTask::removeTaskFromDB: Removed task '5a29a235-b61c-4efb-959a-f29ae7f863be' from DataBase 2024-01-03 10:05:30,050Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2956) [7855db64-635d-430f-9de8-21b1983e43a0] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity 'a6f3ff83-daa4-4799-908a-07029ff8f6ef' 2024-01-03 10:05:31,567Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-6) [1ab78812-4bb8-4889-bea0-d2f2a82d52af] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: 95dfc5bc-2a31-405c-ada0-6015edd281da Type: SystemAction group CREATE_DISK with role type USER 2024-01-03 10:05:33,877Z INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] Getting volume info for image '13dcaf25-6b58-4c79-85a7-0aecd153fb59/6b80fba5-c2ae-4b68-a24d-21d7f657da8f' 2024-01-03 10:05:33,894Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] START, GetVolumeInfoVDSCommand(HostName = kvm-sandbox-qm7, GetVolumeInfoVDSCommandParameters:{hostId='9fb846b0-58cf-41ab-875c-3e3118a24b89', storagePoolId='4c5f1e92-239b-471c-9db0-970029129a62', storageDomainId='95dfc5bc-2a31-405c-ada0-6015edd281da', imageGroupId='13dcaf25-6b58-4c79-85a7-0aecd153fb59', imageId='6b80fba5-c2ae-4b68-a24d-21d7f657da8f'}), log id: 78edc340 2024-01-03 10:05:33,908Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@14184952, log id: 78edc340 2024-01-03 10:05:33,908Z INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] Command 'AddDisk' id: 'dfe023fa-0a96-40e8-9934-fb94a156bff6' child commands '[a6f3ff83-daa4-4799-908a-07029ff8f6ef]' executions were completed, status 'SUCCEEDED' 2024-01-03 10:05:33,967Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] Successfully added Upload disk 'aaa' (disk id: '13dcaf25-6b58-4c79-85a7-0aecd153fb59', image id: '6b80fba5-c2ae-4b68-a24d-21d7f657da8f') for image transfer 'ec704c40-89bc-4fdf-a44a-607dd7b9b2f7' 2024-01-03 10:05:33,978Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] START, PrepareImageVDSCommand(HostName = kvm-sandbox-gcz, PrepareImageVDSCommandParameters:{hostId='059c7eaf-da39-41f2-bb61-659ab3bd1b61'}), log id: 104764a4 2024-01-03 10:05:33,981Z ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] Failed in 'PrepareImageVDS' method, for vds: 'kvm-sandbox-gcz'; host: 'kvm-sandbox-gcz.hprvsr.infra.pdc.[[redacted]]': null 2024-01-03 10:05:33,982Z ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] Command 'PrepareImageVDSCommand(HostName = kvm-sandbox-gcz, PrepareImageVDSCommandParameters:{hostId='059c7eaf-da39-41f2-bb61-659ab3bd1b61'})' execution failed: null 2024-01-03 10:05:33,982Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, PrepareImageVDSCommand, return: , log id: 104764a4 2024-01-03 10:05:33,982Z ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [7855db64-635d-430f-9de8-21b1983e43a0] Failed to prepare image for image transfer 'ec704c40-89bc-4fdf-a44a-607dd7b9b2f7': {}: org.ovirt.engine.core.common.errors.EngineException: EngineException: java.lang.NullPointerException (Failed with error ENGINE and code 5001) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:114) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.runVdsCommand(VDSBrokerFrontendImpl.java:33) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:2121) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.prepareImage(TransferDiskImageCommand.java:188) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.startImageTransferSession(TransferDiskImageCommand.java:1064) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.handleImageIsReadyForTransfer(TransferDiskImageCommand.java:681) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.handleInitializing(TransferDiskImageCommand.java:654) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.executeStateHandler(TransferDiskImageCommand.java:587) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.proceedCommandExecution(TransferDiskImageCommand.java:574) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferImageCommandCallback.doPolling(TransferImageCommandCallback.java:21) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:360) at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:511) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:227) Caused by: java.lang.NullPointerException at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageReturn.<init>(PrepareImageReturn.java:15) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.jsonrpc.JsonRpcVdsServer.prepareImage(JsonRpcVdsServer.java:1947) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand.executeImageActionVdsBrokerCommand(PrepareImageVDSCommand.java:18) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand.executeImageActionVdsBrokerCommand(PrepareImageVDSCommand.java:5) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.ImageActionsVDSCommandBase.executeVdsBrokerCommand(ImageActionsVDSCommandBase.java:14) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:123) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:410) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) at jdk.internal.reflect.GeneratedMethodAccessor87.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) at org.ovirt.engine.core.common//org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) at jdk.internal.reflect.GeneratedMethodAccessor80.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) ... 19 more 2024-01-03 10:05:34,991Z INFO [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] Ending command 'org.ovirt.engine.core.bll.storage.disk.AddDiskCommand' successfully. 2024-01-03 10:05:34,997Z INFO [org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] Ending command 'org.ovirt.engine.core.bll.storage.disk.image.AddImageFromScratchCommand' successfully. 2024-01-03 10:05:35,010Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] START, GetImageInfoVDSCommand( GetImageInfoVDSCommandParameters:{storagePoolId='4c5f1e92-239b-471c-9db0-970029129a62', ignoreFailoverLimit='false', storageDomainId='95dfc5bc-2a31-405c-ada0-6015edd281da', imageGroupId='13dcaf25-6b58-4c79-85a7-0aecd153fb59', imageId='6b80fba5-c2ae-4b68-a24d-21d7f657da8f'}), log id: 127cba80 2024-01-03 10:05:35,011Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] START, GetVolumeInfoVDSCommand(HostName = kvm-sandbox-qm7, GetVolumeInfoVDSCommandParameters:{hostId='9fb846b0-58cf-41ab-875c-3e3118a24b89', storagePoolId='4c5f1e92-239b-471c-9db0-970029129a62', storageDomainId='95dfc5bc-2a31-405c-ada0-6015edd281da', imageGroupId='13dcaf25-6b58-4c79-85a7-0aecd153fb59', imageId='6b80fba5-c2ae-4b68-a24d-21d7f657da8f'}), log id: 1f0ed2a8 2024-01-03 10:05:35,024Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVolumeInfoVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, GetVolumeInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@14184952, log id: 1f0ed2a8 2024-01-03 10:05:35,024Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetImageInfoVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, GetImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.DiskImage@14184952, log id: 127cba80 2024-01-03 10:05:35,046Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] START, PrepareImageVDSCommand(HostName = kvm-sandbox-qm7, PrepareImageVDSCommandParameters:{hostId='9fb846b0-58cf-41ab-875c-3e3118a24b89'}), log id: 39df22a1 2024-01-03 10:05:35,076Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, PrepareImageVDSCommand, return: PrepareImageReturn:{status='Status [code=0, message=Done]'}, log id: 39df22a1 2024-01-03 10:05:35,077Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetQemuImageInfoVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] START, GetQemuImageInfoVDSCommand(HostName = kvm-sandbox-qm7, GetVolumeInfoVDSCommandParameters:{hostId='9fb846b0-58cf-41ab-875c-3e3118a24b89', storagePoolId='4c5f1e92-239b-471c-9db0-970029129a62', storageDomainId='95dfc5bc-2a31-405c-ada0-6015edd281da', imageGroupId='13dcaf25-6b58-4c79-85a7-0aecd153fb59', imageId='6b80fba5-c2ae-4b68-a24d-21d7f657da8f'}), log id: 59083d66 2024-01-03 10:05:35,093Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetQemuImageInfoVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, GetQemuImageInfoVDSCommand, return: org.ovirt.engine.core.common.businessentities.storage.QemuImageInfo@12025249, log id: 59083d66 2024-01-03 10:05:35,095Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] START, TeardownImageVDSCommand(HostName = kvm-sandbox-qm7, ImageActionsVDSCommandParameters:{hostId='9fb846b0-58cf-41ab-875c-3e3118a24b89'}), log id: 2c3b32ab 2024-01-03 10:05:35,097Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.TeardownImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] FINISH, TeardownImageVDSCommand, return: StatusReturn:{status='Status [code=0, message=Done]'}, log id: 2c3b32ab 2024-01-03 10:05:35,106Z WARN [org.ovirt.engine.core.bll.storage.disk.AddDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [] VM is null - no unlocking 2024-01-03 10:05:35,132Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [] EVENT_ID: USER_ADD_DISK_FINISHED_SUCCESS(2,021), The disk 'aaa' was successfully added. 2024-01-03 10:05:35,134Z ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] Ending command 'org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand' with failure. 2024-01-03 10:05:35,134Z ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [7855db64-635d-430f-9de8-21b1983e43a0] Failed to transfer disk '00000000-0000-0000-0000-000000000000' for image transfer 'ec704c40-89bc-4fdf-a44a-607dd7b9b2f7' 2024-01-03 10:05:35,157Z INFO [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] Running command: RemoveDiskCommand internal: true. Entities affected : ID: 13dcaf25-6b58-4c79-85a7-0aecd153fb59 Type: DiskAction group DELETE_DISK with role type USER 2024-01-03 10:05:35,176Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] Running command: RemoveImageCommand internal: true. Entities affected : ID: 95dfc5bc-2a31-405c-ada0-6015edd281da Type: Storage 2024-01-03 10:05:35,202Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] START, DeleteImageGroupVDSCommand( DeleteImageGroupVDSCommandParameters:{storagePoolId='4c5f1e92-239b-471c-9db0-970029129a62', ignoreFailoverLimit='false', storageDomainId='95dfc5bc-2a31-405c-ada0-6015edd281da', imageGroupId='13dcaf25-6b58-4c79-85a7-0aecd153fb59', postZeros='false', discard='false', forceDelete='false'}), log id: 10fab46b 2024-01-03 10:05:35,449Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] FINISH, DeleteImageGroupVDSCommand, return: , log id: 10fab46b 2024-01-03 10:05:35,451Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command '8640049f-0ead-486a-93b4-dcbbaa353294' 2024-01-03 10:05:35,451Z INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] CommandMultiAsyncTasks::attachTask: Attaching task 'b51f31d8-944b-4539-beb6-a0ab995073c6' to command '8640049f-0ead-486a-93b4-dcbbaa353294'. 2024-01-03 10:05:35,463Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] Adding task 'b51f31d8-944b-4539-beb6-a0ab995073c6' (Parent Command 'RemoveImage', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2024-01-03 10:05:35,468Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] BaseAsyncTask::startPollingTask: Starting to poll task 'b51f31d8-944b-4539-beb6-a0ab995073c6'. 2024-01-03 10:05:35,468Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] BaseAsyncTask::startPollingTask: Starting to poll task 'b51f31d8-944b-4539-beb6-a0ab995073c6'. 2024-01-03 10:05:35,533Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] EVENT_ID: USER_FINISHED_REMOVE_DISK(2,014), Disk aaa was successfully removed from domain localstorage (User [[redacted user]]@[[redacted]]@[[redacted]]). 2024-01-03 10:05:35,534Z INFO [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2024-01-03 10:05:35,534Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2024-01-03 10:05:35,535Z INFO [org.ovirt.engine.core.bll.storage.disk.image.ImageTransferUpdater] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] Updating image transfer 'ec704c40-89bc-4fdf-a44a-607dd7b9b2f7' phase from 'Initializing' to 'Finished Failure' 2024-01-03 10:05:35,547Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [5871c85c] EVENT_ID: TRANSFER_IMAGE_FAILED(1,034), Image Upload with disk aaa failed. 2024-01-03 10:05:35,646Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-1) [d4821bf6-c786-4129-a3b0-4a79fc2d61d7] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: 95dfc5bc-2a31-405c-ada0-6015edd281da Type: SystemAction group CREATE_DISK with role type USER 2024-01-03 10:05:36,562Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [5871c85c] Command 'RemoveDisk' (id: 'b01c95d8-b3c3-40db-9a41-6fe1e817fe5a') waiting on child command id: '8640049f-0ead-486a-93b4-dcbbaa353294' type:'RemoveImage' to complete 2024-01-03 10:05:36,565Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [5871c85c] Waiting on remove image command to complete the task 'b51f31d8-944b-4539-beb6-a0ab995073c6' 2024-01-03 10:05:38,569Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [5871c85c] Command 'RemoveDisk' (id: 'b01c95d8-b3c3-40db-9a41-6fe1e817fe5a') waiting on child command id: '8640049f-0ead-486a-93b4-dcbbaa353294' type:'RemoveImage' to complete 2024-01-03 10:05:38,573Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [5871c85c] Waiting on remove image command to complete the task 'b51f31d8-944b-4539-beb6-a0ab995073c6' 2024-01-03 10:05:39,645Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferImageStatusCommand] (default task-1) [95e8a4ca-324f-4f9e-86a0-ef324383ca64] Running command: TransferImageStatusCommand internal: false. Entities affected : ID: 95dfc5bc-2a31-405c-ada0-6015edd281da Type: SystemAction group CREATE_DISK with role type USER 2024-01-03 10:05:40,022Z INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-40) [] Polling and updating Async Tasks: 2 tasks, 1 tasks to poll now 2024-01-03 10:05:40,027Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-40) [] SPMAsyncTask::PollTask: Polling task 'b51f31d8-944b-4539-beb6-a0ab995073c6' (Parent Command 'RemoveImage', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'finished', result 'success'. 2024-01-03 10:05:40,027Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-40) [] BaseAsyncTask::onTaskEndSuccess: Task 'b51f31d8-944b-4539-beb6-a0ab995073c6' (Parent Command 'RemoveImage', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended successfully. 2024-01-03 10:05:40,030Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-40) [] CommandAsyncTask::endActionIfNecessary: All tasks of command '8640049f-0ead-486a-93b4-dcbbaa353294' has ended -> executing 'endAction' 2024-01-03 10:05:40,030Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-40) [] CommandAsyncTask::endAction: Ending action for '1' tasks (command ID: '8640049f-0ead-486a-93b4-dcbbaa353294'): calling endAction '. 2024-01-03 10:05:40,031Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2965) [] CommandAsyncTask::endCommandAction [within thread] context: Attempting to endAction 'RemoveImage', 2024-01-03 10:05:40,033Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'RemoveImage' completed, handling the result. 2024-01-03 10:05:40,034Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] CommandAsyncTask::HandleEndActionResult [within thread]: endAction for action type 'RemoveImage' succeeded, clearing tasks. 2024-01-03 10:05:40,034Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] SPMAsyncTask::ClearAsyncTask: Attempting to clear task 'b51f31d8-944b-4539-beb6-a0ab995073c6' 2024-01-03 10:05:40,034Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] START, SPMClearTaskVDSCommand( SPMTaskGuidBaseVDSCommandParameters:{storagePoolId='4c5f1e92-239b-471c-9db0-970029129a62', ignoreFailoverLimit='false', taskId='b51f31d8-944b-4539-beb6-a0ab995073c6'}), log id: 7535a00c 2024-01-03 10:05:40,035Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] START, HSMClearTaskVDSCommand(HostName = kvm-sandbox-qm7, HSMTaskGuidBaseVDSCommandParameters:{hostId='9fb846b0-58cf-41ab-875c-3e3118a24b89', taskId='b51f31d8-944b-4539-beb6-a0ab995073c6'}), log id: 3522ca07 2024-01-03 10:05:40,046Z INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] FINISH, HSMClearTaskVDSCommand, return: , log id: 3522ca07 2024-01-03 10:05:40,046Z INFO [org.ovirt.engine.core.vdsbroker.irsbroker.SPMClearTaskVDSCommand] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] FINISH, SPMClearTaskVDSCommand, return: , log id: 7535a00c 2024-01-03 10:05:40,050Z INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] BaseAsyncTask::removeTaskFromDB: Removed task 'b51f31d8-944b-4539-beb6-a0ab995073c6' from DataBase 2024-01-03 10:05:40,050Z INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedThreadFactory-engine-Thread-2965) [5871c85c] CommandAsyncTask::HandleEndActionResult [within thread]: Removing CommandMultiAsyncTasks object for entity '8640049f-0ead-486a-93b4-dcbbaa353294' 2024-01-03 10:05:42,583Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-11) [5871c85c] Command 'RemoveDisk' (id: 'b01c95d8-b3c3-40db-9a41-6fe1e817fe5a') waiting on child command id: '8640049f-0ead-486a-93b4-dcbbaa353294' type:'RemoveImage' to complete 2024-01-03 10:05:42,593Z INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommandCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-11) [5871c85c] Remove image command has completed successfully for disk '13dcaf25-6b58-4c79-85a7-0aecd153fb59' with async task(s) '[b51f31d8-944b-4539-beb6-a0ab995073c6]'. 2024-01-03 10:05:44,692Z INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-39) [5871c85c] Command 'RemoveDisk' id: 'b01c95d8-b3c3-40db-9a41-6fe1e817fe5a' child commands '[8640049f-0ead-486a-93b4-dcbbaa353294]' executions were completed, status 'SUCCEEDED' 2024-01-03 10:05:45,719Z INFO [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-26) [5871c85c] Ending command 'org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand' successfully. --- /snip --- Please let me know if I can supply additional information which could be relevant. Kind Regards, Justin Zandbergen.

1 0

ovirt-engine certificate renewal
by bill.hong＠neurogine.com 03 Jan '24

03 Jan '24

Hi, I'm running ovirt Version 4.5.3.2-1.el8 with 1 + 3 nodes setup. Currently i'm encountering this issue of ovirt-engine portal certificate which has already expired. "PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed " I'm aware of the solution by running "engine-setup --offline" to renew the cert. (https://yaohuablog.com/zh/ovirt-engine-upgrade-web-certificate) However my host machine has this problem with the psql command issue whenever i run the engine-backup. [root@server1~]# engine-backup --mode=backup Start of engine-backup with mode 'backup' scope: all archive file: /var/lib/ovirt-engine-backup/ovirt-engine-backup-20240103163047.backup log file: /var/log/ovirt-engine-backup/ovirt-engine-backup-20240103163047.log psql: /lib64/libpq.so.5: no version information available (required by psql) psql: /lib64/libpq.so.5: no version information available (required by psql) psql: /lib64/libpq.so.5: no version information available (required by psql) Backing up: psql: /lib64/libpq.so.5: no version information available (required by psql) psql: /lib64/libpq.so.5: no version information available (required by psql) psql: /lib64/libpq.so.5: no version information available (required by psql) Notifying engine - Files - Engine database 'engine' Notifying engine FATAL: Database engine backup failed [root@server1~]# dnf module list postgresql Last metadata expiration check: 1:55:29 ago on Wed 03 Jan 2024 02:38:30 PM +08. CentOS Stream 8 - AppStream Name Stream Profiles Summary postgresql 9.6 client, server [d] PostgreSQL server and client module postgresql 10 [d] client, server [d] PostgreSQL server and client module postgresql 12 [e] client, server [d] PostgreSQL server and client module postgresql 13 client, server [d] PostgreSQL server and client module postgresql 15 client, server PostgreSQL server and client module postgresql 16 client, server [d] PostgreSQL server and client module Question : 1. Should i fix the psql error first ? If i just want to renew my certificate , will the psql error cause me to fail to renew the cert in the "engine-setup --offline" command ? 2. What if after the "engine-setup --offline" failed to renew will my running VM be affected and down ? will there be any recovery method later ? will the reinstallation work on stand-alone machine ?

1 0

On-Premise to MS Azure Cloud Migration
by techieim 29 Dec '23

29 Dec '23

Hello All User At Ovrit, We are using a Ovrit 4.5 Stable version set of 3 physical server as cluster in to 3 setup. As we have migrated from Ovirt 4.2 to 4.5 version, our hardware are already got out warranty and our management don’t to refresh the hardware. Where they have ask us to migrated running VM’s on our infra to “MS Azure Cloud Migration” As Microsoft say in they KB (https://learn.microsoft.com/en-us/azure/site-recovery/migrate-tutorial-on-p… methods where Ovirt/RHV is not listed. We have try one test vm from out Ovirt infra to MS Azure Cloud Migration. Which get show migrated but after that server don’t boot up we have mostly mix of Linux(CentOS/Ubuntu)/Windows. Is any one has migrated Ovirt host vm’s to MS Azure Cloud Migration Regards Techieim.

1 0

DR plan
by 2707974＠gmail.com 28 Dec '23

28 Dec '23

Hi All, We wish to create some kind of DR plan for our OVM 4.4.10.7-1.0.22.el8 environment. Idea is to do storage replication of defined Storage Domains. steps: create LUN on storage present LUN to OVM create Storage Domain put VMs on Storage Domain on storage replicate LUN to another storage [or the same storage] Storage Domains contains OVF_STORE Now, recovery On live OVM present replica of LUN import Storage Domain But we cannot import replica LUN. Where to look for errors? Is this action possible it all? Facts OVM is the same version Storage is the same vendor LUN is browsable on SAN level and have differen WWIN, if we wish to add replicated LUN like new Storage Domain. Adding new Storage Domain mean that LUN will be formatted ... What I do wrong?

2 3

DRoVirt
by 2707974＠gmail.com 28 Dec '23

28 Dec '23

I need/wish to do replication of VMs from one sie to another Does anyone have experience with this? Is there any other solution like DRoVirt https://github.com/Storware/drovirt

1 0

Re: How to restore VMs from shared storage domain when HE and VMs are not accessible?
by Jorge Visentini 27 Dec '23

27 Dec '23

I'm not sure, but... maybe: 1 - Import the Shared Domain Storage 2 - Export the data (VMs/Disks) to a mount point 3 - Create a Local Storage (the Cluster will changed) 4 - Import the data (VMs/Disks) to a Local Storage. Cheers! Em qua., 27 de dez. de 2023 às 14:51, Gorrepati, Varsha < Varsha.Gorrepati(a)hughes.com> escreveu: > Can we import domain storage when we created it locally? > > This option did not work for ovirt 4.4.10.7-1.el8 version. > > > > > > Thanks and Regards, > > Varsha Gorrepati > > > > > > > > *From:* Jorge Visentini <jorgevisentini(a)gmail.com> > *Sent:* Wednesday, December 27, 2023 10:13 AM > *To:* Gorrepati, Varsha <Varsha.Gorrepati(a)hughes.com> > *Cc:* users(a)ovirt.org > *Subject:* Re: [ovirt-users] How to restore VMs from shared storage > domain when HE and VMs are not accessible? > > > > Hi, First of all, recreate the engine VM using your backup or starting > from scratch. Then, just import the domain storages and your VMs will be > there. Cheers! Em qua. , 27 de dez. de 2023 às 06: 29, Gorrepati, Varsha > via Users <users@ ovirt. org> > > ZjQcmQRYFpfptBannerStart > > *This Message Is From an Untrusted Sender * > > You have not previously corresponded with this sender. > > ZjQcmQRYFpfptBannerEnd > > Hi, > > > > First of all, recreate the engine VM using your backup or starting from > scratch. > Then, just import the domain storages and your VMs will be there. > > > > Cheers! > > > > Em qua., 27 de dez. de 2023 às 06:29, Gorrepati, Varsha via Users < > users(a)ovirt.org> escreveu: > > How to restore VMs from shared storage domain when HE and VMs are not > accessible? > > > > > > Thanks and Regards, > > Varsha Gorrepati > > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > <https://urldefense.com/v3/__https:/www.ovirt.org/privacy-policy.html__;!!Em…> > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > <https://urldefense.com/v3/__https:/www.ovirt.org/community/about/community-…> > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/C27HOFRCFDACX… > <https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ovir…> > > > > > -- > > Att, > > Jorge Visentini > +55 55 98432-9868 > -- Att, Jorge Visentini +55 55 98432-9868

1 0

[ovirt4.4][rockylinux8.9][tg3] Communication down between engine and host after setting up network
by Cyril VINH-TUNG 27 Dec '23

27 Dec '23

Dear all I have an issue with ~same environment~ to make tg3 nic communicate between rocky linux 8.9 oVirt 4.4 engine and rocky linux 8.9 fresh installed host. Thanks to this post (https://forums.centos.org/viewtopic.php?t=65299) I had to make the ifcfg simplications to make engine communicate with the host and therefore be able to install the host via ovirt web UI. Then after setting up the network via ovirt and reboot the host, I lost the communicatiin between ovirt engine and the host (even ping does not work). Note that I have a virtualized pfsense between engine and host. All firewalls are opened. From anywhere else than the engine subnet I can communicate with the host and the engine can also communicate with any device on the same subnet than the host... so my thought is that there might be some incompatible parameter between pfsense and the host.... but then 'why did it work before the vdsm installation ? :-/ ). This last fact makes me think that it's a vdsm/nmstate/ethtool parameter that I have to tune... Any help would be much appreciated... (host is a hp proliant DL360 with tg3 3.137 module coming from base rocky linux) [code] filename: /lib/modules/4.18.0-513.9.1.el8_9.x86_64/kernel/drivers/net/ethernet/broadcom/tg3.ko.xz firmware: tigon/tg3_tso5.bin firmware: tigon/tg3_tso.bin firmware: tigon/tg3.bin version: 3.137 license: GPL description: Broadcom Tigon3 ethernet driver author: David S. Miller (davem(a)redhat.com) and Jeff Garzik (jgarzik(a)pobox.com) rhelversion: 8.9 [/code]

1 1

[oVirt 4.4][RockyLinux 8.9] Engine loses connectivity with freshly installed hosts after network setup
by Cyril VINH-TUNG 27 Dec '23

27 Dec '23

Hello I have 2 freshly installed hosts with rockylinux 8.9 Then after setting up the network via ovirt and reboot, I lost the communication between ovirt engine and the host (even ping does not work). Note that I have a virtualized pfsense between engine and host. All firewalls are opened. From anywhere else than the engine subnet I can communicate with the host and the engine can also communicate with any device on the same subnet than the host... so my thought is that there might be some incompatible parameter between pfsense and the host.... but then 'why did it work before the vdsm installation ? :-/ ). This last fact makes me think that it's a vdsm/nmstate/ethtool parameter that I have to tune... Any help would be much appreciated...

1 1

Re: How to restore VMs from shared storage domain when HE and VMs are not accessible?
by Jorge Visentini 27 Dec '23

27 Dec '23

Hi, First of all, recreate the engine VM using your backup or starting from scratch. Then, just import the domain storages and your VMs will be there. Cheers! Em qua., 27 de dez. de 2023 às 06:29, Gorrepati, Varsha via Users < users(a)ovirt.org> escreveu: > How to restore VMs from shared storage domain when HE and VMs are not > accessible? > > > > > > Thanks and Regards, > > Varsha Gorrepati > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/C27HOFRCFDACX… > -- Att, Jorge Visentini +55 55 98432-9868

2 1

Creating snapshots of Windows VM result in Status Code: 500
by Jon Sattelberger 22 Dec '23

22 Dec '23

I receive a "Status Code: 500" popup whenever I attempt to create a snapshot for a Windows VM from the Administration Portal UI. It doesn't matter if the VM is powered on or off. Nor the OS designation set in the UI (setting Linux or Other...). The modal usually states: "Operation Canceled" followed by "Error while executing action: A Request to the Server failed with the following Status Code: 500" or "Error while executing query: null". There are at least a dozen popups, and will continue to repeat every few seconds. The snapshot tab in the Admin Portal UI will then have issues displaying the Active VM and the newly created snapshot entry. If you try to examine both entries, the disk, network, and installed applications might appear blank. The web inspector will usually contain the following: Fri Dec 22 09:43:07 GMT-500 2023 org.ovirt.engine.ui.frontend.Frontend SEVERE: Failed to execute runQuery: com.google.gwt.user.client.rpc.StatusCodeException: 500 Internal Server Error The call failed on the server; see server log for details com.google.gwt.user.client.rpc.StatusCodeException: 500 Internal Server Error The call failed on the server; see server log for details The engine logs will have: File: server.log 2023-12-22 09:43:04,387-05 ERROR [io.undertow.servlet] (default task-726) Exception while dispatching incoming RPC call: com.google.gwt.user.client.rpc.SerializationException: Can't find the serialization policy file. This probably means that the user has an old version of the application loaded in the browser. To solve the issue the user needs to close the browser and open it again, so that the application is reloaded. ... snip ... Caused by: com.google.gwt.user.client.rpc.SerializationException: Type 'org.ovirt.engine.core.common.utils.SecretValue' was not included in the set of types which can be serialized by this SerializationPolicy or its Class object could not be loaded. For security purposes, this type will not be serialized.: instance = *** The same snapshot will appear fine in the VM Portal. I am able to see the network interfaces, and disks. No issues creating a snapshot of a Linux-based VM from either UI interfaces. I've tried in both Firefox (115.5 ESR) and Google Chrome (latest-ish). Any thoughts on where to look next? Version 4.5.6-0 (git12af746179.el8) on RHEL 8. Thank you, Jon

1 0

Failed to validate GPG signature for ovirt-engine-appliance-4.5-20231201120201.1.el9.x86_64
by Jirka Simon 21 Dec '23

21 Dec '23

Hello ovirt people, please cloud you check ovirt-engine-appliance for centos stream 9? it returns ERROR ] fatal: [localhost]: FAILED! => {"attempts": 10, "changed": false, "msg": "Failed to validate GPG signature for ovirt-engine-appliance-4.5-20231201120201.1.el9.x86_64: Public key for ovirt-engine-appliance-4.5-20231201120201.1.el9.x86_64.rpm is not installed"} it is possible to install it manually with dnf -y install ovirt-engine-appliance --nogpgcheck jirka

1 0

Access Problem
by Vittorio 21 Dec '23

21 Dec '23

When i try to log in on Ovirt There is : "PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed" Can you help me?

1 0

Proxy error when deploying self hosted engine
by dhiabimen＠gmail.com 21 Dec '23

21 Dec '23

Hello, I'm trying to deploy a self hosted engine in a KVM node oracle linux 8.8. But I have got the following error: 2023-12-21 10:40:43,687+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Install Oracle oVirt repo using specified url] 2023-12-21 10:40:43,889+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 skipping: [localhost] 2023-12-21 10:40:44,091+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Install Oracle oVirt repo] 2023-12-21 10:41:28,976+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'results': [], 'rc': 1, 'msg': "Failed to download metadata for repo 'ol8 _baseos_latest': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for https://yum.oracle.com/repo/OracleLinux/OL8/baseos/latest/x86_64/repodata/r… [Could not resolve proxy: www-proxy.us.oracle.com]", 'invocation': {'module_args': {'name': ['oracle-ovirt-release-45-el8'], 'state': 'present', 'allow_downgrade': False, 'autoremove': False, 'bugfix' : False, 'cacheonly': False, 'disable_gpg_check': False, 'disable_plugin': [], 'disablerepo': [], 'download_only': False, 'enable_plugin': [], 'enablerepo': [], 'exclude': [], 'installroot' : '/', 'install_repoquery': True, 'install_weak_deps': True, 'security': False, 'skip_broken': False, 'update_cache': False, 'update_only': False, 'validate_certs': True, 'sslverify': True, 'lock_timeout': 30, 'allowerasing': False, 'nobest': False, 'conf_file': None, 'disable_excludes': None, 'download_dir': None, 'list': None, 'releasever': None}}, '_ansible_no_log': None, 'attempts': 10, 'changed': False, '_ansible_delegated_vars': {'ansible_host': '192.168.222.75', 'ansible_port': None, 'ansible_user': 'root', 'ansible_connection': 'smart'}} 2023-12-21 10:41:29,078+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.222.75]: FAILED! => {"attempts": 10, "changed ": false, "msg"2023-12-21 10:40:43,687+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Install Oracle oVirt repo using spe cified url] 2023-12-21 10:40:43,889+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 skipping: [localhost] 2023-12-21 10:40:44,091+0100 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Install Oracle oVirt repo] 2023-12-21 10:41:28,976+0100 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'results': [], 'rc': 1, 'msg': "Failed to download metadata for repo 'ol8 _baseos_latest': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for https://yum.oracle.com/repo/OracleLinux/OL8/baseos/latest/x86_64/repodata/r… [Could not resolve proxy: www-proxy.us.oracle.com]", 'invocation': {'module_args': {'name': ['oracle-ovirt-release-45-el8'], 'state': 'present', 'allow_downgrade': False, 'autoremove': False, 'bugfix' : False, 'cacheonly': False, 'disable_gpg_check': False, 'disable_plugin': [], 'disablerepo': [], 'download_only': False, 'enable_plugin': [], 'enablerepo': [], 'exclude': [], 'installroot' : '/', 'install_repoquery': True, 'install_weak_deps': True, 'security': False, 'skip_broken': False, 'update_cache': False, 'update_only': False, 'validate_certs': True, 'sslverify': True, 'lock_timeout': 30, 'allowerasing': False, 'nobest': False, 'conf_file': None, 'disable_excludes': None, 'download_dir': None, 'list': None, 'releasever': None}}, '_ansible_no_log': None, 'attempts': 10, 'changed': False, '_ansible_delegated_vars': {'ansible_host': '192.168.222.75', 'ansible_port': None, 'ansible_user': 'root', 'ansible_connection': 'smart'}} 2023-12-21 10:41:29,078+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.222.75]: FAILED! => {"attempts": 10, "changed ": false, "msg": "Failed to download metadata for repo 'ol8_baseos_latest': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for https://yum.oracle.com/repo/OracleLin ux/OL8/baseos/latest/x86_64/repodata/repomd.xml [Could not resolve proxy: www-proxy.us.oracle.com]", "rc": 1, "results": []} : "Failed to download metadata for repo 'ol8_baseos_latest': Cannot download repomd.xml: Curl error (5): Couldn't resolve proxy name for https://yum.oracle.com/repo/OracleLin ux/OL8/baseos/latest/x86_64/repodata/repomd.xml [Could not resolve proxy: www-proxy.us.oracle.com]", "rc": 1, "results": []} I have found that " www-proxy.us.oracle.com" is declared in the "dnf.conf" file of the ovirt engine created VM. How can I deploy the self hosted engine without having this error . Please note that I did not use any proxy. Thanks,

1 0

How restore nodes ovirt UP from NonResponsive and VMs executing
by carlos.mendes＠mgo.cv 21 Dec '23

21 Dec '23

Hello, The node (ovirt2) however is having consistent problems. The follow sequence of events is reproducible and is causing the host to enter a "NonOperational" state on the cluster: * Host ovirt2 installed * VDSM ovirt2 command ConnectStorageServerVDS failed: Message timeout which can be caused by communication issues * Host ovirt2 is not responding. Host cannot be fenced automatically because power management for the host is disabled. * Host ovirt2 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center DataCenter1. Setting Host state to Non-Operational. (5/27/1912:43:22 PM) * (Banner appears in GUI) Failed Activating Host ovirt2.witsconsult.com * Failed to connect Host ovirt2 to Storage Pool DataCenter1 (5/27/1912:47:07 PM) * Host ovirt2 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center DataCenter1. Setting Host state to Non-Operational. (5/27/1912:47:07 PM) * Host ovirt2 is not responding. Host cannot be fenced automatically because power management for the host is disabled. (5/27/1912:47:07 PM) * VDSM ovirt2 command ConnectStorageServerVDS failed: Message timeout which can be caused by communication issues (5/27/1912:47:07 PM) I can then re-activate ovirt2, which appears as green for approximately 5 minutes and then repeats all of the above issues. What can I do to troubleshoot this?

3 2

iSCSI Storage Domain Issues - Please Help
by Matthew J Black 20 Dec '23

20 Dec '23

Hi Guys & Gals, So I've been researching this issue online for a couple of days now and I can't seem to find a solution - so I'm hoping you kind people here can help. We're running oVirt (on Rocky 8, at the moment) with a iSCSI back-end provided by Ceph (Quincy, for the record). Everything from the Ceph-end looks AOK. However, none of the oVirt Hosts (and therefore the VMs) can connect to the Ceph iSCSI RBD Images (oVirt Storage Domains), and only one or two of the Hosts can log into the Ceph iSCSI Target - the others throw a "Failed to setup iSCSI subsystem" error. All of the existing iSCSI Storage Domains are in Maintenance mode, and when I try to do *anything* to them the logs spit out a "Storage domain does not exist:" message. I also cannot create a new iSCSI Storage Domain for a new Ceph pool - again, oVirt simply won't/can't see it, even though it clearly visable in the iSCSI section of the Ceph Dashboard (and in gwcli on the Ceph Nodes). All of this started happening after I ran an update of oVirt - including an "engine setup" with a full engine-vacuum. Nothing has changed on the Ceph-end. So I'm looking for help on 2 issues, which or may not be related: 1) Is there a way to "force" oVirt Hosts to log into iSCSI targets? This will mean all of the oVirt Hosts will be connected to all of the Ceph iSCSI Gateways. 2) I'm thinking that *somehow* the existing "Storage Domains" registered in oVirt have become orphaned, so they need to be "cleaned up" - is there a cli way to do this (I don't mind digging into SQL as I'm an old SQL engineer/admin from way back). Thoughts on how to do this - and if it should be done at all? Or should I simple detach the Storage Domain images from the relevant VMs and destroy the Storage Domains, recreate them (once I can get the oVirt Hosts to log back into the Ceph iSCSI Gateways), and then reattach the relevant images to the relevant VMs? I mean, after all, the data is good and available on the Ceph SAN, so there is only a little risk (as far as I can see) - but there are a *hell* of a lot of VMs to do to do this :-) Anyway, any and all help, suggestions, gotchas, etc, etc, etc, are welcome. :-) Cheers Dulux-Oz

2 1

oVirt 4.6 OS versions
by d03＠bornfree.org 20 Dec '23

20 Dec '23

Has it yet been decided which OS and version will be used for the oVirt 4.6 Hosted Engine and for 4.6 oVirt Node?

10 15

Clone VM Unable to start, went to maintenance in ovirt 4.3
by Arup Jyoti Thakuria 20 Dec '23

20 Dec '23

Hi Team, Clone VM Unable to start, went to maintenance in ovirt 4.3. OS Rocky Linux 9.3 Could you please put some lights? regards Arup

1 0

I missing hosted-engine hosts and manage, Can I restore admin with new engine and import datadomains?
by dortiz＠sinergyhard.com 19 Dec '23

19 Dec '23

I have 3 nodes with hosted engine and the hosts missing with the manage engine, I have a backup but not work fine. It's posible restore the infraestructure import the datadomains?

1 0

Fresh install ovirt node 4.5.5
by nowak.pawel.mail＠gmail.com 19 Dec '23

19 Dec '23

Hi, I made new install ovirt node and i can't login to www panel using the root account (bad user or password). SSH login works correctly. What may be the problem?

2 4

Ovirt 4.4.10 - Host deployment failure due to repository timeout
by tflau＠polyu.edu.hk 19 Dec '23

19 Dec '23

Hi, I faced host deployment issue on Ovirt 4.4.10 in this morning. After log review, it seems the repository took longer time to resolve the key from "https://ftp.yz.yamagata-u.ac.jp/pub/" (Default: 30 seconds) Is there any way to use another repository for resolving the issue? OS Version: Rocky Linux 8.9 Ovirt Version: 4.4.10 Error Message from host deployment log: 2023-12-19 09:29:10 HKT - TASK [ovirt-host-deploy-vdsm : Install ovirt-hosted-engine-setup package] ****** 2023-12-19 09:31:13 HKT - An exception occurred during task execution. To see the full traceback, use -vvv. The error was: OSError: Curl error (28): Timeout was reached for https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/R PM-GPG-KEY-EPEL-8 [Operation timed out after 30000 milliseconds with 0 out of 0 bytes received] fatal: [10.13.5.3]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/usr/lib/python3.6/site-packages/dnf/util.py\", line 115, in _urlopen\n repo._repo.downloadUrl(url, fo.fileno())\n File \"/usr/lib64/python3.6/site-packages/libdnf/repo.py\", line 499, in downloadUrl\n return _repo.Repo_downloadUrl(self, url, fd)\nRuntimeError: Curl error (28): Timeout was reached for https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-pr ojects/epel/RPM-GPG-KEY-EPEL-8 [Operation timed out after 30000 milliseconds with 0 out of 0 bytes received]\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"<stdin>\" , line 102, in <module>\n File \"<stdin>\", line 94, in _ansiballz_main\n File \"<stdin>\", line 40, in invoke_module\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n return _run_module_code(code, init_globals, r un_name, mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n mod_name, mod_spec, pkg_name, script_name)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n F ile \"/tmp/ansible_dnf_payload_nsszl6ze/ansible_dnf_payload.zip/ansible/modules/packaging/os/dnf.py\", line 1370, in <module>\n File \"/tmp/ansible_dnf_payload_nsszl6ze/ansible_dnf_payload.zip/ansible/modules/packaging/os/dnf.py\", line 1359, in main\n File \"/tmp/ansible_dnf_payload_nsszl6ze/ansible_dnf_payload.zip/ansible/modules/packaging/os/dnf.py\", line 1338, in run\n File \"/tmp/ansible_dnf_payload_nsszl6ze/ansible_dnf_payload.zip/ansible/modules/packaging/os/ dnf.py\", line 1242, in ensure\n File \"/usr/lib/python3.6/site-packages/dnf/base.py\", line 2494, in _get_key_for_package\n keys = dnf.crypto.retrieve(keyurl, repo)\n File \"/usr/lib/python3.6/site-packages/dnf/crypto.py\", line 18 5, in retrieve\n with dnf.util._urlopen(keyurl, repo=repo) as handle:\n File \"/usr/lib/python3.6/site-packages/dnf/util.py\", line 119, in _urlopen\n raise IOError(str(e))\nOSError: Curl error (28): Timeout was reached for https: //ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/RPM-GPG-KEY-EPEL-8 [Operation timed out after 30000 milliseconds with 0 out of 0 bytes received]\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact er ror", "rc": 1} Time required based on Curl Result: (Over 60 seconds) yum.repos.d]# curl -vvv --trace-time --connect-timeout 120 https://ftp.yz.yamagata-u.ac.jp/pub/linux/fedora-projects/epel/RPM-GPG-KEY-… 11:15:13.842041 * Trying 133.24.248.18... 11:15:13.842143 * TCP_NODELAY set 11:15:13.906252 * Connected to ftp.yz.yamagata-u.ac.jp (133.24.248.18) port 443 (#0) 11:15:13.907121 * ALPN, offering h2 11:15:13.907139 * ALPN, offering http/1.1 11:15:13.911221 * successfully set certificate verify locations: 11:15:13.911246 * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none 11:15:13.911353 * TLSv1.3 (OUT), TLS handshake, Client hello (1): 11:16:20.151979 * TLSv1.3 (IN), TLS handshake, Server hello (2):

1 0

Can`t upgrade my oVirt Node 4.5.0.2 to latest version 4.5.5.x
by Ivan Pashchuk 18 Dec '23

18 Dec '23

Dear all, I already updated oVirt engine to Version 4.5.5-1.el8 and go to update oVirt node, Removed and re added yum repositories on node host do not help. Reboot host not help too. Check update on host from engine said 'no updates found'. Can anyone help? # rpm -qa ovirt* ovirt-hosted-engine-setup-2.6.3-1.el8.noarch ovirt-imageio-daemon-2.4.3-1.el8.x86_64 ovirt-imageio-common-2.4.3-1.el8.x86_64 ovirt-openvswitch-2.15-3.el8.noarch ovirt-openvswitch-ipsec-2.15-3.el8.noarch ovirt-openvswitch-ovn-common-2.15-3.el8.noarch ovirt-openvswitch-ovn-host-2.15-3.el8.noarch ovirt-provider-ovn-driver-1.2.36-1.el8.noarch ovirt-host-dependencies-4.5.0-3.el8.x86_64 ovirt-release-host-node-4.5.0.2-1.el8.x86_64 ovirt-vmconsole-1.0.9-1.el8.noarch ovirt-node-ng-nodectl-4.4.2-1.el8.noarch ovirt-openvswitch-ovn-2.15-3.el8.noarch ovirt-hosted-engine-ha-2.5.0-1.el8.noarch ovirt-host-4.5.0-3.el8.x86_64 ovirt-vmconsole-host-1.0.9-1.el8.noarch ovirt-python-openvswitch-2.15-3.el8.noarch ovirt-ansible-collection-2.0.3-1.el8.noarch ovirt-imageio-client-2.4.3-1.el8.x86_64 # cat /usr/lib/os.release.d/ovirt-release-host-node NAME="CentOS Stream" VERSION="8" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="8.7.2205.0" VARIANT="oVirt Node 4.5.0.2" VARIANT_ID="ovirt-node" PRETTY_NAME="oVirt Node 4.5.0" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:8" HOME_URL="https://www.ovirt.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" PLATFORM_ID="platform:el8" # yum repolist repo id repo name centos-ovirt45 CentOS Stream 8 - oVirt 4.5 cs8-extras CentOS Stream 8 - Extras cs8-extras-common CentOS Stream 8 - Extras common packages onn-appstream oVirt Node Optional packages from CentOS Stream 8 - AppStream onn-baseos oVirt Node Optional packages from CentOS Stream 8 - BaseOS 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 CentOS Stream 8 - PowerTools

1 0

Can we import local storage domain?
by Gorrepati, Varsha 15 Dec '23

15 Dec '23

Can we import local storage domain? Thanks and Regards, Varsha Gorrepati

1 0

How to restore VMs from shared storage domain when HE and VMs are not accessible?
by Gorrepati, Varsha 15 Dec '23

15 Dec '23

How to restore VMs from shared storage domain when HE and VMs are not accessible? Thanks and Regards, Varsha Gorrepati

1 0

help: Hosted-engine lost data and how to recover vm config to deploy new cluster
by Pandey, Shreyas 15 Dec '23

15 Dec '23

Hi ovirt team, There are couple of questions I am struggling to get answers for. We have ovirt cluster setup on two servers. 1) The cluster went down and upon troubleshooting we noticed the hosted engine is not able to restart. [root@j3sv7sr01ctr01 ~]# hosted-engine --vm-status The hosted engine configuration has not been retrieved from shared storage yet, please ensure that ovirt-ha-agent service is running. [root@j3sv7sr01ctr01 ~]# ovirt-ha-agent and ovirt-ha-broker both are failing because of storage related issue. The glusterfs volume which is being used by hosted-engine doesnt have the hosted engine related configuration. [root@j3sv7sr01ctr01 ~]# cd /rhev/data-center/mnt/glusterSD/ [root@j3sv7sr01ctr01 glusterSD]# ls 10.52.60.131:_j3sv7sr01datastore3 [root@j3sv7sr01ctr01 glusterSD]# cd 10.52.60.131\:_j3sv7sr01datastore3/ [root@j3sv7sr01ctr01 10.52.60.131:_j3sv7sr01datastore3]# [root@j3sv7sr01ctr01 10.52.60.131:_j3sv7sr01datastore3]# ls -al total 1 drwxr-xr-x 4 vdsm kvm 95 Dec 12 20:26 . drwxr-xr-x 3 vdsm kvm 47 Dec 13 19:16 .. [root@j3sv7sr01ctr01 10.52.60.131:_j3sv7sr01datastore3]# [root@j3sv7sr01ctr01 10.52.60.131:_j3sv7sr01datastore3]# Also we dont have the snapshots of the glusterfs and so it looks like we cant get the hosted-engine data now. Is there anyway to recover the cluster from this state? We still have the metadata of the vms as shown below - [root@j3sv7sr01stg01 01a2b8d8-e360-41cc-beea-4080d48f436a]# pwd /mnt/datastore1/vms/6f2c0622-fa3b-48f4-b412-9bd6f20892cb/images/01a2b8d8-e360-41cc-beea-4080d48f436a [root@j3sv7sr01stg01 01a2b8d8-e360-41cc-beea-4080d48f436a]# [root@j3sv7sr01stg01 01a2b8d8-e360-41cc-beea-4080d48f436a]# [root@j3sv7sr01stg01 01a2b8d8-e360-41cc-beea-4080d48f436a]# [root@j3sv7sr01stg01 01a2b8d8-e360-41cc-beea-4080d48f436a]# [root@j3sv7sr01stg01 01a2b8d8-e360-41cc-beea-4080d48f436a]# cd .. [root@j3sv7sr01stg01 images]# cd .. [root@j3sv7sr01stg01 6f2c0622-fa3b-48f4-b412-9bd6f20892cb]# ls dom_md images [root@j3sv7sr01stg01 6f2c0622-fa3b-48f4-b412-9bd6f20892cb]# [root@j3sv7sr01stg01 6f2c0622-fa3b-48f4-b412-9bd6f20892cb]# ls images/ 01a2b8d8-e360-41cc-beea-4080d48f436a 39edc9c3-0f6a-4dc4-b0c9-8279c0d2301f 6841ade8-515b-438e-a464-87ee269b22aa b76b6031-a2ba-482b-a367-620521be9b9b e61b82ae-dae5-4131-b5f1-68050247ac11 05fc7f51-f217-419f-8dcd-781f363c6ec3 3bcf4941-9352-489d-b1cd-e81f6bac08e5 688f08fb-ec0b-4d4a-ba5f-aeb1ebea3c37 b8b48d39-6891-46a2-866c-dcfbd78d02a8 e6b473f9-e18d-49bd-af60-269baa6801ad 085fbfd5-523f-483c-b65f-b50fcdec4883 3c2c19a8-2c01-4487-b8c8-bf0e700f3a52 6ac1b668-6e17-48f9-b334-e271bfcb7788 b8e4bf92-1b68-4452-a2f5-244543a64467 ec9e26ab-fdc4-434c-bbf3-2959f3c1776c 08e0efb2-82de-4727-8527-dcdd134a75ef 3ebd222a-7f5e-4e27-bcb3-8fcdd3a2cfca 6f4ffa95-9855-46d1-b38f-c6fb90e9c92e bc7d3fd2-83a5-4c64-a68e-b50750ea1bee ef1d7d7d-ca6a-43c1-9f7c-3e52e1153842 0cba2187-6d43-4aa4-af8d-1c917aece6bb 401c7293-4f7f-4c47-b6c8-ff0a6f94fb0e 7a44c0a0-f202-423f-b390-13907fcf333e bcc9bc93-e7e3-4f6c-ae4c-f1911cfbebaf efb1b965-5e04-4537-954f-b5a70b95275b 18d527e7-822c-4faf-91d4-0be5940d3663 455dbdc1-2990-4474-ab1f-17767770bcb1 7d89ceb1-13b6-4646-8e1e-70e10a970b5f c12542d9-f9a9-417e-942e-d2b06a44d8d4 efc1d529-5fad-406d-baa5-100d187f8033 18ff181a-f620-49d8-a18d-92fb7c21e2d1 470e1c0e-f8f1-4477-9059-3220c68bad48 846bc7f5-6380-46ce-b31d-470bf2d10054 c27aeb05-e44e-447f-9563-5a8398eb73fc efd940ae-511a-4068-8c6c-97aaafbddcf4 1a2384e4-b850-4dae-a191-bb165c2833d9 48b7f23b-9041-4bd7-a4d9-6894117636e2 8cdf9897-5777-487c-967c-f2505f22755c c4874372-08e0-4ff3-9c5d-0404bdc7d194 f212e13e-3871-4c4a-8d15-450507202518 1a38eb80-6e21-4848-8518-943ac5625caf 4f709682-9159-40fa-b4c2-3080b26b72c3 903f9c51-9788-4a7d-b336-52a6fe4cc3ac c7ac51e0-4575-4d79-9cd9-247752df45a7 f4110154-4926-4019-8412-d76021aeb841 1d753f80-6811-4671-a807-865b7a04e11f 52634d4a-88f7-48e8-99c1-18e574b3cd23 9df26dbf-0370-40d4-badd-c0ad88cf96be c88fa564-2284-46ba-9784-5b66eac420be f6f910a9-0812-4fb1-8b70-bed869dcf580 21a99266-1c78-4271-a2ba-c65ad10cf26a 55356333-996e-4f13-86b3-ed064ec58ff7 a2b6ae87-71f9-41f7-97e8-90bb16e60517 cb354e40-5b5a-494f-a22d-b0a37fec09b3 fa7d2900-812f-4f9d-8f05-09a9321880d2 2330dbe1-abeb-4a0b-a4bd-e7e5fae68be2 57b097ed-9896-4a2c-a7a7-8ff387388752 a4b980d8-ff6a-4e10-a8ee-d4cfc9a4765a cb94ec8c-b29f-41cd-8b74-77687a69e75b fc63ae3e-35fb-4360-9c83-2089ec5d81c5 280fe3d4-dd16-49c7-ae7f-db8f70143f07 5bc471ba-52c9-4bbd-a1da-d2375e42b6bb a8afa44f-cf4f-4cc4-9fbb-5ce1b6be4bd5 d26d5671-6f6c-4b9b-81bc-d5a7e28eab0e ff0447dc-e950-4419-800b-495af75a5c65 31e2b9a1-946e-400b-be62-3c78575b23bc 5bf990c6-8898-41a9-bcc8-61bc81c872f9 a9fa7d64-70b3-46ce-9682-a976d86380fb da0c9b8e-66de-4283-85b4-f639205dd76a 355d27a1-ecc7-4e5d-bfe5-16d0e83d7df6 5c02176c-7ac1-4067-8cef-2be322798519 b171c219-0bb7-4619-aa45-886583f1dc5f dafdfde9-aa69-46f6-9f6d-9bf4ca7d5c94 39061360-c4d7-4852-a946-dee6a279039b 61dc998c-3ad9-404f-8103-82e66612e31d b578ddb5-da3b-4e73-9630-5ae605b92ee0 e1eb62b4-54a9-47a8-b2b2-bf8e3612f74c 39c0f701-574c-4795-91a4-60bfac700bcc 67f13533-2377-401b-8584-b0c2d70bad7c b6500cfa-d578-437c-98bb-602cd843228d e2fe200c-efa8-470c-a5cb-7a2ed6b50afa [root@j3sv7sr01stg01 6f2c0622-fa3b-48f4-b412-9bd6f20892cb]# [root@j3sv7sr01stg01 6f2c0622-fa3b-48f4-b412-9bd6f20892cb]# ls images/01a2b8d8-e360-41cc-beea-4080d48f436a/ e45d87e2-6fdb-41ab-9f1f-ac113db71ba5 e45d87e2-6fdb-41ab-9f1f-ac113db71ba5.meta f7529d80-f20b-46a8-bac4-5827afe2a648.lease e45d87e2-6fdb-41ab-9f1f-ac113db71ba5.lease f7529d80-f20b-46a8-bac4-5827afe2a648 f7529d80-f20b-46a8-bac4-5827afe2a648.meta [root@j3sv7sr01stg01 6f2c0622-fa3b-48f4-b412-9bd6f20892cb]# [root@j3sv7sr01stg01 6f2c0622-fa3b-48f4-b412-9bd6f20892cb]# 2) If we think of redeploying new cluster , can we use exisinting datastore which has the metdata of the vms to have the vms in its pre-outage state? What other options do we have here? Any help would be really important for us. Thanks!

1 0

Failed to migrate VM to Host ovirt3.XXX.cz due to an Error: Fatal error during migration. Trying to migrate to another Host.
by Jirka Simon 14 Dec '23

14 Dec '23

Hello there, after today's update I have problem with live migration to this host. with message 2023-12-14 10:00:01,089+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [67218183] VM '77f85710-45e7-43ca-b0f4-69f87766cc43'(ca1.access.prod.hq.sldev.cz) was unexpectedly detected as 'Down' on VDS '044b7175-ca36-49b2-b01b-0253f9af7e4f'(ovirt3.corp.sldev.cz) (expected on '858b8951-9b5a-4b8f-994e-4e11788c34d6') 2023-12-14 10:00:01,090+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-11) [67218183] START, DestroyVDSCommand(HostName = ovirt3.corp.sldev.cz, DestroyVmV DSCommandParameters:{hostId='044b7175-ca36-49b2-b01b-0253f9af7e4f', vmId='77f85710-45e7-43ca-b0f4-69f87766cc43', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 696e7f0e 2023-12-14 10:00:01,336+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-11) [67218183] FINISH, DestroyVDSCommand, return: , log id: 696e7f0e 2023-12-14 10:00:01,337+01 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [67218183] VM '77f85710-45e7-43ca-b0f4-69f87766cc43'(ca1.access.prod.hq.sldev.cz) was unexpectedly detected as 'Down' on VDS '044b7175-ca36-49b2-b01b-0253f9af7e4f'(ovirt3.corp.sldev.cz) (expected on '858b8951-9b5a-4b8f-994e-4e11788c34d6') 2023-12-14 10:00:01,337+01 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [67218183] Migration of VM 'ca1.access.prod.hq.sldev.cz' to host 'ovirt3.corp.sldev.c z' failed: VM destroyed during the startup. When I stop a VM and start it again it starts on affected without any problem, but migration doesn't work. thank you for any help. Jirka

3 6

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

virsh console support
by marek 13 Dec '23

13 Dec '23

hi, is it possible use virsh console on ovirt host? [root@server ~]# virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf console 21 --safe Connected to domain 'server-dev-1' Escape character is ^] (Ctrl + ]) error: internal error: character device ua-e4d8f97d-a7dd-4769-972c-27412212b955 is not using a PTY dumpxml 21 shows <console type='unix'> <source mode='bind' path='/var/run/ovirt-vmconsole-console/5a06d390-431c-48b5-9fb6-ebc34af73a88.sock'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> Marek

1 0

Move SHE to a LUN on another storage appliance
by Colin Coe 12 Dec '23

12 Dec '23

Hi all I'm decommissioning an old SAN that holds our DEV/TST RHV instance. I'm following https://access.redhat.com/solutions/6529691 (How to move the Hosted-Engine storage to a new storage domain) and I'm on step 9 (Make sure that the self-hosted engine is shut down). hosted-engine --vm-status is reporting: hosted-engine --vm-status | grep -E 'Engine status|Hostname' Engine status : {"vm": "up", "health": "good", "detail": "Up"} Hostname : rhvh01.example.com Engine status : {"vm": "down_unexpected", "health": "bad", "detail": "unknown", "reason": "vm not running on this host"} Hostname : rhvh02.example.com Even though the vm is definitely shut down. The instructions say call Red Hat but its nearly 6PM and we only have standard support for this environment. Any ideas on how to resolve this? I'm not sure if it's a big issue but I don't want to cause myself more problems later. Thanks

1 0

Migrate Hosted-Engine to different cluster
by Michaal R 12 Dec '23

12 Dec '23

I know this question pops up on a regular with this forum, but my best search engine manipulation turned up only to back up the engine configuration to a shared storage, then restore it on the other cluster using hosted-engine --deploy --restore-from-file=backup.tar.gz. While this is workable (it's by no means the end of the world for me), I wanted to ask if a different or better way has been or will be implemented. Here's why: I am trying to move to oVirt from ESXi (the latter has outgrown its usefulness to me and has become increasingly more difficult to maintain for my purposes, as VMware is intent on pushing newer CPU technologies with each new version, leaving perfectly good systems with perfectly good processors and hardware out in the cold. On top of that, VMware won't let you easily do vGPU or GPU passthrough without significant risk to the system stability.). I started with a VM on the ESXi host as a proof-of-concept for setting up and configuring oVirt to run the hosted engine and a couple of VMs. This worked after some great work from the members here on the forum (shout out to Tomas and Arik!). This initial cluster is an Intel CPU based cluster, as the server its VM is running on is an R720. This is the server I need to migrate off of (I have a plan). So I set up in VMware Workstation on my PC a second host in its own cluster (as that machine is an AMD CPU machine). Now, I know I can't live migr ate between clusters to begin with, but I was hoping there was an easier way to move the hosted-engine to the shared NAS storage, put the hosted-engine in maintenance mode, shut it down, change a variable or three with the --set-shared-config option (if that applies), run some script on the other host that starts the hosted-engine on that host in that cluster, bringing it out of maintenance mode automatically once up and verified stable. I understand that process COULD be slower and more fraught with danger than just simply backing up the config to shared storage and deploying on the AMD host with the restored config, but on the off-chance it ISN'T I wanted to explore that possibility. Besides, it would be a nice feature of the hosted-engine and oVirt as a whole if you could eventually right-click the hosted-engine VM in the portal and click "Move to new cluster...", which would automate that entire process for you. All that said, I'm working on one last problematic VM import before I start the arduous process of pulling everything off of ESXi and reformatting the R720 for oVirt. Hopefully that goes smoother than my start with oVirt. :)

2 1