October 2022 - Users - oVirt List Archives

Re: OVS Task Error when Add EL Host
by erdosi.peter＠kifu.gov.hu 13 Oct '22

13 Oct '22

Actually, there are some strange stuff going on a newly deployed HE: [root@poc ~]# yum update Failed to set locale, defaulting to C.UTF-8 Last metadata expiration check: 0:34:52 ago on Fri Oct 14 01:09:57 2022. Error: Problem 1: package ovirt-openvswitch-2.15-4.el8.noarch requires openvswitch2.15, but none of the providers can be installed - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-119.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-106.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-110.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-115.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-117.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-22.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-23.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-24.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-27.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-30.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-32.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-35.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-37.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-39.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-41.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-47.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-48.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-51.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-52.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-53.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-54.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-56.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-6.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-72.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-75.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-80.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-81.el8s.x86_64 - package rdo-openvswitch-2:2.17-3.el8.noarch obsoletes openvswitch2.15 < 2.17 provided by openvswitch2.15-2.15.0-88.el8s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-2.15-4.el8.noarch - cannot install the best update candidate for package openvswitch2.15-2.15.0-119.el8s.x86_64 Problem 2: package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch requires ovn-2021, but none of the providers can be installed - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-82.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-21.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.03.0-40.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-17.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.06.0-29.el8s.x86_64 - package rdo-ovn-2:22.06-3.el8.noarch obsoletes ovn-2021 < 22.06 provided by ovn-2021-21.12.0-11.el8s.x86_64 - cannot install the best update candidate for package ovn-2021-21.12.0-82.el8s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-ovn-common-2.15-4.el8.noarch Problem 3: package ovirt-openvswitch-ovn-central-2.15-4.el8.noarch requires ovn-2021-central, but none of the providers can be installed - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.12.0-82.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.03.0-21.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.03.0-40.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.06.0-17.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.06.0-29.el8s.x86_64 - package rdo-ovn-central-2:22.06-3.el8.noarch obsoletes ovn-2021-central < 22.06 provided by ovn-2021-central-21.12.0-11.el8s.x86_64 - cannot install the best update candidate for package ovn-2021-central-21.12.0-82.el8s.x86_64 - cannot install the best update candidate for package ovirt-openvswitch-ovn-central-2.15-4.el8.noarch Problem 4: package ovirt-python-openvswitch-2.15-4.el8.noarch requires python3-openvswitch2.15, but none of the providers can be installed - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-119.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-106.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-110.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-115.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-117.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-22.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-23.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-24.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-27.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-30.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-32.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-35.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-37.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-39.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-41.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-47.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-48.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-51.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-52.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-53.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-54.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-56.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-6.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-72.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-75.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-80.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-81.el8s.x86_64 - package python3-rdo-openvswitch-2:2.17-3.el8.noarch obsoletes python3-openvswitch2.15 < 2.17 provided by python3-openvswitch2.15-2.15.0-88.el8s.x86_64 - cannot install the best update candidate for package python3-openvswitch2.15-2.15.0-119.el8s.x86_64 - cannot install the best update candidate for package ovirt-python-openvswitch-2.15-4.el8.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Maybe this can give a clue to someone. I used this iso: ovirt-node-ng-installer-4.5.2-2022081013.el8

1 0

Re: OVS Task Error when Add EL Host
by erdosi.peter＠kifu.gov.hu 13 Oct '22

13 Oct '22

I have a same issue with an installation today (oVirt 4.5.2, based on Centos Stream 8)

1 0

Disks in "Finalizing" state on Web Inteface
by markeczzz＠gmail.com 13 Oct '22

13 Oct '22

Hi! I have few vm-s that have disk status in "Finalizing" This VMs are working normally, but on web interface status is always "Finalizing" and progress bar is not moving. (It's in this state for days now) I can create snapshots and backups of them without problems and everything works ok. Is there any way that I can check why are this disks in that state? Regards,

1 0

Cannot run VM. The Custom Compatibility Version of VM ... (4.3) is not supported in Data Center compatibility version 4.4.
by nicolas＠devels.es 13 Oct '22

13 Oct '22

Hi, I'm running oVirt 4.4 and recently I changed the Data Center compatibility version from 4.3 to 4.4. Now turns out that some Pools are unable to restart machines, returning this error: Cannot run VM. The Custom Compatibility Version of VM ... (4.3) is not supported in Data Center compatibility version 4.4. I cannot edit manually the custom compatibility version of VMs, as pools won't allow that. Is there any manual way to fix it? I tried to do it via Python SDK but it doesn't seem to work... vm = vms_serv.list(name='X')[0] ver = vm.custom_compatibility_version ver.minor = 4 vm.custom_compatibility_version = ver vmsv = sys_serv.vms_service().vm_service(id=vm.id) vmsv.upfate(vm=vm) It doesn't seem to do any difference, though. Any help is really appreciated, as many our users can't use theis VMs. Thanks.

1 1

Ovirt support on el9
by Nathanaël Blanchet 13 Oct '22

13 Oct '22

Hello, is there a plan for an official el9 support ?

1 0

Upgrading from ovirt 4.5 rhel8 to rhel9
by Robert Pouliot 12 Oct '22

12 Oct '22

Hi, my setup is 3 physical servers with glusterfs. One of them had ovirt-engine. Usually my upgrade was (from 4.2, 4.3, 4.4, 4.5): engine-backup reinstall OS yum install ovirt-engine engine-backup: restore engine-setup. My main server was RHEL 8.6, ovirt 4.52. I did the backup, install AlmaLinux 9. But the package doesn't exist anymore with rhel9. Is the engine on bare-metal still available with rhel9? If not, is it possible to install the appliance with the saved config file with a different hostname and IP for the appliance? Thanks

1 0

Invalid GPG keys for rhel9 package
by Robert Pouliot 12 Oct '22

12 Oct '22

Hi, OS used is AlmaLinux 9.0. I tried to install the appliance with "hosted-engine", but unfortunately it complained about invalid GPG keys. The last 2 lines of the Key block seem strange. How can I fix this? I get the following message: [root@master ~]# yum install ovirt-engine-appliance Last metadata expiration check: 3:08:01 ago on Wed 12 Oct 2022 05:38:43 PM EDT. Dependencies resolved. ==================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================== Installing: ovirt-engine-appliance x86_64 4.5-20220419160254.1.el9 ovirt-45-upstream 1.6 G Transaction Summary ==================================================================================================================================== Install 1 Package Total download size: 1.6 G Installed size: 1.6 G Is this ok [y/N]: y Downloading Packages: ovirt-engine-appliance-4.5-20220419160254.1.el9.x86_64.rpm 17 MB/s | 1.6 GB 01:36 ------------------------------------------------------------------------------------------------------------------------------------ Total 15 MB/s | 1.6 GB 01:45 oVirt upstream for CentOS Stream 9 - oVirt 4.5 682 kB/s | 2.9 kB 00:00 Importing GPG key 0xFE590CB7: Userid : "oVirt <infra(a)ovirt.org>" Fingerprint: 31A5 D783 7FAD 7CB2 86CD 3469 AB8C 4F9D FE59 0CB7 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 Is this ok [y/N]: y Key import failed (code 2). Failing package is: ovirt-engine-appliance-4.5-20220419160254.1.el9.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oVirt-4.5 The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'yum clean packages'. Error: GPG check FAILED Here is a part of the GPG key: -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.22 (GNU/Linux) mQENBFM3+3YBCADTLqGw5hI0whRPeN0hSjpaZ2yNNtVzgqj8/EFQ9IfR7GasHz/4 kkT3cpKXZygo0AIVEe5dkrcYXF+9C6bowiuGZG+9G6j8MXneunRv7S0mv1mnx7MW [snip] FFm7Fr9czelRSW+NCUvvtKKFG612VvwSSU/u8DarGdLnrKxJ5ito7Pd+n3ZB1YVy sfxDvnYN =SxBW -----END PGP PUBLIC KEY BLOCK-----

1 0

VM Disk extend not reflected in VM oS
by simon＠justconnect.ie 12 Oct '22

12 Oct '22

Hi All, I extended a VM disk via oVirt Manager (4.4.8) without error, but when I checked the VM (fdisk & lsblk) the size has not changed. Any help as always would be appreciated. Kind Regards Simon...

5 11

Geo-replication configuration problem
by dan_agache＠yahoo.com 12 Oct '22

12 Oct '22

Hello, I have two GlusterFS clusters with Centos 9 Stream managed by oVirt 4.5 (standalone Manager with local databases) and when I want to configure geo-replication I receive this error message: Oct 10 15:15:15 myhostname vdsm[222665]: ERROR TypeError raised by dispatched function Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 194, in _dynamicMethod result = fn(*methodArgs) File "/usr/lib/python3.9/site-packages/vdsm/gluster/apiwrapper.py", line 300, in geoRepKeysUpdate return self._gluster.geoRepKeysUpdate(userName, geoRepPubKeys) File "/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 95, in wrapper rv = func(*args, **kwargs) File "/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 720, in geoRepKeysUpdate self.svdsmProxy.glusterUpdateGeoRepKeys(userName, geoRepPubKeys) File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> getattr(self._supervdsmProxy._svdsm, self._funcName)(*args, File "<string>", line 2, in glusterUpdateGeoRepKeys File "/usr/lib64/python3.9/multiprocessing/managers.py", line 825, in _callmethod raise convert_to_error(kind, result) TypeError: a bytes-like object is required, not 'str' Oct 10 15:15:15 myhostname vdsm[222665]: ERROR Internal server error Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 194, in _dynamicMethod result = fn(*methodArgs) File "/usr/lib/python3.9/site-packages/vdsm/gluster/apiwrapper.py", line 300, in geoRepKeysUpdate return self._gluster.geoRepKeysUpdate(userName, geoRepPubKeys) File "/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 95, in wrapper rv = func(*args, **kwargs) File "/usr/lib/python3.9/site-packages/vdsm/gluster/api.py", line 720, in geoRepKeysUpdate self.svdsmProxy.glusterUpdateGeoRepKeys(userName, geoRepPubKeys) File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.9/site-packages/vdsm/common/supervdsm.py", line 53, in <lambda> getattr(self._supervdsmProxy._svdsm, self._funcName)(*args, File "<string>", line 2, in glusterUpdateGeoRepKeys File "/usr/lib64/python3.9/multiprocessing/managers.py", line 825, in _callmethod raise convert_to_error(kind, result) TypeError: a bytes-like object is required, not 'str' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/yajsonrpc/__init__.py", line 349, in _handle_request res = method(**params) File "/usr/lib/python3.9/site-packages/vdsm/rpc/Bridge.py", line 201, in _dynamicMethod raise InvalidCall(fn, methodArgs, e) vdsm.rpc.Bridge.InvalidCall: Attempt to call function: <bound method GlusterVolume.geoRepKeysUpdate of <vdsm.gluster.apiwrapper.GlusterVolume object at 0x7efd082d3400>> with arguments: ('geoaccount', ['command="/usr/libexec/glusterfs/gsyncd" ssh-rsa ...']) error: a bytes-like object is required, not 'str' Can you tell me what is wrong? Thank you, Dan

1 1

Re: OVS Task Error when Add EL Host
by aleksandar＠dualsoft.net 12 Oct '22

12 Oct '22

Hello, I am facing the same issue on multiple Operating Systems (Rocky Linux 8,9, oVirt Node 4.5.2). Did you maybe find a solution for this problem? All best, Aleksandar

1 0

How to configure HA virtual machine on hosts without IPMI
by samuel.xhu＠horebdata.cn 12 Oct '22

12 Oct '22

Dear Ovirt folks, I am thinking of deploly an experimental Ovirt 3-node Cluster on servers without IPMI. As far i know, Ovirts needs each host to have fence agent working for any HA virtual machine. My question is, are there any other ways in Ovirt to support fencing without using IPMI? thanks a lot, Samuel Do Right Thing (做正确的事) / Pursue Excellence (追求卓越) / Help Others Succeed (成就他人)

4 6

Re: OVS Task Error when Add EL Host
by Rui Crespo 11 Oct '22

11 Oct '22

Hi, I'm having the exact same problem doing a fresh install of RHEL and setting up (command line: hosted-engine --deploy --4) the ovirt-engine. I assume it must have been some kind of update to the base OS - (in my case RHEL 8.6 (Ootpa), because i have done previous installations with this exact OS and centos-release-ovirt45 repos without having an issues. The failed task is: TASK [ovirt.ovirt.hosted_engine_setup : Wait for the host to be up] and, on the hosted-engine log: /var/log/ovirt-hosted-engine-setup/engine-logs-2022-10-11T18:43:29Z/log/ovirt-engine/host-deploy I see: "stdout" : "fatal: [xxxxx]: FAILED! => {\"msg\": \"The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller\\n\\nThe error appears to be in '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may\\nbe elsewhere in the file depending on the exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n - name: Install ovs\\n ^ here\\n\"}",

1 0

SSL error on oVirt 4.2.4
by Don Dupuis 11 Oct '22

11 Oct '22

Hello I have oVirt cluster with 25 hypervisors that has been running fine for a couple of years and today all of a sudden engine was getting ssl errors talking to the hypervisors. Error in engine.log is: 2022-10-10 16:20:23,562-05 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-47) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Received fatal alert: unknown_ca Certificates don't seem expired and I ran the command: openssl x509 -noout -in /etc/pki/ovirt-engine/ca.pem -fingerprint openssl x509 -noout -in /etc/pki/vdsm/certs/cacert.pem -fingerprint # openssl x509 -noout -in /etc/pki/vdsm/libvirt-spice/ca-cert.pem -fingerprint # openssl x509 -noout -in /etc/pki/vdsm/libvirt-vnc/ca-cert.pem -fingerprint # openssl x509 -noout -in /etc/pki/CA/cacert.pem -fingerprint Those commands show that the fingerprints are the same. openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/engine.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/apache.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/websocket-proxy.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/jboss.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/imageio-proxy.cer # openssl verify -CAfile /etc/pki/ovirt-engine/ca.pem /etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer These verification commands come back as OK. I am having trouble finding my problem. Does anyone have any suggestions? I am not finding any hits on google and unknown_ca. Also the vdsm log on hypervisors has this: 2022-10-10 15:54:42,843-0500 ERROR (Reactor thread) [ProtocolDetector.SSLHandshakeDispatcher] ssl handshake: SSLError, address: ::ffff:192.168.50.26 (sslutils:263) Thanks Don

1 1

Re: Snapshot not working
by Facundo Badaracco 11 Oct '22

11 Oct '22

Sorry for my ignorance. But, im trying since a few days to upload the requested logs, but it keeping me saying they are too big. How con i upload them? El vie, 7 de oct. de 2022 19:09, Facundo Badaracco <varekoarfa(a)gmail.com> escribió: > sorry for the delay. > > there are the engine.log, vdsm.log from spm and the host where the vm is > running. > > thx in advance! > > ---------- Forwarded message --------- > De: Facundo Badaracco <varekoarfa(a)gmail.com> > Date: jue, 6 oct 2022 a la(s) 20:22 > Subject: Re: [ovirt-users] Re: Snapshot not working > To: Benny Zlotnik <bzlotnik(a)redhat.com> > > > sorry for the delay. > > there are the engine.log, vdsm.log from spm and the host where the vm is > running. > > thx in advance! > > El jue, 6 oct 2022 a la(s) 20:03, Facundo Badaracco (varekoarfa(a)gmail.com) > escribió: > >> sorry for the delay. >> >> there are the engine.log, vdsm.log from spm and the host where the vm is >> running. >> >> thx in advance! >> >> >> El jue, 6 oct 2022 a la(s) 05:30, Benny Zlotnik (bzlotnik(a)redhat.com) >> escribió: >> >>> Can you provide relevant ovirt-engine and vdsm logs (SPM and host where >>> VM runs) >>> >>> On Tue, Oct 4, 2022 at 7:49 PM Facundo Badaracco <varekoarfa(a)gmail.com> >>> wrote: >>> > >>> > Someone? Any hint? >>> > >>> > El jue, 29 de sep. de 2022 10:58, Facundo Badaracco < >>> varekoarfa(a)gmail.com> escribió: >>> >> >>> >> hi everyone, >>> >> >>> >> I have a glusterFS replica x3 node. >>> >> >>> >> I can't create snapshot. when I create it, if I select to save the >>> memory, then in the disks section only appears the snapshot of the memory >>> and in locked state. If instead, I remove the option to make snapshot of >>> the memory, it does not make the snapshot saying "failed". >>> >> >>> >> Any idea? >>> > >>> > _______________________________________________ >>> > 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/5LQQKPQC6LRNE… >>> >>>

1 0

Convert raw images to qcow format
by Jonas 11 Oct '22

11 Oct '22

Hi there I want to create incremental backups of a few imported VMs, but the VM disks are in the raw disk format which does not support incremental backup. Is there a way to convert existing disks from raw to qcow in oVirt? Since qemu-img can do this,I assume there must be a way.. Thank you Jonas

2 1

Pre-Installing OpenVSwitch For oVirt Self-Hoster Install - Issues?
by Matthew J Black 11 Oct '22

11 Oct '22

Hi All, Is anyone aware of any issues (ie "gotchas") with pre-installing OpenVSwitch in preparation for an oVirt Self-Hosted install? We're trying to work around an error we're getting with `hosted-engine --deploy` which spits out: `error: Failed to start network default\nerror: internal error: Network is already in use by interface bond1.a`. What we're thinking is if we pre-create the OVS Network (ie ovirtmgmt) then `hosted-engine --deploy` won't baulk and fail to install. We've been grinding away at this and other issues for several weeks now and we're getting pretty desperate at this stage, to the point that we're starting to seriously consider giving up on oVirt completely - which would be a shame because it seems to be made for the job we want to do, but if we can't get it installed, let along working, then what's the point? (Plus I hate the thought of all the wasted time and effort - but that may just be the "suck cost fallacy" at work). Anyway, if anyone has any insights we'd appreciate them. Cheers Dulux-Oz

1 1

Re: OVS Task Error when Add EL Host
by Łukasz Pelczyk 09 Oct '22

09 Oct '22

I just hit the same error. Initially I got it on the beginning of installation (both netaddr and jmespath were not found). Seems that python3.9 is used so initially I solved it via pip3.9 install. Alternatively you can get the rpm packages from epel. The same issues is on ovirt VM side. As a workaround I started deployment with pause (hosted-engine --deploy --ansible-extra-vars=he_pause_host=true). With that you can ssh to the instance, and manually run pip install which got me: 'Successfully installed jmespath-1.0.1 netaddr-0.8.0'. This is just a workaround and proper fix should be reflected in engine VM image, or on the repos side.

1 0

Re: OVS Task Error when Add EL Host
by Martin Perina 07 Oct '22

07 Oct '22

Hi, please try to downgrade ansible-core-2.13 to 2.12, oVirt doesn't support 2.13 on EL8 yet. Regards, Martin On Thu, Oct 6, 2022 at 3:23 PM Nur Imam Febrianto <nur_imam(a)outlook.com> wrote: > Hi, > > > > Getting strange error when adding EL Host (Using CentOS Stream 8) : > > The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is > defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter > requires python's netaddr be installed on the ansible controller\\n\\nThe > error appears to be in > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > line 3, column 5, but may\\nbe elsewhere in the file depending on the exact > syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n - > name: Install ovs\\n ^ here\\n\"}", > > "msg" : "The conditional check 'cluster_switch == \"ovs\" or > (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: > The ipaddr filter requires python's netaddr be installed on the ansible > controller\n\nThe error appears to be in > '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': > line 3, column 5, but may\nbe elsewhere in the file depending on the exact > syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: > Install ovs\n ^ here\n" > > > > Already checking the python-netaddr and its already installed on the > system (both python3-netaddr and python38-netaddr). > > Using oVirt 4.5. Anybody getting this same issue ? > > > > Thanks before. > > Regards, > > Nur Imam Febrianto > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows > > > _______________________________________________ > 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/EGVQEKGAA6O2X… > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

2 1

Question: How does ovirt storage domain differ from VMFS?
by jstk888＠gmail.com 07 Oct '22

07 Oct '22

Hello, I was asked the other day what file system oVirt uses to store virtual machine images and how it differed from VMware VMFS. I had to admit that I didn't quite understand this aspect of oVirt. I've had a look around but haven't found an answer. I was wondering if someone could explain at a high level, how the underlying oVirt VM storage domain differs from VMFS? What file system is used? Does it use a file system at all? Thank you.

2 1

OVS Task Error when Add EL Host
by Nur Imam Febrianto 06 Oct '22

06 Oct '22

Hi, Getting strange error when adding EL Host (Using CentOS Stream 8) : The conditional check 'cluster_switch == \\\"ovs\\\" or (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller\\n\\nThe error appears to be in '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may\\nbe elsewhere in the file depending on the exact syntax problem.\\n\\nThe offending line appears to be:\\n\\n- block:\\n - name: Install ovs\\n ^ here\\n\"}", "msg" : "The conditional check 'cluster_switch == \"ovs\" or (ovn_central is defined and ovn_central | ipaddr)' failed. The error was: The ipaddr filter requires python's netaddr be installed on the ansible controller\n\nThe error appears to be in '/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-provider-ovn-driver/tasks/configure.yml': line 3, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: Install ovs\n ^ here\n" Already checking the python-netaddr and its already installed on the system (both python3-netaddr and python38-netaddr). Using oVirt 4.5. Anybody getting this same issue ? Thanks before. Regards, Nur Imam Febrianto Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

1 0

Snapshot not working
by Facundo Badaracco 06 Oct '22

06 Oct '22

hi everyone, I have a glusterFS replica x3 node. I can't create snapshot. when I create it, if I select to save the memory, then in the disks section only appears the snapshot of the memory and in locked state. If instead, I remove the option to make snapshot of the memory, it does not make the snapshot saying "failed". Any idea?

2 2

Issues with snapshot and template
by David Johnson 06 Oct '22

06 Oct '22

Good morning all, Thank you in advance. My current environment is ovirt 4.5.2.4-1.el8, running on centos 7.9. I'm looking for advice on resolving two issues that have just come to light: *Issue #1*: When I attempt to create a template from the oVirt GUI, I click the "Make Template" button, enter the name for the new template, then click the "OK" button. The OK button highlights, but nothing happens. *There are no entries showing activity in the engine.log.* *Issue #2:* When I delete a snapshot, after the snapshot is deleted, I receive this error message from the GUI: [image: image.png] *ui.log entry:* 2022-10-05 11:01:42,014-05 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-243) [] Permutation name: 872EE01DC49AC3F81586694F1584D19D 2022-10-05 11:01:42,014-05 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-243) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read properties of null (reading 'wV') at org.ovirt.engine.ui.uicommonweb.models.vms.VmSnapshotListModel.$updateActionAvailability(VmSnapshotListModel.java:834) at org.ovirt.engine.ui.uicommonweb.models.vms.VmSnapshotListModel.onSelectedItemChanged(VmSnapshotListModel.java:262) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel.$setItems(SearchableListModel.java:714) at org.ovirt.engine.ui.uicommonweb.models.vms.VmSnapshotListModel.$updateItems(VmSnapshotListModel.java:225) at org.ovirt.engine.ui.uicommonweb.models.vms.VmSnapshotListModel.setItems(VmSnapshotListModel.java:205) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel$SetItemsAsyncQuery$1.$onSuccess(SearchableListModel.java:878) at org.ovirt.engine.ui.uicommonweb.models.SearchableListModel$SetItemsAsyncQuery$1.onSuccess(SearchableListModel.java:878) at org.ovirt.engine.ui.frontend.Frontend$1.$onSuccess(Frontend.java:239) at org.ovirt.engine.ui.frontend.Frontend$1.onSuccess(Frontend.java:239) at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.$onSuccess(OperationProcessor.java:133) at org.ovirt.engine.ui.frontend.communication.OperationProcessor$1.onSuccess(OperationProcessor.java:133) at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.$onSuccess(GWTRPCCommunicationProvider.java:270) at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onSuccess(GWTRPCCommunicationProvider.java:270) at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198) at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233) at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409) at Unknown.eval(webadmin-0.js) at com.google.gwt.core.client.impl.Impl.apply(Impl.java:306) at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:345) at Unknown.eval(webadmin-0.js) *David Johnson*

2 1

Re: oVirt 4.5 self-hosted network not working
by Paul-Erik Törrönen 05 Oct '22

05 Oct '22

On 2022-08-25 22:56, Facundo Badaracco wrote: > Have u checked the IP of the engine VM? Yes. It is what I configured during the setup, and which I use when I ssh from the host to the engine VM. Sorry, I should have mentioned this in my previous message. Poltsi

2 4

oVirt 4.5.2 /var growing rapidly due to ovirt_engine_history db
by sohail_akhter3＠hotmail.com 05 Oct '22

05 Oct '22

Hi, We have recently upgrade our oVirt environment to 4.5.2 version. Environment is based on hosted-engine. Since we have upgrade we noticed rapid incrase in /var partition in engine VM. It is increasing very rapidly. If we vacuum ovirt_engine_history db, /var size reduces but next day size will increase again upto 5-10%. We did db vacuuming couple of time but not sure we it is increasing so rapidly. Here is the partial output of vacuuming that was done on 26-08-22. Table "host_interface_hourly_history" had more entries to be removed. Rest of the table had not much entries. Previously table "host_interface_samples_history" had entries to be removed. Any Idea what can be the reason for that? # dwh-vacuum -f -v SELECT pg_catalog.set_config('search_path', '', false); vacuumdb: vacuuming database "ovirt_engine_history" RESET search_path; SELECT c.relname, ns.nspname FROM pg_catalog.pg_class c JOIN pg_catalog.pg_namespace ns ON c.relnamespace OPERATOR(pg_catalog.=) ns.oid LEFT JOIN pg_catalog.pg_class t ON c.reltoastrelid OPERATOR(pg_catalog.=) t.oid WHERE c.relkind OPERATOR(pg_catalog.=) ANY (array['r', 'm']) ORDER BY c.relpages DESC; SELECT pg_catalog.set_config('search_path', '', false); VACUUM (FULL, VERBOSE) public.host_interface_samples_history; INFO: vacuuming "public.host_interface_samples_history" INFO: "host_interface_samples_history": found 3135 removable, 84609901 nonremovable row versions in 1564960 pages DETAIL: 0 dead row versions cannot be removed yet. CPU: user: 41.88 s, system: 14.93 s, elapsed: 422.83 s. VACUUM (FULL, VERBOSE) public.host_interface_hourly_history; INFO: vacuuming "public.host_interface_hourly_history" INFO: "host_interface_hourly_history": found 252422 removable, 39904650 nonremovable row versions in 473269 pages Please let me know if any further information is required. Regards Sohail

2 4

Re: Export to Data Domain (with TPM)
by Milan Zamazal 05 Oct '22

05 Oct '22

Christopher Law <chris(a)chrislaw.me> writes: > Anyone explain why I can't export a Virtual Machine with a TPM? Is > this something to do with the TPM data? I'm exporting the VM to some > cold storage. What's the deal here how can I export it and keep the > TPM data or do I have to disable TPM on it first? > > oVirt Error message when trying to export a VM to a Data Domain that has a TPM. > Export VM Failed > Cannot add VM. TPM device is required by the guest OS Hi, it is a Windows VM, right? It is a bug, I filed https://github.com/oVirt/ovirt-engine/issues/702 . The export should work. A workaround could be temporarily switching the VM operating system in the VM properties to Red Hat Enterprise Linux 9 before exporting but I'm not sure it won't change some other VM properties, be careful if you attempt it. Regards, Milan

2 1