October 2021 - Users - Ovirt List Archives

by Sketch

This is on oVirt 4.4.8, engine on CS8, hosts on C8, cluster and DC are both set to 4.6. With a newly configured cinderlib/ceph RBD setup. I can create new VM images, and copy existing VM images, but I can't copy existing template images to RBD. When I do, I try, I get this error in cinderlib.log (see below), which sounds like the disk already exists there, but it definitely does not. This leaves me unable to create new VMs on RBD, only migrate existing VM disks. 2021-09-01 04:31:05,881 - cinder.volume.driver - INFO - Driver hasn't implemented _init_vendor_properties() 2021-09-01 04:31:05,882 - cinderlib-client - INFO - Creating volume '0e8b9aca-1eb1-4837-ac9e-cb3d8f4c1676', with size '500' GB [5c5d0a6b] 2021-09-01 04:31:05,943 - cinderlib-client - ERROR - Failure occurred when trying to run command 'create_volume': Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' [5c5d0a6b] 2021-09-01 04:31:05,944 - cinder - CRITICAL - Unhandled error Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 455, in create self._raise_with_resource() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 222, in _raise_with_resource six.reraise(*exc_info) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 448, in create model_update = self.backend.driver.create_volume(self._ovo) File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/rbd.py", line 986, in create_volume features=client.features) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 190, in doit result = proxy_call(self._autowrap, f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 148, in proxy_call rv = execute(f, *args, **kwargs) File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 129, in execute six.reraise(c, e, tb) File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise raise value File "/usr/lib/python3.6/site-packages/eventlet/tpool.py", line 83, in tworker rv = meth(*args, **kwargs) File "rbd.pyx", line 629, in rbd.RBD.create rbd.ImageExists: [errno 17] RBD image already exists (error creating image) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 399, in _entity_descriptor return getattr(entity, key) AttributeError: type object 'Volume' has no attribute 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 170, in main args.command(args) File "./cinderlib-client.py", line 208, in create_volume backend.create_volume(int(args.size), id=args.volume_id) File "/usr/lib/python3.6/site-packages/cinderlib/cinderlib.py", line 175, in create_volume vol.create() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 457, in create self.save() File "/usr/lib/python3.6/site-packages/cinderlib/objects.py", line 628, in save self.persistence.set_volume(self) File "/usr/lib/python3.6/site-packages/cinderlib/persistence/dbms.py", line 254, in set_volume self.db.volume_update(objects.CONTEXT, volume.id, changed) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 236, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 184, in wrapper return f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/cinder/db/sqlalchemy/api.py", line 2570, in volume_update result = query.filter_by(id=volume_id).update(values) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/query.py", line 3818, in update update_op.exec_() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1670, in exec_ self._do_pre_synchronize() File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1743, in _do_pre_synchronize self._additional_evaluators(evaluator_compiler) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1912, in _additional_evaluators values = self._resolved_values_keys_as_propnames File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1831, in _resolved_values_keys_as_propnames for k, v in self._resolved_values: File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/persistence.py", line 1818, in _resolved_values desc = _entity_descriptor(self.mapper, k) File "/usr/lib64/python3.6/site-packages/sqlalchemy/orm/base.py", line 402, in _entity_descriptor "Entity '%s' has no property '%s'" % (description, key) sqlalchemy.exc.InvalidRequestError: Entity '<class 'cinder.db.sqlalchemy.models.Volume'>' has no property 'glance_metadata' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "./cinderlib-client.py", line 390, in <module> sys.exit(main(sys.argv[1:])) File "./cinderlib-client.py", line 176, in main sys.stderr.write(traceback.format_exc(e)) File "/usr/lib64/python3.6/traceback.py", line 167, in format_exc return "".join(format_exception(*sys.exc_info(), limit=limit, chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 121, in format_exception type(value), value, tb, limit=limit).format(chain=chain)) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 498, in __init__ _seen=_seen) File "/usr/lib64/python3.6/traceback.py", line 509, in __init__ capture_locals=capture_locals) File "/usr/lib64/python3.6/traceback.py", line 338, in extract if limit >= 0: TypeError: '>=' not supported between instances of 'InvalidRequestError' and 'int'

2 years, 10 months

3
4
0 / 0

Import an exported VM using Ansible

by paolo＠airaldi.it

Hello everybody! I'm trying to automate a copy of a VM from one Datacenter to another using an Ansible.playbook. I'm able to: - Create a snapshot of the source VM - create a clone from the snapshot - remove the snapshot - attach an Export Domain - export the clone to the Export Domain - remove the clone - detach the Export domain from the source Datacenter and attach to the destination. Unfortunately I cannot find a module to: - import the VM from the Export Domain - delete the VM image from the Export Domain. Any hint on how to do that? Thanks in advance. Cheers. Paolo PS: if someone is interested I can share the playbook.

2 years, 10 months

4
3
0 / 0

did 4.3.9 reset bug https://bugzilla.redhat.com/show_bug.cgi?id=1590266

by kelley bryan

I am experiencing the error message in the ovirt-hosted-engine-setup-ansible-create_target_vm log {2020-05-06 14:15:30,024-0500 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u"Fail if Engine IP is different from engine's he_fqdn resolved IP", 'ansible_result': u'type: <type \'dict\'>\nstr: {\'msg\': u"Engine VM IP address is while the engine\'s he_fqdn ovirt1-engine.kelleykars.org resolves to 192.168.122.2. If you are using DHCP, check your DHCP reservation configuration", \'changed\': False, \'_ansible_no_log\': False}', 'task_duration': 1, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'}}:Q! The bug 1590266 says it should report the engine VM IP address xxx.xxx.xxx.xxx while the Engines he_fqdn is xxxxxxxxx I need to see what it thins is wrong as both dig fqdn engine name and dig -x ip return the correct information. Now this bug looks like it may play but I don't see the failed rediness check in the this log https://access.redhat.com/solutions/4462431 or is it because the vm fails or dies or ???

2 years, 10 months

3
7
0 / 0

Lots of storage.MailBox.SpmMailMonitor

by Fabrice Bacchella

My vdsm log files are huge: -rw-r--r-- 1 vdsm kvm 1.8G Nov 22 11:32 vdsm.log And this is juste half an hour of logs: $ head -1 vdsm.log 2018-11-22 11:01:12,132+0100 ERROR (mailbox-spm) [storage.MailBox.SpmMailMonitor] mailbox 2 checksum failed, not clearing mailbox, clearing new mail (data='...lots of data', expected='\xa4\x06\x08\x00') (mailbox:612) I just upgraded vdsm: $ rpm -qi vdsm Name : vdsm Version : 4.20.43

2 years, 11 months

3
5
0 / 0

upgrade dependency issues

by John Florian

I recently upgrade my engine to 4.4.9 following the usual engine-setup procedure. Once that was done, I tried to do a dnf upgrade to get everything else and found: Error: Problem: cannot install the best update candidate for package ovirt-engine-metrics-1.4.3-1.el8.noarch - nothing provides rhel-system-roles >= 1.7.2-1 needed by ovirt-engine-metrics-1.4.4-1.el8.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) I was also trying to update my hosts thru the GUI and that was failing also. I couldn't find the right log with good details as to why, so I just tried to dnf upgrade from the shell to see what got reported and found: Error: Problem 1: cannot install the best update candidate for package ovirt-host-dependencies-4.4.8-1.el8.x86_64 - nothing provides rsyslog-openssl needed by ovirt-host-dependencies-4.4.9-2.el8.x86_64 Problem 2: cannot install the best update candidate for package ovirt-hosted-engine-setup-2.5.3-1.el8.noarch - nothing provides ovirt-host >= 4.5.0 needed by ovirt-hosted-engine-setup-2.5.4-1.el8.noarch - nothing provides vdsm-python >= 4.50 needed by ovirt-hosted-engine-setup-2.5.4-1.el8.noarch Problem 3: cannot install the best update candidate for package vdsm-4.40.80.5-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 4: package ovirt-host-4.4.9-2.el8.x86_64 requires ovirt-host-dependencies = 4.4.9-2.el8, but none of the providers can be installed - cannot install the best update candidate for package ovirt-host-4.4.8-1.el8.x86_64 - nothing provides rsyslog-openssl needed by ovirt-host-dependencies-4.4.9-2.el8.x86_64 Problem 5: package vdsm-hook-fcoe-4.40.90.3-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-http = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-http = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-http = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-http = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-http = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-http = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-http = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-http = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-http = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-http = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-http = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-http = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-http = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-http = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-http = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-http = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-http = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-http = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-http = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-http = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-http = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-http = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-http = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-http = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-http = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-http = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires ovirt-imageio-common = 2.0.6, but none of the providers can be installed - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.80.5-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.17-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.18-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.19-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.20-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.21-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.22-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.26.3-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.30-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.31-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.32-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.33-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.34-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.35-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.35.1-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.36-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.37-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.38-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.39-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.40-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.50.8-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.50.9-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.60.6-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.60.7-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.70.6-1.el8.noarch - cannot install both vdsm-http-4.40.90.3-1.el8.noarch and vdsm-http-4.40.80.6-1.el8.noarch - cannot install both ovirt-imageio-common-2.3.0-1.el8.x86_64 and ovirt-imageio-common-2.0.6-0.el8.x86_64 - cannot install the best update candidate for package vdsm-http-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package vdsm-hook-fcoe-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package ovirt-imageio-common-2.2.0-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 6: package vdsm-hook-ethtool-options-4.40.90.3-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires ovirt-imageio-daemon = 2.0.6, but none of the providers can be installed - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.80.5-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.17-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.18-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.19-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.20-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.21-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.22-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.26.3-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.30-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.31-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.32-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.33-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.34-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.35-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.35.1-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.36-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.37-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.38-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.39-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.40-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.50.8-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.50.9-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.60.6-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.60.7-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.70.6-1.el8.noarch - cannot install both vdsm-jsonrpc-4.40.90.3-1.el8.noarch and vdsm-jsonrpc-4.40.80.6-1.el8.noarch - cannot install both ovirt-imageio-daemon-2.3.0-1.el8.x86_64 and ovirt-imageio-daemon-2.0.6-0.el8.x86_64 - cannot install the best update candidate for package vdsm-jsonrpc-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package vdsm-hook-ethtool-options-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package ovirt-imageio-daemon-2.2.0-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 7: package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires vdsm-python = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-python = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-python = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-python = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-python = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-python = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-python = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-python = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-python = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-python = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-python = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-python = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-python = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-python = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-python = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-python = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-python = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-python = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-python = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-python = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-python = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-python = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-python = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-python = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-python = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.80.5-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.16-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.17-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.18-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.19-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.20-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.21-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.22-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.26.3-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.30-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.31-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.32-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.33-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.34-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.35-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.35.1-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.36-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.37-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.38-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.39-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.40-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.50.8-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.50.9-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.60.6-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.60.7-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.70.6-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.80.6-1.el8.noarch - cannot install the best update candidate for package vdsm-python-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 8: package ovirt-hosted-engine-ha-2.4.9-1.el8.noarch requires vdsm >= 4.40.0, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-python = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-python = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-python = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-python = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-python = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-python = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-python = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-python = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-python = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-python = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-python = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-python = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-python = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-python = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-python = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-python = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-python = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-python = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-python = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-python = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-python = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-python = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-python = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-python = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires ovirt-imageio-common = 2.0.6, but none of the providers can be installed - package vdsm-python-4.40.80.5-1.el8.noarch requires vdsm-api = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-python-4.40.17-1.el8.noarch requires vdsm-api = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-python-4.40.18-1.el8.noarch requires vdsm-api = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-python-4.40.19-1.el8.noarch requires vdsm-api = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-python-4.40.20-1.el8.noarch requires vdsm-api = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-python-4.40.21-1.el8.noarch requires vdsm-api = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-python-4.40.22-1.el8.noarch requires vdsm-api = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-python-4.40.26.3-1.el8.noarch requires vdsm-api = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-python-4.40.30-1.el8.noarch requires vdsm-api = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-python-4.40.31-1.el8.noarch requires vdsm-api = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-python-4.40.32-1.el8.noarch requires vdsm-api = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-python-4.40.33-1.el8.noarch requires vdsm-api = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-python-4.40.34-1.el8.noarch requires vdsm-api = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35-1.el8.noarch requires vdsm-api = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35.1-1.el8.noarch requires vdsm-api = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-python-4.40.36-1.el8.noarch requires vdsm-api = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-python-4.40.37-1.el8.noarch requires vdsm-api = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-python-4.40.38-1.el8.noarch requires vdsm-api = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-python-4.40.39-1.el8.noarch requires vdsm-api = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-python-4.40.40-1.el8.noarch requires vdsm-api = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.8-1.el8.noarch requires vdsm-api = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.9-1.el8.noarch requires vdsm-api = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.6-1.el8.noarch requires vdsm-api = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.7-1.el8.noarch requires vdsm-api = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-python-4.40.70.6-1.el8.noarch requires vdsm-api = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.6-1.el8.noarch requires vdsm-api = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both ovirt-imageio-common-2.3.0-1.el8.x86_64 and ovirt-imageio-common-2.0.6-0.el8.x86_64 - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.80.5-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.17-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.18-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.19-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.20-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.21-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.22-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.26.3-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.30-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.31-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.32-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.33-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.34-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.35-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.35.1-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.36-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.37-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.38-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.39-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.40-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.50.8-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.50.9-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.60.6-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.60.7-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.70.6-1.el8.noarch - cannot install both vdsm-api-4.40.90.3-1.el8.noarch and vdsm-api-4.40.80.6-1.el8.noarch - package ovirt-imageio-client-2.3.0-1.el8.x86_64 requires ovirt-imageio-common = 2.3.0-1.el8, but none of the providers can be installed - cannot install the best update candidate for package vdsm-api-4.40.80.5-1.el8.noarch - cannot install the best update candidate for package ovirt-imageio-client-2.2.0-1.el8.x86_64 - cannot install the best update candidate for package ovirt-hosted-engine-ha-2.4.8-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 9: problem with installed package vdsm-4.40.80.5-1.el8.x86_64 - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.80.5-1.el8.noarch - cannot install both vdsm-python-4.40.90.3-1.el8.noarch and vdsm-python-4.40.80.6-1.el8.noarch - package vdsm-client-4.40.90.3-1.el8.noarch requires vdsm-python = 4.40.90.3-1.el8, but none of the providers can be installed - cannot install the best update candidate for package vdsm-client-4.40.80.5-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 10: problem with installed package vdsm-hook-fcoe-4.40.80.5-1.el8.noarch - package vdsm-hook-fcoe-4.40.80.5-1.el8.noarch requires vdsm = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-hook-fcoe-4.40.90.3-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-hook-fcoe-4.40.80.6-1.el8.noarch requires vdsm = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires vdsm-python = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-python = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-python = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-python = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-python = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-python = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-python = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-python = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-python = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-python = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-python = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-python = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-python = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-python = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-python = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-python = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-python = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-python = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-python = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-python = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-python = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-python = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-python = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-python = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-python = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.5-1.el8.noarch requires vdsm-common = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-python-4.40.16-1.el8.noarch requires vdsm-common = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-python-4.40.17-1.el8.noarch requires vdsm-common = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-python-4.40.18-1.el8.noarch requires vdsm-common = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-python-4.40.19-1.el8.noarch requires vdsm-common = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-python-4.40.20-1.el8.noarch requires vdsm-common = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-python-4.40.21-1.el8.noarch requires vdsm-common = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-python-4.40.22-1.el8.noarch requires vdsm-common = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-python-4.40.26.3-1.el8.noarch requires vdsm-common = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-python-4.40.30-1.el8.noarch requires vdsm-common = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-python-4.40.31-1.el8.noarch requires vdsm-common = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-python-4.40.32-1.el8.noarch requires vdsm-common = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-python-4.40.33-1.el8.noarch requires vdsm-common = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-python-4.40.34-1.el8.noarch requires vdsm-common = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35-1.el8.noarch requires vdsm-common = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35.1-1.el8.noarch requires vdsm-common = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-python-4.40.36-1.el8.noarch requires vdsm-common = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-python-4.40.37-1.el8.noarch requires vdsm-common = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-python-4.40.38-1.el8.noarch requires vdsm-common = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-python-4.40.39-1.el8.noarch requires vdsm-common = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-python-4.40.40-1.el8.noarch requires vdsm-common = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.8-1.el8.noarch requires vdsm-common = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.9-1.el8.noarch requires vdsm-common = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.6-1.el8.noarch requires vdsm-common = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.7-1.el8.noarch requires vdsm-common = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-python-4.40.70.6-1.el8.noarch requires vdsm-common = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.6-1.el8.noarch requires vdsm-common = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.80.5-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.16-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.17-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.18-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.19-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.20-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.21-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.22-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.26.3-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.30-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.31-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.32-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.33-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.34-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.35-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.35.1-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.36-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.37-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.38-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.39-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.40-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.50.8-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.50.9-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.60.6-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.60.7-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.70.6-1.el8.noarch - cannot install both vdsm-common-4.40.90.3-1.el8.noarch and vdsm-common-4.40.80.6-1.el8.noarch - cannot install the best update candidate for package vdsm-common-4.40.80.5-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 11: problem with installed package vdsm-hook-ethtool-options-4.40.80.5-1.el8.noarch - package vdsm-hook-ethtool-options-4.40.80.5-1.el8.noarch requires vdsm = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-hook-ethtool-options-4.40.90.3-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-hook-ethtool-options-4.40.80.6-1.el8.noarch requires vdsm = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-python = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires vdsm-python = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-python = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-python = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-python = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-python = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-python = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-python = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-python = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-python = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-python = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-python = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-python = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-python = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-python = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-python = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-python = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-python = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-python = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-python = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-python = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-python = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-python = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-python = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-python = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-python = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-python = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.5-1.el8.noarch requires vdsm-network = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-python-4.40.16-1.el8.noarch requires vdsm-network = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-python-4.40.17-1.el8.noarch requires vdsm-network = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-python-4.40.18-1.el8.noarch requires vdsm-network = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-python-4.40.19-1.el8.noarch requires vdsm-network = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-python-4.40.20-1.el8.noarch requires vdsm-network = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-python-4.40.21-1.el8.noarch requires vdsm-network = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-python-4.40.22-1.el8.noarch requires vdsm-network = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-python-4.40.26.3-1.el8.noarch requires vdsm-network = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-python-4.40.30-1.el8.noarch requires vdsm-network = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-python-4.40.31-1.el8.noarch requires vdsm-network = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-python-4.40.32-1.el8.noarch requires vdsm-network = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-python-4.40.33-1.el8.noarch requires vdsm-network = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-python-4.40.34-1.el8.noarch requires vdsm-network = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35-1.el8.noarch requires vdsm-network = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-python-4.40.35.1-1.el8.noarch requires vdsm-network = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-python-4.40.36-1.el8.noarch requires vdsm-network = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-python-4.40.37-1.el8.noarch requires vdsm-network = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-python-4.40.38-1.el8.noarch requires vdsm-network = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-python-4.40.39-1.el8.noarch requires vdsm-network = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-python-4.40.40-1.el8.noarch requires vdsm-network = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.8-1.el8.noarch requires vdsm-network = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-python-4.40.50.9-1.el8.noarch requires vdsm-network = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.6-1.el8.noarch requires vdsm-network = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.60.7-1.el8.noarch requires vdsm-network = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-python-4.40.70.6-1.el8.noarch requires vdsm-network = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-python-4.40.80.6-1.el8.noarch requires vdsm-network = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.80.5-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.16-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.17-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.18-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.19-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.20-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.21-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.22-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.26.3-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.30-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.31-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.32-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.33-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.34-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.35-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.35.1-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.36-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.37-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.38-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.39-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.40-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.50.8-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.50.9-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.60.6-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.60.7-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.70.6-1.el8.x86_64 - cannot install both vdsm-network-4.40.90.3-1.el8.x86_64 and vdsm-network-4.40.80.6-1.el8.x86_64 - cannot install the best update candidate for package vdsm-network-4.40.80.5-1.el8.x86_64 - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 Problem 12: problem with installed package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch - package ovirt-provider-ovn-driver-1.2.34-1.el8.noarch requires vdsm, but none of the providers can be installed - package vdsm-4.40.80.5-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-4.40.16-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-4.40.17-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-4.40.18-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-4.40.19-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-4.40.20-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-4.40.21-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-4.40.22-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-4.40.26.3-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-4.40.30-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-4.40.31-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-4.40.32-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-4.40.33-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-4.40.34-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-4.40.35-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-4.40.35.1-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-4.40.36-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-4.40.37-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-4.40.38-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-4.40.39-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-4.40.40-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-4.40.50.8-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-4.40.50.9-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-4.40.60.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-4.40.60.7-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-4.40.70.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-4.40.80.6-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.80.6-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.80.5-1.el8.noarch requires vdsm-yajsonrpc = 4.40.80.5-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.16-1.el8.noarch requires vdsm-yajsonrpc = 4.40.16-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.17-1.el8.noarch requires vdsm-yajsonrpc = 4.40.17-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.18-1.el8.noarch requires vdsm-yajsonrpc = 4.40.18-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.19-1.el8.noarch requires vdsm-yajsonrpc = 4.40.19-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.20-1.el8.noarch requires vdsm-yajsonrpc = 4.40.20-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.21-1.el8.noarch requires vdsm-yajsonrpc = 4.40.21-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.22-1.el8.noarch requires vdsm-yajsonrpc = 4.40.22-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.26.3-1.el8.noarch requires vdsm-yajsonrpc = 4.40.26.3-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.30-1.el8.noarch requires vdsm-yajsonrpc = 4.40.30-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.31-1.el8.noarch requires vdsm-yajsonrpc = 4.40.31-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.32-1.el8.noarch requires vdsm-yajsonrpc = 4.40.32-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.33-1.el8.noarch requires vdsm-yajsonrpc = 4.40.33-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.34-1.el8.noarch requires vdsm-yajsonrpc = 4.40.34-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.35-1.el8.noarch requires vdsm-yajsonrpc = 4.40.35-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.35.1-1.el8.noarch requires vdsm-yajsonrpc = 4.40.35.1-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.36-1.el8.noarch requires vdsm-yajsonrpc = 4.40.36-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.37-1.el8.noarch requires vdsm-yajsonrpc = 4.40.37-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.38-1.el8.noarch requires vdsm-yajsonrpc = 4.40.38-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.39-1.el8.noarch requires vdsm-yajsonrpc = 4.40.39-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.40-1.el8.noarch requires vdsm-yajsonrpc = 4.40.40-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.50.8-1.el8.noarch requires vdsm-yajsonrpc = 4.40.50.8-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.50.9-1.el8.noarch requires vdsm-yajsonrpc = 4.40.50.9-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.60.6-1.el8.noarch requires vdsm-yajsonrpc = 4.40.60.6-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.60.7-1.el8.noarch requires vdsm-yajsonrpc = 4.40.60.7-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.70.6-1.el8.noarch requires vdsm-yajsonrpc = 4.40.70.6-1.el8, but none of the providers can be installed - package vdsm-jsonrpc-4.40.80.6-1.el8.noarch requires vdsm-yajsonrpc = 4.40.80.6-1.el8, but none of the providers can be installed - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.80.5-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.16-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.17-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.18-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.19-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.20-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.21-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.22-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.26.3-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.30-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.31-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.32-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.33-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.34-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.35-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.35.1-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.36-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.37-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.38-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.39-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.40-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.50.8-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.50.9-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.60.6-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.60.7-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.70.6-1.el8.noarch - cannot install both vdsm-yajsonrpc-4.40.90.3-1.el8.noarch and vdsm-yajsonrpc-4.40.80.6-1.el8.noarch - cannot install the best update candidate for package vdsm-yajsonrpc-4.40.80.5-1.el8.noarch - nothing provides libvirt-daemon-kvm >= 7.6.0-2 needed by vdsm-4.40.90.3-1.el8.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) -- John Florian

3 years

9
18
1 / 0

How to renew vmconsole-proxy* certificates

by capelle＠labri.fr

Hi, Since a few weeks, we are not able to connect to the vmconsole proxy: $ ssh -t -p 2222 ovirt-vmconsole@ovirt ovirt-vmconsole@ovirt: Permission denied (publickey). Last successful login record: Mar 29 11:31:32 First login failure record: Mar 31 17:28:51 We tracked the issue to the following log in /var/log/ovirt-engine/engine.log: ERROR [org.ovirt.engine.core.services.VMConsoleProxyServlet] (default task-11) [] Error validating ticket: : sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Indeed, certificate /etc/pki/ovirt-engine/certs/vmconsole-proxy-helper.cer and others did expire: -- # grep 'Not After' /etc/pki/ovirt-engine/certs/vmconsole-proxy-* /etc/pki/ovirt-engine/certs/vmconsole-proxy-helper.cer: Not After : Mar 31 13:18:44 2021 GMT /etc/pki/ovirt-engine/certs/vmconsole-proxy-host.cer: Not After : Mar 31 13:18:44 2021 GMT /etc/pki/ovirt-engine/certs/vmconsole-proxy-user.cer: Not After : Mar 31 13:18:44 2021 GMT -- But we did not manage to found how to renew them. Any advice ? -- Benoît

3 years

3
2
0 / 0

CentOS 8 Stream: hosted-engine deploy with CPU type is not supported

by matyi.szabolcs＠internetx.com

Hi all, On CentOS 8 Stream I get the following error during "hosted-engine --deploy": [ INFO ] The host has been set in non_operational status, deployment errors: code 156: Host HOST moved to Non-Operational state as host CPU type is not supported in this cluster compatibility version or is not supported at all, code 519 CPU: [root@ovirt-test ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 24 On-line CPU(s) list: 0-23 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel BIOS Vendor ID: Intel CPU family: 6 Model: 63 Model name: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz I set up cluster compatibility but it did not solve the problem. On a normal CentOS 8.4 system, the error is not present. Does anyone have an idea? Or have older drivers been removed from the Streram version? Thanks

3 years

4
3
1 / 0

Failed to delete snapshot

by ivohccarvalho＠gmail.com

Hello all. We use vprotect to make snapshot backups of our vm's. This VM, let's call it OVIRTVM, has it's disks created as thin. A full snapshot is created daily on sunday and the daily ones are incremental. After the backup vprotect tries to delete the snapshot and almost always fails with the error: "Failed to delete snapshot 'vProtect 2021-10-25 22:30:17.641654' for VM 'OVIRTVM'." From engine.log can't get much more information: 2021-10-26 22:39:02,510+01 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-511666) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2021-10-26 22:39:02,558+01 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-15) [666e0f97-8b02-4b1e-80d4-2a640dd28d90] Ending command 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2021-10-26 22:39:02,595+01 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-511666) [1a9981] Running command: CreateUserSessionCommand internal: false. 2021-10-26 22:39:02,630+01 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-511612) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2021-10-26 22:39:02,674+01 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-511669) [] User admin@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access 2021-10-26 22:39:02,729+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-15) [666e0f97-8b02-4b1e-80d4-2a640dd28d90] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'vProtect 2021-10-25 22:30:17.641654' for VM 'OVIRTVM'. 2021-10-26 22:39:02,739+01 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-511675) [55891f0c] Running command: CreateUserSessionCommand internal: false. 2021-10-26 22:39:02,755+01 INFO [org.ovirt.engine.core.bll.aaa.CreateUserSessionCommand] (default task-511660) [7895798d] Running command: CreateUserSessionCommand internal: false. What else should I be looking for? Thanks in advance!

3 years, 1 month

3
6
2 / 0

question about engine deployment success rate

by Henning Sprang

Hello, I've just inherited a project where we need to bring a prototype of a small Ovirt system (single node or 3 node hyperconverged, with glusterFS on the same machine, a bunch of different VM's ) running in an industrial machine into serial production. This means, we want to build a new 1 or 3 node Ovirt system each day up until 3 times a day. In my tests so far, the failure rate of the Ovirt engine deployment (via the included scripts as well as the web UI) turns out to be pretty high - it's between 40-60%, meaning until we have a running system, we would have to try the installation and/or final engine deployment about 2-4 times until we are successful. So far I could not identify clear error messages that let me tell how to fix the problem. Before going into details of the errors I would like to ask if people deeper into Ovirt would consider this a somewhat normal success rate, or if this indicates we are doing something generally wrong and we should definitely spend a few more hours or maybe days into finding sources of problems. More info about the system and errors * OVirt 4.3.9 (because the prototype was made and verified with that version - would be interesting to know, too, if it's strongly considered to upgrade for more stable installation/deployment) * The errors that appear are changing between the deployment process seeming not to be able to transfer the "LocalHostedEngine" VM to the glusterFS storage to become a "HostedEngine", and the other seems to be when the engine is already up and running, but never being really connected to the Ovirt system, continuously restarting, and also showing XFS filesystem errors in it's dmesg output. Any hints on our chances on getting this solved or requests for more information about the error are welcome - thanks in advance. Henning

3 years, 1 month

2
5
0 / 0

The Engine VM (/32) and this host (/32) will not be in the same IP subnet.

by notify.sina＠gmail.com

Hi list, 'The Engine VM (10.200.30.5/32) and this host (10.200.30.3/32) will not be in the same IP subnet.' This happens when I select a static IP address configuration for the engine. Ive been struggling with setting up ovirt-hosted-engine on CentOS 8 servers in the Equinix network, using hosted-engine --deploy. Why would the setup not want the engine and the host it's being setup on, not be in the same subnet? Can someone please help me understand what prerequisites I am missing?

3 years, 1 month

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users October 2021