- Users - oVirt List Archives

Unable to ugprade cluster level to 4.7 for the hosted engine (only)
by lists＠pequod.io 24 Jun '22

24 Jun '22

Hello, i upgraded my engine and nodes to 4.5 a few days ago and now planning to upgrade the cluster level compatibility from 4.6 to 4.7. First i tried doing this from the cluster settings, but it fails because hosted-engine settings are locked. So i tried it by hand but again got the locked error, i found i cant change any values on the hosted engine. Changing compatiblity level on all other VMs worked fine and there are on 4.7 now. I read about the timezone issue in 4.4.8, so i checked the timezone of my hosted engine it is filled with "Standard: (GMTZ) Greenwhich Standard Time". To be sure, i just did a "/usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "update vm_static SET time_zone='Etc/GMT' where vm_name='HostedEngine';"" and it changed the timezone, but settings are still locked and i am unable to change the compatibility level. Any idea how to solve this?

4 6

oVirt Node 4.5.1
by Lev Veyde 23 Jun '22

23 Jun '22

On June 23rd 2022 the oVirt project released an update of oVirt Node (4.5.1) delivering several security fixes, bug fixes and enhancements. The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. With oVirt 4.5.1 oVirt Node based on CentOS Stream 9 is also available as a tech preview. Known issues: - On oVirt Node based on CentOS Stream 9 with UEFI secure boot, vdsm fails to decode DMI data due to Bug 2081648 <https://bugzilla.redhat.com/show_bug.cgi?id=2081648> – python-dmidecode module fails to decode DMI data Updates on el8 based oVirt Node: Security fixes: - Important - Bug 2082616 <https://bugzilla.redhat.com/show_bug.cgi?id=2082616> - CVE-2022-24903 - rsyslog: Heap-based overflow in TCP syslog server - Important - Bug 2072376 <https://bugzilla.redhat.com/show_bug.cgi?id=2072376> - CVE-2018-25032 - zlib: A flaw in zlib-1.2.11 when compressing (not decompressing!) certain inputs. - Important - Bug 2065568 <https://bugzilla.redhat.com/show_bug.cgi?id=2065568> - CVE-2022-27666 - kernel: buffer overflow in IPsec ESP transformation code Other updates: - CentOS Stream 8 latest updates - Full list of changes compared to oVirt Node 4.5.0.3: oVirt Node 4.5.0.3 oVirt Node 4.5.1 NetworkManager 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-config-server 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-libnm 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-ovs 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-team 1.39.3-1.el8 1.39.5-1.el8 NetworkManager-tui 1.39.3-1.el8 1.39.5-1.el8 binutils 2.30-114.el8 2.30-116.el8 centos-release-ovirt45 8.7-1.el8s 8.7-2.el8s cockpit 264.1-1.el8 270-1.el8 cockpit-bridge 264.1-1.el8 270-1.el8 cockpit-storaged 264.1-1.el8 269-1.el8 cockpit-system 264.1-1.el8 270-1.el8 cockpit-ws 264.1-1.el8 270-1.el8 cronie 1.5.2-6.el8 1.5.2-7.el8 cronie-anacron 1.5.2-6.el8 1.5.2-7.el8 cups-libs 2.2.6-45.el8 device-mapper-multipath 0.8.4-23.el8 0.8.4-25.el8 device-mapper-multipath-libs 0.8.4-23.el8 0.8.4-25.el8 dnf 4.7.0-9.el8 4.7.0-10.el8 dnf-data 4.7.0-9.el8 4.7.0-10.el8 dracut 049-201.git20220131.el8 049-202.git20220511.el8 dracut-config-generic 049-201.git20220131.el8 049-202.git20220511.el8 dracut-live 049-201.git20220131.el8 049-202.git20220511.el8 dracut-network 049-201.git20220131.el8 049-202.git20220511.el8 dracut-squash 049-201.git20220131.el8 049-202.git20220511.el8 e2fsprogs 1.45.6-4.el8 1.45.6-5.el8 e2fsprogs-libs 1.45.6-4.el8 1.45.6-5.el8 elfutils-default-yama-scope 0.186-1.el8 0.187-4.el8 elfutils-libelf 0.186-1.el8 0.187-4.el8 elfutils-libs 0.186-1.el8 0.187-4.el8 fence-agents-all 4.2.1-94.el8 4.2.1-97.el8 fence-agents-amt-ws 4.2.1-94.el8 4.2.1-97.el8 fence-agents-apc 4.2.1-94.el8 4.2.1-97.el8 fence-agents-apc-snmp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-bladecenter 4.2.1-94.el8 4.2.1-97.el8 fence-agents-brocade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-cisco-mds 4.2.1-94.el8 4.2.1-97.el8 fence-agents-cisco-ucs 4.2.1-94.el8 4.2.1-97.el8 fence-agents-common 4.2.1-94.el8 4.2.1-97.el8 fence-agents-compute 4.2.1-94.el8 4.2.1-97.el8 fence-agents-drac5 4.2.1-94.el8 4.2.1-97.el8 fence-agents-eaton-snmp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-emerson 4.2.1-94.el8 4.2.1-97.el8 fence-agents-eps 4.2.1-94.el8 4.2.1-97.el8 fence-agents-heuristics-ping 4.2.1-94.el8 4.2.1-97.el8 fence-agents-hpblade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ibmblade 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ifmib 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-moonshot 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-mp 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo-ssh 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ilo2 4.2.1-94.el8 4.2.1-97.el8 fence-agents-intelmodular 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ipdu 4.2.1-94.el8 4.2.1-97.el8 fence-agents-ipmilan 4.2.1-94.el8 4.2.1-97.el8 fence-agents-kdump 4.2.1-94.el8 4.2.1-97.el8 fence-agents-mpath 4.2.1-94.el8 4.2.1-97.el8 fence-agents-redfish 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rhevm 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rsa 4.2.1-94.el8 4.2.1-97.el8 fence-agents-rsb 4.2.1-94.el8 4.2.1-97.el8 fence-agents-sbd 4.2.1-94.el8 4.2.1-97.el8 fence-agents-scsi 4.2.1-94.el8 4.2.1-97.el8 fence-agents-vmware-rest 4.2.1-94.el8 4.2.1-97.el8 fence-agents-vmware-soap 4.2.1-94.el8 4.2.1-97.el8 fence-agents-wti 4.2.1-94.el8 4.2.1-97.el8 glibc 2.28-200.el8 2.28-203.el8 glibc-common 2.28-200.el8 2.28-203.el8 glibc-langpack-en 2.28-200.el8 2.28-203.el8 kernel 4.18.0-383.el8 4.18.0-394.el8 kernel-core 4.18.0-383.el8 4.18.0-394.el8 kernel-modules 4.18.0-383.el8 4.18.0-394.el8 kernel-tools 4.18.0-383.el8 4.18.0-394.el8 kernel-tools-libs 4.18.0-383.el8 4.18.0-394.el8 kexec-tools 2.0.24-1.el8 2.0.24-2.el8 kpartx 0.8.4-23.el8 0.8.4-25.el8 libbasicobjects 0.1.1-39.el8 0.1.1-40.el8 libcap 2.48-2.el8 2.48-4.el8 libcollection 0.7.0-39.el8 0.7.0-40.el8 libcom_err 1.45.6-4.el8 1.45.6-5.el8 libdhash 0.5.0-39.el8 0.5.0-40.el8 libini_config 1.3.1-39.el8 1.3.1-40.el8 libldb 2.4.1-1.el8 2.5.0-1.el8 libpath_utils 0.2.1-39.el8 0.2.1-40.el8 libref_array 0.1.5-39.el8 0.1.5-40.el8 libss 1.45.6-4.el8 1.45.6-5.el8 libtdb 1.4.4-1.el8 1.4.6-1.el8 libtevent 0.11.0-0.el8 0.12.0-0.el8 libwbclient 4.15.5-8.el8 4.16.1-0.el8 mesa-dri-drivers 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-filesystem 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libEGL 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libGL 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libgbm 21.3.4-1.el8 21.3.4-1.0.1.el8 mesa-libglapi 21.3.4-1.el8 21.3.4-1.0.1.el8 nmap-ncat 7.70-6.el8 7.70-7.el8 openvswitch-selinux-extra-policy 1.0-28.el8 1.0-29.el8s osinfo-db 20211216-1.el8 20220516-1.el8 ovirt-ansible-collection 2.0.3-1.el8 2.1.0-1.el8 ovirt-hosted-engine-setup 2.6.3-1.el8 2.6.4-1.el8 ovirt-imageio-client 2.4.3-1.el8 2.4.5-1.el8 ovirt-imageio-common 2.4.3-1.el8 2.4.5-1.el8 ovirt-imageio-daemon 2.4.3-1.el8 2.4.5-1.el8 ovirt-node-ng-image-update-placeholder 4.5.0.3-1.el8 4.5.1-1.el8 ovirt-release-host-node 4.5.0.3-1.el8 4.5.1-1.el8 pacemaker-cluster-libs 2.1.2-4.el8 2.1.3-1.el8 pacemaker-libs 2.1.2-4.el8 2.1.3-1.el8 pacemaker-schemas 2.1.2-4.el8 2.1.3-1.el8 pam 1.3.1-16.el8 1.3.1-20.el8 python3-dnf 4.7.0-9.el8 4.7.0-10.el8 python3-perf 4.18.0-383.el8 4.18.0-394.el8 python38-ovirt-imageio-client 2.4.3-1.el8 2.4.5-1.el8 python38-ovirt-imageio-common 2.4.3-1.el8 2.4.5-1.el8 rpcbind 1.2.5-8.el8 1.2.5-9.el8 rsyslog 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-elasticsearch 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-mmjsonparse 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-mmnormalize 8.2102.0-9.el8 8.2102.0-10.el8 rsyslog-openssl 8.2102.0-9.el8 8.2102.0-10.el8 samba-client-libs 4.15.5-8.el8 4.16.1-0.el8 samba-common 4.15.5-8.el8 4.16.1-0.el8 samba-common-libs 4.15.5-8.el8 4.16.1-0.el8 scap-security-guide 0.1.60-7.el8 0.1.60-9.el8 selinux-policy 3.14.3-98.el8 3.14.3-99.el8 selinux-policy-targeted 3.14.3-98.el8 3.14.3-99.el8 sos 4.2-15.el8 4.3-1.el8 vdsm 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-api 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-client 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-common 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-gluster 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-http 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-jsonrpc 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-network 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-python 4.50.0.13-1.el8 4.50.1.4-1.el8 vdsm-yajsonrpc 4.50.0.13-1.el8 4.50.1.4-1.el8 yum 4.7.0-9.el8 4.7.0-10.el8 zlib 1.2.11-17.el8 1.2.11-19.el8 Additional resources: - Read more about the oVirt 4.5.1 release highlights: https://www.ovirt.org/release/4.5.1/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ Thanks in advance, -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

import vm disk image on ISCSI Data Domain
by sultanu＠inbox.ru 23 Jun '22

23 Jun '22

Hello, all Maybe somebody have experiance. I have cluster 3 hosts + ISCSI storage as Data Domain. How can i upload vm image from my old ovirt (baremetal with local storage) to my new cluster from CLI, NOT from WEB UI? Dowload on my local computer and post from WEB UI it take long period of time. Thak you for your time.

1 0

Lost space in /var/log
by Andrei Verovski 23 Jun '22

23 Jun '22

Hi ! I have strange situation with low disk space on /var/log/, yet I can't figure out what have consumed so much space. Look at the du output. Thanks in advance for any suggestion(s). # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/centos-var 15G 1.3G 13G 9% /var /dev/mapper/centos-var_log 7.8G 7.1G 293M 97% /var/log /dev/mapper/centos-var_log_audit 2.0G 41M 1.8G 3% /var/log/audit # # du -ah /var/log | sort -n -r | head -n 20 664K /var/log/vdsm 660K /var/log/vdsm/vdsm.log 624K /var/log/gdm 580K /var/log/anaconda/storage.log 480K /var/log/anaconda/packaging.log 380K /var/log/gdm/:0.log.4 316K /var/log/anaconda/syslog 276K /var/log/tuned 252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806 220K /var/log/Xorg.0.log 168K /var/log/gdm/:0.log 156K /var/log/yum.log-20191117 156K /var/log/secure-20180726 132K /var/log/libvirt/qemu/NextCloud-Collabora-Active.log 128K /var/log/anaconda/anaconda.log 120K /var/log/hp-snmp-agents 116K /var/log/hp-snmp-agents/cma.log 112K /var/log/vinchin 104K /var/log/vinchin/kvm_backup_service 104K /var/log/tuned/tuned.log.2 # # find . -printf '%s %p\n'| sort -nr | head -10 16311686 ./rhsm/rhsm.log 4070423 ./cron-20180726 3667146 ./anaconda/journal.log 3409071 ./secure 3066660 ./rhsm/rhsm.log-20180726 2912670 ./audit/audit.log 1418007 ./sanlock.log 1189580 ./vdsm/vdsm.log 592718 ./anaconda/storage.log 487567 ./anaconda/packaging.log

3 4

Re: Lost space in /var/log
by Michael Thomas 22 Jun '22

22 Jun '22

This can also happen with a misconfigured logrotate config. If a process is writing to a large log file, and logrotate comes along and removes it, then the process still has an open filehandle to the large file even though you can't see it. The space won't get removed until the process closes the filehandle (eg rebooting). The following command should give you a list of these ghost files that are still open but have been removed from the directory tree: lsof | grep '(deleted)' Stackexchange has some additional useful tips: https://unix.stackexchange.com/questions/68523/find-and-remove-large-files-… --Mike On 6/22/22 15:49, Matthew.Stier(a)fujitsu.com wrote: > Deleted some files to "clean up" /var/log, but the space was not recovered? > > Space for deleted files are only recovered when all references to that space are removed. This includes the directory reference, and any open file-handles to the file. > > The is a popular trick for a self-deleting scratch file. Create a file, open file-handle to it, and then remove the file. The open file-handle can then be written to, and read from, as long as you like, but when the file-handle is closed, explicitly or implicitly, the space is automatically recovered. > > > -----Original Message----- > From: Andrei Verovski <andreil1(a)starlett.lv> > Sent: Wednesday, June 22, 2022 3:27 PM > To: users(a)ovirt.org > Subject: [ovirt-users] Lost space in /var/log > > Hi ! > > I have strange situation with low disk space on /var/log/, yet I can't figure out what have consumed so much space. > Look at the du output. > > Thanks in advance for any suggestion(s). > > > # df -h > > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/centos-var 15G 1.3G 13G 9% /var > /dev/mapper/centos-var_log 7.8G 7.1G 293M 97% /var/log > /dev/mapper/centos-var_log_audit 2.0G 41M 1.8G 3% /var/log/audit > > # > # du -ah /var/log | sort -n -r | head -n 20 > > 664K /var/log/vdsm > 660K /var/log/vdsm/vdsm.log > 624K /var/log/gdm > 580K /var/log/anaconda/storage.log > 480K /var/log/anaconda/packaging.log > 380K /var/log/gdm/:0.log.4 > 316K /var/log/anaconda/syslog > 276K /var/log/tuned > 252K /var/log/libvirt/qemu/NextCloud-Collabora-LVM.log-20210806 > 220K /var/log/Xorg.0.log > 168K /var/log/gdm/:0.log > 156K /var/log/yum.log-20191117 > 156K /var/log/secure-20180726 > 132K /var/log/libvirt/qemu/NextCloud-Collabora-Active.log > 128K /var/log/anaconda/anaconda.log > 120K /var/log/hp-snmp-agents > 116K /var/log/hp-snmp-agents/cma.log > 112K /var/log/vinchin > 104K /var/log/vinchin/kvm_backup_service > 104K /var/log/tuned/tuned.log.2 > > # > # find . -printf '%s %p\n'| sort -nr | head -10 > > 16311686 ./rhsm/rhsm.log > 4070423 ./cron-20180726 > 3667146 ./anaconda/journal.log > 3409071 ./secure > 3066660 ./rhsm/rhsm.log-20180726 > 2912670 ./audit/audit.log > 1418007 ./sanlock.log > 1189580 ./vdsm/vdsm.log > 592718 ./anaconda/storage.log > 487567 ./anaconda/packaging.log > _______________________________________________ > 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/N566CST3DAXIL… > _______________________________________________ > 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/JCAQU32UZSEWK…

1 0

Q: Error ID 119 - ioctl(KVM_CREATE_VM) failed: Cannot allocate memory
by Andrei Verovski 22 Jun '22

22 Jun '22

Hi ! Does this error message means node runs out of RAM? Quite strange since there are about 20 GB of free RAN, and VM requires only 8. I noticed this happen till Vinchin was in a process of removing snapshot from another VM. Thanks. VM Jumis_VM-Active is down with error. Exit message: internal error: process exited while connecting to monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2022-06-22T19:50:46.501704Z qemu-kvm: failed to initialize KVM: Cannot allocate memory.

1 0

Move Master Storage Domain
by john＠penrod.net 22 Jun '22

22 Jun '22

Running oVirt 4.3.10. Three storage domains. #1 is the current master. No disks/data remain on it. All virtual machines have been moved. I plan to put it in maintenance mode and let it force an election. I don't care which of the remaining two become master. Will this impact virtual machines that are currently running? If possible, I need to keep them running. Thoughts?

1 0

Cannot export VM to another data domain. "o.original_template is undefined"
by Gilboa Davara 22 Jun '22

22 Jun '22

Hello, 4.4.10 Gluster based cluster w/ 3 nodes. I'm backing up all VMs before upgrading the setup to 4.5. (Hopefully done right before 4.5.1 w/ Gluster fix is released). When trying to export a VM to another data domain, several VMs show the following error: "Export VM Failed. o.original_template is undefined". Engine log looks clean (I see nothing about the failed upgrade). Any idea what's broken? - Gilboa

2 11

datacenter, node becam non responsive after power cut
by moulayhakim3＠yahoo.com 22 Jun '22

22 Jun '22

hello team, i have self hosted engine, after power cut , the datacenter and node becam non responsive, can you help me please

1 0

Gluster Volume cannot be activated Ovirt 4.5 Centos 8 Stream
by m.rohweder＠itm-h.de 21 Jun '22

21 Jun '22

Hi, i convertet my ovirt 4.5 tu ovirt 4.5 hyperconverged. (activate on cluster the gluster service and reinstalled all hosts) I can create bricks on hosts and i'm able to create a Volume. All with the Ovirt GUI. But if i want to activate the Volume, i get the error mesage that no host with running gluster is found in my cluster. All hosts show message that ovirt think glusterd ist not running, but its running on all hosts. What can i du to use gluster with the lokal storage on each host? Greatings Michael

2 2

Ovirt 4.4 - starting just-installed host from ovirt console fails
by David Johnson 21 Jun '22

21 Jun '22

Good afternoon all, I recently had to rebuild my cluster due to a self inflicted error. I have finally managed to get the ovirt host software installed and communicating on all hosts. The first host installed and started cleanly. However, after installation the second host is failing to start. Prior to my cluster crash, this host was running well in the cluster. During the downtime, we applied microcode and BIOS updates as part of the recovery process. I have reviewed this chain: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/N3PPT34GBRLPLT… and reached a dead end. Based on what I see (in the long stream of logs and info following), it looks like I should change the cluster CPU type from Cascadelake to Haswell to restore normal operation. The long involved stuff: The Engine reports: [image: image.png] Host CPU type is not compatible with Cluster Properties. [image: image.png] The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: model_Cascadelake-Server-noTSX. Please update the host CPU microcode or change the Cluster CPU Type. The Cluster definition is: [image: image.png] *lscpu returns:* Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 48 On-line CPU(s) list: 0-47 Thread(s) per core: 2 Core(s) per socket: 12 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel BIOS Vendor ID: Intel(R) Corporation CPU family: 6 Model: 63 Model name: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz BIOS Model name: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz Stepping: 2 CPU MHz: 3300.000 CPU max MHz: 3300.0000 CPU min MHz: 1200.0000 BogoMIPS: 4988.45 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 30720K NUMA node0 CPU(s): 0-11,24-35 NUMA node1 CPU(s): 12-23,36-47 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti intel_ppin ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts md_clear flush_l1d *cpuid returns:* CPU 0: vendor_id = "GenuineIntel" version information (1/eax): processor type = primary processor (0) family = 0x6 (6) model = 0xf (15) stepping id = 0x2 (2) extended family = 0x0 (0) extended model = 0x3 (3) (family synth) = 0x6 (6) (model synth) = 0x3f (63) (simple synth) = Intel (unknown type) (Haswell C1/M1/R2) {Haswell}, 22nm *virsh domcapabilities returns:* <domainCapabilities> <path>/usr/libexec/qemu-kvm</path> <domain>kvm</domain> <machine>pc-i440fx-rhel7.6.0</machine> <arch>x86_64</arch> <vcpu max='240'/> <iothreads supported='yes'/> <os supported='yes'> <enum name='firmware'/> <loader supported='yes'> <value>/usr/share/OVMF/OVMF_CODE.secboot.fd</value> <enum name='type'> <value>rom</value> <value>pflash</value> </enum> <enum name='readonly'> <value>yes</value> <value>no</value> </enum> <enum name='secure'> <value>no</value> </enum> </loader> </os> <cpu> <mode name='host-passthrough' supported='yes'> <enum name='hostPassthroughMigratable'> <value>on</value> <value>off</value> </enum> </mode> <mode name='maximum' supported='yes'> <enum name='maximumMigratable'> <value>on</value> <value>off</value> </enum> </mode> <mode name='host-model' supported='yes'> <model fallback='forbid'>Haswell-noTSX-IBRS</model> <vendor>Intel</vendor> <feature policy='require' name='vme'/> <feature policy='require' name='ss'/> <feature policy='require' name='vmx'/> <feature policy='require' name='pdcm'/> <feature policy='require' name='f16c'/> <feature policy='require' name='rdrand'/> <feature policy='require' name='hypervisor'/> <feature policy='require' name='arat'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='umip'/> <feature policy='require' name='md-clear'/> <feature policy='require' name='stibp'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='ssbd'/> <feature policy='require' name='xsaveopt'/> <feature policy='require' name='pdpe1gb'/> <feature policy='require' name='abm'/> <feature policy='require' name='invtsc'/> <feature policy='require' name='ibpb'/> <feature policy='require' name='ibrs'/> <feature policy='require' name='amd-stibp'/> <feature policy='require' name='amd-ssbd'/> <feature policy='require' name='skip-l1dfl-vmentry'/> <feature policy='require' name='pschange-mc-no'/> </mode> <mode name='custom' supported='yes'> <model usable='yes'>qemu64</model> <model usable='yes'>qemu32</model> <model usable='no'>phenom</model> <model usable='yes'>pentium3</model> <model usable='yes'>pentium2</model> <model usable='yes'>pentium</model> <model usable='yes'>n270</model> <model usable='yes'>kvm64</model> <model usable='yes'>kvm32</model> <model usable='yes'>coreduo</model> <model usable='yes'>core2duo</model> <model usable='no'>athlon</model> <model usable='yes'>Westmere-IBRS</model> <model usable='yes'>Westmere</model> <model usable='no'>Snowridge</model> <model usable='no'>Skylake-Server-noTSX-IBRS</model> <model usable='no'>Skylake-Server-IBRS</model> <model usable='no'>Skylake-Server</model> <model usable='no'>Skylake-Client-noTSX-IBRS</model> <model usable='no'>Skylake-Client-IBRS</model> <model usable='no'>Skylake-Client</model> <model usable='yes'>SandyBridge-IBRS</model> <model usable='yes'>SandyBridge</model> <model usable='yes'>Penryn</model> <model usable='no'>Opteron_G5</model> <model usable='no'>Opteron_G4</model> <model usable='no'>Opteron_G3</model> <model usable='yes'>Opteron_G2</model> <model usable='yes'>Opteron_G1</model> <model usable='yes'>Nehalem-IBRS</model> <model usable='yes'>Nehalem</model> <model usable='yes'>IvyBridge-IBRS</model> <model usable='yes'>IvyBridge</model> <model usable='no'>Icelake-Server-noTSX</model> <model usable='no'>Icelake-Server</model> <model usable='no' deprecated='yes'>Icelake-Client-noTSX</model> <model usable='no' deprecated='yes'>Icelake-Client</model> <model usable='yes'>Haswell-noTSX-IBRS</model> <model usable='yes'>Haswell-noTSX</model> <model usable='no'>Haswell-IBRS</model> <model usable='no'>Haswell</model> <model usable='no'>EPYC-Rome</model> <model usable='no'>EPYC-Milan</model> <model usable='no'>EPYC-IBPB</model> <model usable='no'>EPYC</model> <model usable='no'>Dhyana</model> <model usable='no'>Cooperlake</model> <model usable='yes'>Conroe</model> <model usable='no'>Cascadelake-Server-noTSX</model> <model usable='no'>Cascadelake-Server</model> <model usable='no'>Broadwell-noTSX-IBRS</model> <model usable='no'>Broadwell-noTSX</model> <model usable='no'>Broadwell-IBRS</model> <model usable='no'>Broadwell</model> <model usable='yes'>486</model> </mode> </cpu> <memoryBacking supported='yes'> <enum name='sourceType'> <value>file</value> <value>anonymous</value> <value>memfd</value> </enum> </memoryBacking> <devices> <disk supported='yes'> <enum name='diskDevice'> <value>disk</value> <value>cdrom</value> <value>floppy</value> <value>lun</value> </enum> <enum name='bus'> <value>ide</value> <value>fdc</value> <value>scsi</value> <value>virtio</value> <value>usb</value> <value>sata</value> </enum> <enum name='model'> <value>virtio</value> <value>virtio-transitional</value> <value>virtio-non-transitional</value> </enum> </disk> <graphics supported='yes'> <enum name='type'> <value>vnc</value> <value>spice</value> <value>egl-headless</value> </enum> </graphics> <video supported='yes'> <enum name='modelType'> <value>vga</value> <value>cirrus</value> <value>qxl</value> <value>virtio</value> <value>none</value> <value>bochs</value> <value>ramfb</value> </enum> </video> <hostdev supported='yes'> <enum name='mode'> <value>subsystem</value> </enum> <enum name='startupPolicy'> <value>default</value> <value>mandatory</value> <value>requisite</value> <value>optional</value> </enum> <enum name='subsysType'> <value>usb</value> <value>pci</value> <value>scsi</value> </enum> <enum name='capsType'/> <enum name='pciBackend'/> </hostdev> <rng supported='yes'> <enum name='model'> <value>virtio</value> <value>virtio-transitional</value> <value>virtio-non-transitional</value> </enum> <enum name='backendModel'> <value>random</value> <value>egd</value> <value>builtin</value> </enum> </rng> <filesystem supported='yes'> <enum name='driverType'> <value>path</value> <value>handle</value> <value>virtiofs</value> </enum> </filesystem> <tpm supported='yes'> <enum name='model'> <value>tpm-tis</value> <value>tpm-crb</value> </enum> <enum name='backendModel'> <value>passthrough</value> <value>emulator</value> </enum> </tpm> </devices> <features> <gic supported='no'/> <vmcoreinfo supported='yes'/> <genid supported='yes'/> <backingStoreInput supported='yes'/> <backup supported='yes'/> <sev supported='no'/> </features> </domainCapabilities> Please advise.

1 1

Preferred RHEL Based Distro For oVirt
by Clint Boggio 21 Jun '22

21 Jun '22

Good Day All; i am inquiring about which RHEL based distros are currently preferred and which ones are currently supported. I know the oVirt project is a RH entity and so RHEL and CentOS-Stream are the base offering. Would it, or is it, feasible for Rocky 8.X, or Alma 8.X to be the base OS for an oVirt deployment seeing as though they both RHEL clones ? How confident is the user community in the stability of CentOS-Stream in terms of production use as compared to Alma or Rocky ?

3 4

failed to mount hosted engine gluster storage - how to debug?
by diego.ercolani＠ssis.sm 21 Jun '22

21 Jun '22

Hello, I have an issue probably related to my particular implementation but I think some controls are missing Here is the story. I have a cluster of two nodes 4.4.10.3 with an upgraded kernel as the cpu (Ryzen 5) suffer from an incompatibility issue with the kernel provided by 4.4.10.x series. On each node there are three glusterfs "partitions" in replica mode, one for the hosted_engine, the other two are for user usage. The third node was an old i3 workstation only used to provide the arbiter partition to the glusterfs cluster. I installed a new server (ryzen processor) with 4.5.0 and successfully installed glusterfs 10.1 and inserted the arbiter bricks implemented on glusterfs 10.1 while the replica bricks are 8.6 after removing the old i3 provided bricks. I successfully imported the new node in the ovirt engine (after updating the engine to 4.5) The problem is that the ovirt-ha-broker doesn't start complaining that is not possible to connect the storage. (I suppose the hosted_engine storage) so I did some digs that I'm going to show here: #### 1. The node seem to be correctly configured: [root@ovirt-node3 devices]# vdsm-tool validate-config SUCCESS: ssl configured to true. No conflicts [root@ovirt-node3 devices]# vdsm-tool configure Checking configuration status... libvirt is already configured for vdsm SUCCESS: ssl configured to true. No conflicts sanlock is configured for vdsm Managed volume database is already configured lvm is configured for vdsm Current revision of multipath.conf detected, preserving Running configure... Done configuring modules to VDSM. [root@ovirt-node3 devices]# vdsm-tool validate-config SUCCESS: ssl configured to true. No conflicts #### 2. the node refuses to mount via hosted-engine (same error in broker.log) [root@ovirt-node3 devices]# hosted-engine --connect-storage Traceback (most recent call last): File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_setup/connect_storage_server.py", line 30, in <module> timeout=ohostedcons.Const.STORAGE_SERVER_TIMEOUT, File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/client/client.py", line 312, in connect_storage_server sserver.connect_storage_server(timeout=timeout) File "/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/storage_server.py", line 451, in connect_storage_server 'Connection to storage server failed' RuntimeError: Connection to storage server failed ##### 3. manually mount of glusterfs work correctly [root@ovirt-node3 devices]# grep storage /etc/ovirt-hosted-engine/hosted-engine.conf storage=ovirt-node2.ovirt:/gveng # The following are used only for iSCSI storage [root@ovirt-node3 devices]# [root@ovirt-node3 devices]# mount -t glusterfs ovirt-node2.ovirt:/gveng /mnt/tmp/ [root@ovirt-node3 devices]# ls -l /mnt/tmp total 0 drwxr-xr-x. 6 vdsm kvm 64 Dec 15 19:04 7b8f1cc9-e3de-401f-b97f-8c281ca30482 What else should I control? Thank you and sorry for the long message Diego

5 9

Virtual disk shareable checkbox is greyed out when using GlusterFS storage domains
by Ken Holmes 21 Jun '22

21 Jun '22

Is there a work around that will allow multiple VM's to share a disk with out using the network? I read Dave White's Thread but saw no resolution except maybe using NetApp. Thanks

1 0

moVirt delisted from Google Play
by Filip Krepinsky 21 Jun '22

21 Jun '22

Hi all, Unfortunately, we decided to delist moVirt from Google Play. As you might have noticed, the app has not been maintained for some time and also the main repository https://github.com/oVirt/moVirt has been archived. It is not possible for us to maintain store presence due to new requirements for Google APIs (and thus our libraries that are obsolete at this point), app interoperability and in general to fulfill expectations of our users. For users who still wish to use moVirt, you can keep your current application installed or download an APK ( https://github.com/oVirt/moVirt/releases/tag/v2.1) and install moVirt manually. Just keep in mind that the app might not behave properly (mostly on newer versions of Android). I hope moVirt has been helpful with managing your envs :) Best regards, Filip

1 0

Dedicated Migration Network
by Clint Boggio 21 Jun '22

21 Jun '22

Good Day All; I am in the process of assembling a new oVirt cluster and I am wondering if there is any benefit to having a dedicated set of nics solely dedicated to VM migration. If so, would those nics (bonded) be on their own vlan and subnet or would they share a subnet with gluster storage or the management network ? Right now i'm planning on the following architecture. 1. Management = 10G X2 Bond per hypervisor host (10.66.0.0/24) 2. Gluster/iSCSI Storage = 10G X2 Bond per hypervisor host (10.244.0.0/24) 3. VM Production Network(s) = 10G X2 Bond per hypervisor host (No IP Range) 4. ?? Possible Dedicated VM Migration Thank you very much as any input would be greatly appreciated

4 6

"Retrieval of iSCSI targets failed" during hosted engine deployment on oVirt node 4.5
by pat＠patfruth.com 21 Jun '22

21 Jun '22

I have freshly installed ovirt node 4.5 from the iso download here; https://resources.ovirt.org/pub/ovirt-4.5/iso/ovirt-node-ng-installer/4.5.0… output from 'rpm -qa | grep ovirt' shows ovirt-hosted-engine-setup-2.6.3-1.el8.noarch ovirt-imageio-daemon-2.4.3-1.el8.x86_64 python38-ovirt-engine-sdk4-4.5.1-1.el8.x86_64 ovirt-imageio-common-2.4.3-1.el8.x86_64 ovirt-node-ng-image-update-placeholder-4.5.0.3-1.el8.noarch ovirt-openvswitch-2.15-3.el8.noarch python38-ovirt-imageio-client-2.4.3-1.el8.x86_64 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 centos-release-ovirt45-8.7-1.el8s.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.3-1.el8.x86_64 ovirt-ansible-collection-2.0.3-1.el8.noarch ovirt-vmconsole-1.0.9-1.el8.noarch python3-ovirt-engine-sdk4-4.5.1-1.el8.x86_64 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-engine-appliance-4.5-20220511122240.1.el8.x86_64 ovirt-vmconsole-host-1.0.9-1.el8.noarch ovirt-python-openvswitch-2.15-3.el8.noarch python38-ovirt-imageio-common-2.4.3-1.el8.x86_64 python3-ovirt-node-ng-nodectl-4.4.2-1.el8.noarch cockpit-ovirt-dashboard-0.16.0-1.el8.noarch python3-ovirt-setup-lib-1.3.3-1.el8.noarch ovirt-imageio-client-2.4.3-1.el8.x86_64 During the hosted engine deployment process, I get thru Step 3 ( the "Prepare VM" step) successfully. On Step 4 (Storage Settings), I set; - Storage type = iSCSI - Portal IP address = my ISCSI target's ip address - Accept the default Portal port number, which is already set to 3260 - Leave username & password blank (as I have no CHAP configured on the ISCSI target system) When I click the "Retrieve Target List" button there is a brief pause, followed by red error message which says "Retrieval of iSCSI targets failed" Upon reviewing the files in /var/log/ovirt-hosted-engine-setup on the ovirt node, I find a new log file named ovirt-hosted-engine-setup-ansible-iscsi_discover-20220614084053-in517x.log The message near the end of the log file are as follows; ------ snip ------ ..... 2022-06-14 08:41:03,510-0600 INFO ansible task start {'status': 'OK', 'ansible_type': 'task', 'ansible_playbook': '/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml', 'ansible_task': 'ovirt.ovirt.hosted_engine_setup : iSCSI discover'} 2022-06-14 08:41:03,511-0600 DEBUG ansible on_any args TASK: ovirt.ovirt.hosted_engine_setup : iSCSI discover kwargs is_conditional:False 2022-06-14 08:41:03,511-0600 DEBUG ansible on_any args localhost TASK: ovirt.ovirt.hosted_engine_setup : iSCSI discover kwargs 2022-06-14 08:41:06,430-0600 DEBUG var changed: host "localhost" var "ansible_play_hosts" type "<class 'list'>" value: "[]" 2022-06-14 08:41:06,430-0600 DEBUG var changed: host "localhost" var "ansible_play_batch" type "<class 'list'>" value: "[]" 2022-06-14 08:41:06,430-0600 DEBUG var changed: host "localhost" var "play_hosts" type "<class 'list'>" value: "[]" 2022-06-14 08:41:06,431-0600 ERROR ansible failed { "ansible_host": "localhost", "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_result": { "_ansible_no_log": false, "changed": false, "exception": "Traceback (most recent call last):\n File \"/tmp/ansible_ovirt_host_payload_ky4zlp1s/ansible_ovirt_host_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host.py\", line 638, in main\nTypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'\n", "invocation": { "module_args": { "activate": true, "address": null, "check_upgrade": true, "cluster": null, "comment": null, "enroll_certificate": false, "fetch_nested": false, "force": false, "hosted_engine": null, "id": null, "iscsi": { "address": "192.168.1.2", "password": "", "port": null, "username": "" }, "kdump_integration": null, "kernel_params": null, "name": "ovirt-node01.internal.net", "nested_attributes": [], "override_display": null, "override_iptables": null, "password": null, "poll_interval": 3, "power_management_enabled": null, "public_key": false, "reboot_after_installation": null, "reboot_after_upgrade": true, "spm_priority": null, "ssh_port": null, "state": "iscsidiscover", "timeout": 600, "vgpu_placement": null, "wait": true } }, "msg": "int() argument must be a string, a bytes-like object or a number, not 'NoneType'" }, "ansible_task": "iSCSI discover", "ansible_type": "task", "status": "FAILED", "task_duration": 3 } 2022-06-14 08:41:06,431-0600 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f9c76744370> kwargs ignore_errors:None 2022-06-14 08:41:06,432-0600 INFO ansible stats { "ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", "ansible_playbook_duration": "00:11 Minutes", "ansible_result": "type: <class 'dict'>\nstr: {'localhost': {'ok': 5, 'failures': 1, 'unreachable': 0, 'changed': 0, 'skipped': 0, 'rescued': 0, 'ignored': 0}}", "ansible_type": "finish", "status": "FAILED" } 2022-06-14 08:41:06,432-0600 INFO SUMMARY: Duration Task Name -------- -------- [ < 1 sec ] Execute just a specific set of steps [ 00:01 ] Force facts gathering [ 00:03 ] Obtain SSO token using username/password credentials [ 00:03 ] Fetch host facts [ FAILED ] iSCSI discover 2022-06-14 08:41:06,432-0600 DEBUG ansible on_any args <ansible.executor.stats.AggregateStats object at 0x7f9c793444c0> kwargs ------ snip ------ The error suggest that the iSCSI portal port number (which is defaulted to 3260 in the UI) is not being properly passed into the python module ovirt/ovirt/plugins/modules/ovirt_host.py Looking at the code at line 638 of ovirt_host.py, found here; https://github.com/oVirt/ovirt-ansible-collection/blob/2.0.3-1/plugins/modu… I see; ..... elif state == 'iscsidiscover': host_id = get_id_by_name(hosts_service, module.params['name']) iscsi_param = module.params['iscsi'] iscsi_targets = hosts_service.service(host_id).discover_iscsi( iscsi=otypes.IscsiDetails( port=int(iscsi_param.get('port', 3260)), <---- line 638 username=iscsi_param.get('username'), password=iscsi_param.get('password'), address=iscsi_param.get('address'), portal=iscsi_param.get('portal'), ), ) ret = { 'changed': False, 'id': host_id, 'iscsi_targets': [iscsi.target for iscsi in iscsi_targets], 'iscsi_targets_struct': [get_dict_of_struct( struct=iscsi, connection=connection, fetch_nested=module.params.get('fetch_nested'), attributes=module.params.get('nested_attributes'), ) for iscsi in iscsi_targets], } ..... I'm not a Python expert, so I can't tell if this logic is correct or not. Looking at Git history on this code, it looks like the last time a change was made effecting ISCSI was in May of 2021; https://github.com/oVirt/ovirt-ansible-collection/commit/1c4c18d844a69b821f… By Martin Necas - https://github.com/mnecas I gotta believe I'm not the first one to try setting up oVirt 4.5 hosted engine with ISCSI storage. Is anyone else out there using ISCSI storage with oVirt 4.5.0.3 yet? How did you get it working?

2 2

Release announcement: go-ovirt-client 1.0.0, terraform-provider-ovirt 2.0.0
by Janos Bonic 20 Jun '22

20 Jun '22

Hey there folks, Just a quick announcement, we have released the first stable version of *go-ovirt-client*, an overlay for the go SDK which you can find here: https://github.com/ovirt/go-ovirt-client and the docs are available here: https://pkg.go.dev/github.com/ovirt/go-ovirt-client In parallel, we also released the first stable version of the *overhauled Terraform provider*, which is available on the Terraform registry: https://registry.terraform.io/providers/oVirt/ovirt/latest/docs Thank you to everyone who worked on this over the last year and made it possible. Contributors lists are here: https://github.com/oVirt/go-ovirt-client/graphs/contributors and here: https://github.com/oVirt/terraform-provider-ovirt/graphs/contributors If you run into problems, our GitHub issue box is always open. :) Cheers, Janos

1 0

Issue adding host to ovirt 4.4 cluster
by David Johnson 20 Jun '22

20 Jun '22

Good morning all, I am attempting to add a host to my ovirt 4.4 cluster. The installation of the first host went smoothly, but the installation of the second host stalled. Currently, the second host is in Installing state, but doing nothing. The installation failed due to a failure to register the host certificate. I cannot change the state of the host or retry the installation to capture logs. Warnings from the host that are visible on the ovirt console are: - Power Management is not configured for this Host. Enable Power Management - Host has no default route. - The host CPU does not match the Cluster CPU Type and is running in a degraded mode. It is missing the following CPU flags: vmx, model_Cascadelake-Server-noTSX. Please update the host CPU microcode or change the Cluster CPU Type. The error message generated at the last attempt to install the host from the ovirt console is: - Failed to enroll certificate for host ovirt-host-04 (User: admin@internal-authz). Please advise

1 1

Re: Dedicated Migration Network
by Clint Boggio 20 Jun '22

20 Jun '22

Thank you Abe, Angus, and Strahil. I appreciate your direction and input.

1 0

Re: oVirt 4.4.x step-by-step procedure to renew expired oVirt certificates
by Nathanaël Blanchet 20 Jun '22

20 Jun '22

Hi, Le 17/06/2022 à 12:18, Marko Vrgotic a écrit : > > Dear Nathanael, > > Thank you very much for you reply. Regarding host expiration playbook > you wrote – my compliments – is it safe to run on host with expired > certificates, or its rather meant to be executed for renewal of certs > on hosts with still valid certs? > both are okay, in case of a host in "up" status, it will go down during the playbook execution, but vms will continue to run without any downtime. Host will recover and go up once certificates will be successfully renewed. This is an emergency procedure, the best solution to renew a certificate on a running host is to put the host into maintenance and renew certs via UI. > We have also found following script which should at least safely take > care of the renewal of certs on host with already expired certificates > - . > > https://github.com/tothf/renew_vdsm_cert/blob/main/renew_vdsm_cert.sh > > ----- > > kind regards/met vriendelijke groeten > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > *o: *+31 (35) 6774131 > > *m: +*31 (65) 5734174** > > *e:*m.vrgotic@activevideo.com <mailto:m.vrgotic@activevideo.com> > *w: *www.activevideo.com <http://www.activevideo.com> > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein > 1.1217 WJ Hilversum, The Netherlands. The information contained in > this message may be legally privileged and confidential. It is > intended to be read only by the individual or entity to whom it is > addressed or by their designee. If the reader of this message is not > the intended recipient, you are on notice that any distribution of > this message, in any form, is strictly prohibited. If you have > received this message in error, please immediately notify the sender > and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and > delete or destroy any copy of this message. > > *From: *Nathanaël Blanchet <blanchet(a)abes.fr> > *Date: *Thursday, 16 June 2022 at 14:40 > *To: *Marko Vrgotic <M.Vrgotic(a)activevideo.com>, users(a)ovirt.org > <users(a)ovirt.org> > *Subject: *Re: [ovirt-users] oVirt 4.4.x step-by-step procedure to > renew expired oVirt certificates > > ***CAUTION: This email originated from outside of the organization. Do > not click links or open attachments unless you recognize the sender!!!*** > > Hello, > > If you refer to: > > 1. engine apache certificate expiration ("PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException:) to > access to ovirt console. > => engine-setup --offline > 2. hosts certificate expiration? > => https://access.redhat.com/solutions/3532921 > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccess.re…> > I also wrote a playbook to do so there: > https://galaxy.ansible.com/natman/ovirt_renew_certs > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgalaxy.an…> > In this case, don't forget to renew certificate with UI (into > maintenance) when host is reponding, otherwise you may enconter > issues with console or live migration or other SSL related stuff. > > tested and approved. > > Le 16/06/2022 à 12:34, Marko Vrgotic a écrit : > > Dear oVirt, > > The oVirt SSL certificated were changed to one-year renewal and we > have a problem now. > > We are running 4.4.x version with SHE on local storage cluster and > we have four more local storage clusters. > > One the cluster running SHE, the engine and host certificates have > expired. We found the procedure for renewal prior to expiration, > but we do not have a mnual one, required once certificates have > expired. > > Would you be so kind to share the manual or steps needed to fix > our oVirt setup. > > Thank you in advance. > > ----- > > kind regards/met vriendelijke groeten > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > *o: *+31 (35) 6774131 > > *m: +*31 (65) 5734174 > > *e:*m.vrgotic@activevideo.com <mailto:m.vrgotic@activevideo.com> > *w: *www.activevideo.com <http://www.activevideo.com> > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein > 1.1217 WJ Hilversum, The Netherlands. The information contained in > this message may be legally privileged and confidential. It is > intended to be read only by the individual or entity to whom it is > addressed or by their designee. If the reader of this message is > not the intended recipient, you are on notice that any > distribution of this message, in any form, is strictly > prohibited. If you have received this message in error, please > immediately notify the sender and/or ActiveVideo Networks, LLC by > telephone at +1 408.931.9200 and delete or destroy any copy of > this message. > > > > _______________________________________________ > > Users mailing list --users(a)ovirt.org > > To unsubscribe send an email tousers-leave(a)ovirt.org > > Privacy Statement:https://www.ovirt.org/privacy-policy.html <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > > oVirt Code of Conduct:https://www.ovirt.org/community/about/community-guidelines/ <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > > List Archives:https://lists.ovirt.org/archives/list/users@ovirt.org/message/5LOT… <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> > > -- > Nathanaël Blanchet > Supervision réseau > SIRE > 227 avenue Professeur-Jean-Louis-Viala > 34193 MONTPELLIER CEDEX 5 > Tél. 33 (0)4 67 54 84 55 > Fax 33 (0)4 67 54 84 14 > blanchet(a)abes.fr -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

1 0

After attaching the Storage domain, the VMs are disappeared from the VM import
by aminur.rahman＠iongroup.com 20 Jun '22

20 Jun '22

Hi, We're noticing some weird issue while re-attaching the storage domain. After re-attach the storage domain, some VMs are completely missing from the VM Import. Before detaching the storage domain, all the VMs were shutdown gracefully. I also noticed some disks are exists with no Alias under the disk import on the storage domain and I can't import those disks. Its failed to register the disk with <UNKONOWN> error. We're using Ovirt 4.2 with multiple Dell hosts in the cluster and Compellent SAN with iSCSI volumes. Please kindly advise if I am missing anything before detach the storage domain. Thanks

4 4

Delete the post :
by khznm 21 18 Jun '22

18 Jun '22

Dear Admin Pls delete the post under the below subject line , posted on June 18, 2022, 3:51 p.m. [ovirt-users] The he_fqdn proposed for the engine VM resolves on this host The post is incorrect and the problem was corrected sorry for the inconvenience caused. regards/khznm

1 0

The he_fqdn proposed for the engine VM resolves on this host
by khznm 21 18 Jun '22

18 Jun '22

Installing oVirt is not so easy as stated, i am struck up in FQDN resolution , i have this FQDN (vmanager.headache.com) resolve to ip 10.1.1.6 in DNS within the network,additionally i also input this entries into /etc/hosts file. while installing ( may be 8 times ) ,i am struck up with error " he_fqdn proposed for the engine VM resolves on this host " . The network is using vlan ip, the host is already installed bare metal into cisco c240-m5 with RH virtualization ver 4.4 ,its installed on IP :10.1.1.5. the problem is with installing the self hosted engine (ovirt). the vlan are like eno2.vlan7 and eno2.vlan7.1 /etc/hosts 10.1.1.6 vmanager.headache.com vmanager 10.1.1.5 vhrh1.headache.com vhrh1 10.1.1.6 vmanager.headache.com 10.1.1.5 vhrh1.headache.com i even tried cli install,,here also the same issue .. below are the error .. Host name is not valid: vmanager.headache.com resolves to 10.1.1.6 Host name is not valid: vman.headache.com did not resolve into an IP address Pls any body help here ,,,what i am doing wrong...

1 1

Cannot log into oVirt Manager - certificate issue
by Diggy Mc 18 Jun '22

18 Jun '22

I cannot log into oVirt Manager. My browser gave me a warning that the site's certificate has expired. Then when I try to log in, I receive the following error message: "PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed" How can I fix this problem? In advance, thank you for your help. hosted-engine: v4.4.8.6 hosts: oVirt Node v4.4.8.3

7 24