- 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