How to debug "Non Operational" host
by Gervais de Montbrun
Hi Folks,
I did a minor upgrade on the first host in my cluster and now it is reporting "Non Operational"
This is what yum showed as updatable. However, I did the update through the ovirt-engine web interface.
ovirt-node-ng-image-update.noarch 4.4.9-1.el8 ovirt-4.4
Obsoleting Packages
ovirt-node-ng-image-update.noarch 4.4.9-1.el8 ovirt-4.4
ovirt-node-ng-image-update.noarch 4.4.8.3-1.el8 @System
ovirt-node-ng-image-update.noarch 4.4.9-1.el8 ovirt-4.4
ovirt-node-ng-image-update-placeholder.noarch 4.4.8.3-1.el8 @System
How do I start to debug this issue?
Also, it looks like the vmstore brick is not mounting on that host. I only see the engine mounted.
Broken server:
root(a)ovirt1.dgi log]# mount | grep storage
ovirt1-storage.dgi:/engine on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
Working server:
[root(a)ovirt2.dgi ~]# mount | grep storage
ovirt1-storage.dgi:/engine on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
ovirt1-storage.dgi:/vmstore on /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)
I tried putting the server into maintenance mode and running a reinstall on it. No change. I'de really appreciate some help sorting this our.
Cheers,
Gervais
2 years, 5 months
oVirt installation via PXE
by Jean-Louis Dupond
Hi,
We would like to install oVirt Node via some automated way.
I think the best option to do this is via a PXE boot, and there run the
installation.
But I would like to know how you can customize the installation of oVirt
Node. So no manual intervention is needed.
Is it just creating a kickstart file based from the
'interactive-defaults.ks' kickstart in the iso and have the
'ovirt-node-ng-image.squashfs.img' file accessible somewhere?
Are there things that should not be used in the kickstart file? I think
like disk settings as this is already built-in into oVirt Node?
Other idea's are also welcome :)
Thanks
Jean-Louis
2 years, 5 months
host non responsive
by Nathanaël Blanchet
Hello,
Some of my hosts are for some different reason in "non responsive"
state. Fortunately, critical vms continue to run on it.
I didn't manage to recover the up state and the only solution will be at
a predefined date to stop and fence the host.
Waiting for this date, I ssh stopped a targeted vm for maintenance (with
init 0) and now I want to reboot it on a healthy host. This vm is ovirt
high available with a lease on a storage domain.
How can I tell to engine that the vm lease is not anymore on the non
responding host so as to start the vm elsewhere?
--
Nathanaël Blanchet
Supervision réseau
SIRE
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5
Tél. 33 (0)4 67 54 84 55
Fax 33 (0)4 67 54 84 14
blanchet(a)abes.fr
2 years, 5 months
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
2 years, 5 months
Update Issue
by Gary Pedretty
After doing the latest updates on one of my CentOS 8 Stream hosts, it will non longer allow VMs to be migrated to it. VMs can be started on the host, but then have no network access. The hosted engine can be started on the host, but again no network access. I have tried removing the host, rebuilding the OS from scratch and re-adding it, with no change. It shows up and you do not get any error messages that I can tell when a migrate fails, it just shows that it failed.
The updated host has the following versions, only KVM and LIBVIRT appear to be different. I tried downgrading KVM and LIBVIRT, but the migration still fails. I have avoided trying up update the other hosts since I cannot migrate any of my VMs to the one host that I already tried to update.
RHEL - 8.6 - 1.el8
OS Description:
CentOS Stream 8
Kernel Version:
4.18.0 - 348.el8.x86_64
KVM Version:
6.1.0 - 4.module_el8.6.0+983+a7505f3f
LIBVIRT Version:
libvirt-7.9.0-1.module_el8.6.0+983+a7505f3f
VDSM Version:
vdsm-4.40.90.4-1.el8
The other two hosts which have not been updated and still work normally have
RHEL - 8.6 - 1.el8
OS Description:
CentOS Stream 8
Kernel Version:
4.18.0 - 348.el8.x86_64
KVM Version:
6.0.0 - 33.el8s
LIBVIRT Version:
libvirt-7.6.0-4.el8s
VDSM Version:
vdsm-4.40.90.4-1.el8
The engine log from an attempted migrations is as follows.
2021-11-17 21:12:46,099-09 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-21) [c0c87da3-a8aa-4f8e-ab9c-1e2fc05babac] Running command: MigrateVmToServerCommand internal: false. Entities affected : ID: fa1a2d6b-99cb-42bd-a343-91f314d5f47b Type: VMAction group MIGRATE_VM with role type USER
2021-11-17 21:12:46,134-09 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-21) [c0c87da3-a8aa-4f8e-ab9c-1e2fc05babac] START, MigrateVDSCommand( MigrateVDSCommandParameters:{hostId='6ee16602-c686-471a-9f65-e5952b813672', vmId='fa1a2d6b-99cb-42bd-a343-91f314d5f47b', srcHost='ravn-kvm-8.ravnalaska.net', dstVdsId='10491335-e2e1-49f2-96c3-79331535542b', dstHost='ravn-kvm-9.ravnalaska.net:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', migrateEncrypted='false', consoleAddress='null', maxBandwidth='1250', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='10.9.24.79'}), log id: 3522dfb9
2021-11-17 21:12:46,134-09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-21) [c0c87da3-a8aa-4f8e-ab9c-1e2fc05babac] START, MigrateBrokerVDSCommand(HostName = ravn-kvm-8.ravnalaska.net, MigrateVDSCommandParameters:{hostId='6ee16602-c686-471a-9f65-e5952b813672', vmId='fa1a2d6b-99cb-42bd-a343-91f314d5f47b', srcHost='ravn-kvm-8.ravnalaska.net', dstVdsId='10491335-e2e1-49f2-96c3-79331535542b', dstHost='ravn-kvm-9.ravnalaska.net:54321', migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', autoConverge='true', migrateCompressed='false', migrateEncrypted='false', consoleAddress='null', maxBandwidth='1250', enableGuestEvents='true', maxIncomingMigrations='2', maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, {limit=-1, action={name=abort, params=[]}}]]', dstQemu='10.9.24.79'}), log id: 23f98865
2021-11-17 21:12:46,141-09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] (default task-21) [c0c87da3-a8aa-4f8e-ab9c-1e2fc05babac] FINISH, MigrateBrokerVDSCommand, return: , log id: 23f98865
2021-11-17 21:12:46,143-09 INFO [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] (default task-21) [c0c87da3-a8aa-4f8e-ab9c-1e2fc05babac] FINISH, MigrateVDSCommand, return: MigratingFrom, log id: 3522dfb9
2021-11-17 21:12:46,149-09 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-21) [c0c87da3-a8aa-4f8e-ab9c-1e2fc05babac] EVENT_ID: VM_MIGRATION_START(62), Migration started (VM: ns8, Source: ravn-kvm-8.ravnalaska.net, Destination: ravn-kvm-9.ravnalaska.net, User: admin@internal-authz).
2021-11-17 21:12:49,052-09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-36) [] Fetched 2 VMs from VDS '10491335-e2e1-49f2-96c3-79331535542b'
2021-11-17 21:12:49,053-09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-36) [] VM 'fa1a2d6b-99cb-42bd-a343-91f314d5f47b' is migrating to VDS '10491335-e2e1-49f2-96c3-79331535542b'(ravn-kvm-9.ravnalaska.net) ignoring it in the refresh until migration is done
2021-11-17 21:12:54,314-09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [] VM 'fa1a2d6b-99cb-42bd-a343-91f314d5f47b' was reported as Down on VDS '10491335-e2e1-49f2-96c3-79331535542b'(ravn-kvm-9.ravnalaska.net)
2021-11-17 21:12:54,314-09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [] VM 'fa1a2d6b-99cb-42bd-a343-91f314d5f47b'(ns8) was unexpectedly detected as 'Down' on VDS '10491335-e2e1-49f2-96c3-79331535542b'(ravn-kvm-9.ravnalaska.net) (expected on '6ee16602-c686-471a-9f65-e5952b813672')
2021-11-17 21:12:54,315-09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-21) [] START, DestroyVDSCommand(HostName = ravn-kvm-9.ravnalaska.net, DestroyVmVDSCommandParameters:{hostId='10491335-e2e1-49f2-96c3-79331535542b', vmId='fa1a2d6b-99cb-42bd-a343-91f314d5f47b', secondsToWait='0', gracefully='false', reason='', ignoreNoVm='true'}), log id: 389ad865
2021-11-17 21:12:54,596-09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (ForkJoinPool-1-worker-21) [] FINISH, DestroyVDSCommand, return: , log id: 389ad865
2021-11-17 21:12:54,596-09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [] VM 'fa1a2d6b-99cb-42bd-a343-91f314d5f47b'(ns8) was unexpectedly detected as 'Down' on VDS '10491335-e2e1-49f2-96c3-79331535542b'(ravn-kvm-9.ravnalaska.net) (expected on '6ee16602-c686-471a-9f65-e5952b813672')
2021-11-17 21:12:54,596-09 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-21) [] Migration of VM 'ns8' to host 'ravn-kvm-9.ravnalaska.net' failed: VM destroyed during the startup.
2021-11-17 21:12:54,642-09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-5) [] VM 'fa1a2d6b-99cb-42bd-a343-91f314d5f47b'(ns8) moved from 'MigratingFrom' --> 'Up'
2021-11-17 21:12:54,642-09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-5) [] Adding VM 'fa1a2d6b-99cb-42bd-a343-91f314d5f47b'(ns8) to re-run list
2021-11-17 21:12:54,644-09 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-5) [] Rerun VM 'fa1a2d6b-99cb-42bd-a343-91f314d5f47b'. Called from VDS 'ravn-kvm-8.ravnalaska.net'
2021-11-17 21:12:54,679-09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-7232) [] START, MigrateStatusVDSCommand(HostName = ravn-kvm-8.ravnalaska.net, MigrateStatusVDSCommandParameters:{hostId='6ee16602-c686-471a-9f65-e5952b813672', vmId='fa1a2d6b-99cb-42bd-a343-91f314d5f47b'}), log id: 7ce5593e
2021-11-17 21:12:54,681-09 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] (EE-ManagedThreadFactory-engine-Thread-7232) [] FINISH, MigrateStatusVDSCommand, return: , log id: 7ce5593e
2021-11-17 21:12:54,695-09 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-7232) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed (VM: ns8, Source: ravn-kvm-8.ravnalaska.net, Destination: ravn-kvm-9.ravnalaska.net).
2021-11-17 21:12:54,697-09 INFO [org.ovirt.engine.core.bll.MigrateVmToServerCommand] (EE-ManagedThreadFactory-engine-Thread-7232) [] Lock freed to object 'EngineLock:{exclusiveLocks='[fa1a2d6b-99cb-42bd-a343-91f314d5f47b=VM]', sharedLocks=''}'
2021-11-17 21:13:04,061-09 INFO [org.ovirt.engine.core.vdsbroker.monitoring.PollVmStatsRefresher] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-94) [] Fetched 1 VMs from VDS '10491335-e2e1-49f2-96c3-79331535542b'
_______________________________
Gary Pedretty
Director of IT
Ravn Alaska
Office: 907-266-8451
Mobile: 907-388-2247
Email: gary.pedretty(a)ravnalaska.com
2 years, 5 months
Add static route to ovirt nodes
by Michael Thomas
I'm running ovirt 4.4.2 on CentOS 8.2. My ovirt nodes have two network
addresses, ovirtmgmt and a second used for normal routed traffic to the
cluster and WAN.
After the ovirt nodes were set up, I found that I needed to add an extra
static route to the cluster interface to allow the hosts to see my ceph
storage nodes (to make the rbd images visible to the VMs):
10.9.0.0/16 via 10.13.0.1
I can add this route using three different methods:
1) ip route add 10.9.0.0/16 via 10.13.0.1
2) nmcli conn modify enp65s0f0 ipv4.routes "10.9.0.0/16 10.13.0.1"
nmcli conn down enp65s0f0
nmcli conn up enp65s0f0
3) vi /etc/sysconfig/network-scripts/route-enp65s0f0
ifdown enp65s0f0
ifup enp65s0f0
However, when I reboot the host, the static route goes away. Methods 2
and 3 have always given me a persistent static route on other EL8 hosts,
but not on my ovirt nodes.
What is the correct way to add a persistent static route on an ovirt host?
--Mike
2 years, 5 months
CentOS 8 streams: Hosted engine deploy failed.
by Gilboa Davara
Hello all,
I'm trying to redeploy one of the HE/Gluster clusters after a botched
upgrade to Stream + simultaneous 2 x UPS failure that killed the previous
setup.
Post crash, the 3 nodes were cleaned up
(manually + ovirt-hosted-engine-cleanup) and upgraded to Streams + reboot.
I've made 3 attempts to deploy the HE, all failed with the same error.
As far as I can see, everything works up until the final deployment, there
the host fails to access the HE static address.
Note: All machines have a static IP, resolved via local hosts file.
Please advise (log attached).
- Gilboa
2 years, 5 months
oVirt 4.4.3 - some hosts in unassigned state - Get Host Capabilities failed: PKIX path building failed
by Roberto Nunin
Hi all
We have an (old) installation with two DC in two different locations.
Hosts where hosted engine is running are regularly reported UP (DC 1)
Host into the other DC (connected by WAN lines) are reported as Unassigned
(DC 2)
Connection between DC is working.
In events we can find lot of errors like:
VDSM itmilu0xx-mng.example.com command Get Host Capabilities failed: PKIX
path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
We are NOT using a thirdy party SSL certificate.
In engine.log these are recurring errors:
2021-11-16 10:28:49,370+01 ERROR
[org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) []
Unable to process messages PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
2021-11-16 10:28:49,372+01 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-100)
[] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException:
VDSNetworkException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target
Thanks in advance for any suggestion
Roberto Nunin
2 years, 5 months
Import from Vcenter failed with qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
by roanne.philip@voxtelecom.co.za
Hi I have ovirt HE Ver 4.4.7 with hosts on 4.3.10
I am trying to migrate vm's from vmware to ovirt but it fails.
weirdly small vm imports successful and the larger ones fails
have anyone experienced this issue
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
[ 2140.296725] sd 2:0:0:0: [sda] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 2140.298168] sd 2:0:0:0: [sda] Sense Key : Aborted Command [current]
[ 2140.299204] sd 2:0:0:0: [sda] Add. Sense: I/O process terminated
[ 2140.300183] sd 2:0:0:0: [sda] CDB: Read(10) 28 00 0a cc 9a 78 00 00 08 00
[ 2140.301291] blk_update_request: I/O error, dev sda, sector 181181048
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
[ 2140.411642] sd 2:0:0:0: [sda] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 2140.413110] sd 2:0:0:0: [sda] Sense Key : Aborted Command [current]
[ 2140.414207] sd 2:0:0:0: [sda] Add. Sense: I/O process terminated
[ 2140.415198] sd 2:0:0:0: [sda] CDB: Read(10) 28 00 0a cc 9a 78 00 00 08 00
[ 2140.416326] blk_update_request: I/O error, dev sda, sector 181181048
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
[ 2140.547845] sd 2:0:0:0: [sda] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 2140.549289] sd 2:0:0:0: [sda] Sense Key : Aborted Command [current]
[ 2140.550324] sd 2:0:0:0: [sda] Add. Sense: I/O process terminated
[ 2140.551296] sd 2:0:0:0: [sda] CDB: Read(10) 28 00 0a cc 9a 60 00 00 08 00
[ 2140.552397] blk_update_request: I/O error, dev sda, sector 181181024
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
[ 2140.671078] sd 2:0:0:0: [sda] FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
[ 2140.672537] sd 2:0:0:0: [sda] Sense Key : Aborted Command [current]
[ 2140.673581] sd 2:0:0:0: [sda] Add. Sense: I/O process terminated
[ 2140.674575] sd 2:0:0:0: [sda] CDB: Read(10) 28 00 0a cc 9a 60 00 00 08 00
[ 2140.675681] blk_update_request: I/O error, dev sda, sector 181181024
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
qemu-kvm: curl: The requested URL returned error: 401 Unauthorized
2 years, 5 months