6:42 p.m.
oVirt 4.4.7 Fourth Release Candidate is now available for testing
The oVirt Project is pleased to announce the availability of oVirt 4.4.7
Fourth Release Candidate for testing, as of June 18th, 2021.
This update is the seventh in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1
Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.
Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> -
Host enter emergency mode after upgrading to latest build
If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.7 you may get your
host entering emergency mode.
In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:
1.
Remove the current lvm filter while still on 4.4.1, or in emergency mode
(if rebooted).
2.
Reboot.
3.
Upgrade to 4.4.7 (redeploy in case of already being on 4.4.7).
4.
Run vdsm-tool config-lvm-filter to confirm there is a new filter in
place.
5.
Only if not using oVirt Node:
- run "dracut --force --add multipath” to rebuild initramfs with the
correct filter configuration
6.
Reboot.
Documentation
-
If you want to try oVirt as quickly as possible, follow the instructions
on the Download <https://ovirt.org/download/> page.
-
For complete installation, administration, and usage instructions, see
the oVirt Documentation <https://ovirt.org/documentation/>;.
-
For upgrading from a previous version, see the oVirt Upgrade Guide
<https://ovirt.org/documentation/upgrade_guide/>;.
-
For a general overview of oVirt, see About oVirt
<https://ovirt.org/community/about.html>;.
Important notes before you try it
Please note this is a pre-release build.
The oVirt Project makes no guarantees as to its suitability or usefulness.
This pre-release must not be used in production.
Installation instructions
For installation instructions and additional information please refer to:
https://ovirt.org/documentation/
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 8.4 or similar
* CentOS Stream 8
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 8.4 or similar
* CentOS Stream 8
* oVirt Node 4.4 based on CentOS Stream 8 (available for x86_64 only)
See the release notes [1] for installation instructions and a list of new
features and bugs fixed.
Notes:
- oVirt Appliance is already available based on CentOS Stream 8
- oVirt Node NG is already available based on CentOS Stream 8
Additional Resources:
* Read more about the oVirt 4.4.7 release highlights:
http://www.ovirt.org/release/4.4.7/
* Get more oVirt project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] http://www.ovirt.org/release/4.4.7/
[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/
--
Lev Veyde
Senior Software Engineer, RHCE | RHCVA | MCITP
Red Hat Israel
<https://www.redhat.com>
lev(a)redhat.com | lveyde(a)redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
1:12 a.m.
New subject: [ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing
Installation fails on a CentOS Linux 8.4 host using yum update.
I had previously installed ceph and python3-os-brick from the
centos-oepnstrack-train and ceph-nautilus repos, but I removed the
packages and the repos and ran dnf distro-sync, and used yum list
installed just to be sure everything was in a clean state with no extra
packages installed from nonstandard repos.
Here's the output from yum update:
Last metadata expiration check: 2:31:18 ago on Tue 22 Jun 2021 11:26:39 PM PDT.
Error:
Problem 1: cannot install the best update candidate for package
vdsm-4.40.60.7-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 2: package vdsm-hook-fcoe-4.40.70.4-1.el8.noarch requires vdsm =
4.40.70.4-1.el8, but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-hook-fcoe-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 3: package vdsm-hook-ethtool-options-4.40.70.4-1.el8.noarch requires vdsm =
4.40.70.4-1.el8, but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 4: cannot install the best update candidate for package
vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
- package vdsm-hook-vmfex-dev-4.40.70.4-1.el8.noarch requires vdsm = 4.40.70.4-1.el8,
but none of the providers can be installed
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 5: package ovirt-provider-ovn-driver-1.2.33-1.el8.noarch requires vdsm, 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.1-1.el8.x86_64 requires vdsm-http = 4.40.70.1-1.el8, but none of
the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-http = 4.40.70.2-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.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.70.4-1.el8.noarch and
vdsm-http-4.40.60.7-1.el8.noarch
- cannot install both vdsm-http-4.40.70.4-1.el8.noarch and
vdsm-http-4.40.70.1-1.el8.noarch
- cannot install both vdsm-http-4.40.70.4-1.el8.noarch and
vdsm-http-4.40.70.2-1.el8.noarch
- cannot install both vdsm-http-4.40.17-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.18-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.19-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.20-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.21-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.22-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.26.3-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.30-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.31-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.32-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.33-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.34-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.35-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.35.1-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.36-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.37-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.38-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.39-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.40-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.50.8-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.50.9-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.60.6-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.60.7-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both ovirt-imageio-common-2.0.6-0.el8.x86_64 and
ovirt-imageio-common-2.1.1-1.el8.x86_64
- cannot install the best update candidate for package
vdsm-http-4.40.60.7-1.el8.noarch
- cannot install the best update candidate for package
ovirt-provider-ovn-driver-1.2.33-1.el8.noarch
- cannot install the best update candidate for package
ovirt-imageio-common-2.1.1-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 6: package ovirt-hosted-engine-ha-2.4.7-1.el8.noarch requires vdsm >= 4.40.0,
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.1-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.2-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.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.70.4-1.el8.noarch and
vdsm-jsonrpc-4.40.60.7-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.70.4-1.el8.noarch and
vdsm-jsonrpc-4.40.70.1-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.70.4-1.el8.noarch and
vdsm-jsonrpc-4.40.70.2-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.17-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.18-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.19-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.20-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.21-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.22-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.26.3-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.30-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.31-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.32-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.33-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.34-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.35-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.35.1-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.36-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.37-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.38-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.39-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.40-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.50.8-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.50.9-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.60.6-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.60.7-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both ovirt-imageio-daemon-2.0.6-0.el8.x86_64 and
ovirt-imageio-daemon-2.1.1-1.el8.x86_64
- cannot install the best update candidate for package
vdsm-jsonrpc-4.40.60.7-1.el8.noarch
- cannot install the best update candidate for package
ovirt-imageio-daemon-2.1.1-1.el8.x86_64
- cannot install the best update candidate for package
ovirt-hosted-engine-ha-2.4.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 7: package ovirt-host-dependencies-4.4.7-1.el8.x86_64 requires vdsm >=
4.40.60, 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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-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
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.60.7-1.el8.noarch
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.70.1-1.el8.noarch
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.70.2-1.el8.noarch
- cannot install both vdsm-python-4.40.60.6-1.el8.noarch and
vdsm-python-4.40.70.4-1.el8.noarch
- cannot install both vdsm-python-4.40.60.7-1.el8.noarch and
vdsm-python-4.40.70.4-1.el8.noarch
- cannot install the best update candidate for package
vdsm-python-4.40.60.7-1.el8.noarch
- cannot install the best update candidate for package
ovirt-host-dependencies-4.4.6-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 8: package ovirt-host-dependencies-4.4.7-1.el8.x86_64 requires vdsm >=
4.40.60, 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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-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-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.1-1.el8.noarch requires vdsm-api = 4.40.70.1-1.el8, but
none of the providers can be installed
- package vdsm-python-4.40.70.2-1.el8.noarch requires vdsm-api = 4.40.70.2-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
- cannot install both vdsm-api-4.40.70.4-1.el8.noarch and
vdsm-api-4.40.60.7-1.el8.noarch
- cannot install both vdsm-api-4.40.70.4-1.el8.noarch and
vdsm-api-4.40.70.1-1.el8.noarch
- cannot install both vdsm-api-4.40.70.4-1.el8.noarch and
vdsm-api-4.40.70.2-1.el8.noarch
- cannot install both vdsm-api-4.40.60.6-1.el8.noarch and
vdsm-api-4.40.70.4-1.el8.noarch
- cannot install both vdsm-api-4.40.60.7-1.el8.noarch and
vdsm-api-4.40.70.4-1.el8.noarch
- package ovirt-host-4.4.7-1.el8.x86_64 requires ovirt-host-dependencies = 4.4.7-1.el8,
but none of the providers can be installed
- cannot install the best update candidate for package vdsm-api-4.40.60.7-1.el8.noarch
- cannot install the best update candidate for package ovirt-host-4.4.6-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 9: problem with installed package vdsm-4.40.60.7-1.el8.x86_64
- 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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-1.el8, but none
of the providers can be installed
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.60.7-1.el8.noarch
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.70.1-1.el8.noarch
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.70.2-1.el8.noarch
- cannot install both vdsm-python-4.40.60.7-1.el8.noarch and
vdsm-python-4.40.70.4-1.el8.noarch
- package vdsm-client-4.40.70.4-1.el8.noarch requires vdsm-python = 4.40.70.4-1.el8,
but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-client-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 10: problem with installed package vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
- package vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch requires vdsm = 4.40.60.7-1.el8,
but none of the providers can be installed
- package vdsm-hook-vmfex-dev-4.40.70.1-1.el8.noarch requires vdsm = 4.40.70.1-1.el8,
but none of the providers can be installed
- package vdsm-hook-vmfex-dev-4.40.70.2-1.el8.noarch requires vdsm = 4.40.70.2-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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-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.1-1.el8.noarch requires vdsm-common = 4.40.70.1-1.el8,
but none of the providers can be installed
- package vdsm-python-4.40.70.2-1.el8.noarch requires vdsm-common = 4.40.70.2-1.el8,
but none of the providers can be installed
- cannot install both vdsm-common-4.40.70.4-1.el8.noarch and
vdsm-common-4.40.60.7-1.el8.noarch
- cannot install both vdsm-common-4.40.70.4-1.el8.noarch and
vdsm-common-4.40.70.1-1.el8.noarch
- cannot install both vdsm-common-4.40.70.4-1.el8.noarch and
vdsm-common-4.40.70.2-1.el8.noarch
- cannot install both vdsm-common-4.40.60.7-1.el8.noarch and
vdsm-common-4.40.70.4-1.el8.noarch
- package vdsm-hook-vmfex-dev-4.40.70.3-1.el8.noarch requires vdsm = 4.40.70.3-1.el8,
but none of the providers can be installed
- package vdsm-hook-vmfex-dev-4.40.70.4-1.el8.noarch requires vdsm = 4.40.70.4-1.el8,
but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-common-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 11: problem with installed package vdsm-hook-fcoe-4.40.60.7-1.el8.noarch
- package vdsm-hook-fcoe-4.40.60.7-1.el8.noarch requires vdsm = 4.40.60.7-1.el8, but
none of the providers can be installed
- package vdsm-hook-fcoe-4.40.70.1-1.el8.noarch requires vdsm = 4.40.70.1-1.el8, but
none of the providers can be installed
- package vdsm-hook-fcoe-4.40.70.2-1.el8.noarch requires vdsm = 4.40.70.2-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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-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.1-1.el8.noarch requires vdsm-network = 4.40.70.1-1.el8,
but none of the providers can be installed
- package vdsm-python-4.40.70.2-1.el8.noarch requires vdsm-network = 4.40.70.2-1.el8,
but none of the providers can be installed
- cannot install both vdsm-network-4.40.70.4-1.el8.x86_64 and
vdsm-network-4.40.60.7-1.el8.x86_64
- cannot install both vdsm-network-4.40.70.4-1.el8.x86_64 and
vdsm-network-4.40.70.1-1.el8.x86_64
- cannot install both vdsm-network-4.40.70.4-1.el8.x86_64 and
vdsm-network-4.40.70.2-1.el8.x86_64
- cannot install both vdsm-network-4.40.60.7-1.el8.x86_64 and
vdsm-network-4.40.70.4-1.el8.x86_64
- package vdsm-hook-fcoe-4.40.70.3-1.el8.noarch requires vdsm = 4.40.70.3-1.el8, but
none of the providers can be installed
- package vdsm-hook-fcoe-4.40.70.4-1.el8.noarch requires vdsm = 4.40.70.4-1.el8, but
none of the providers can be installed
- cannot install the best update candidate for package
vdsm-network-4.40.60.7-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 12: problem with installed package
vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch
- package vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch requires vdsm =
4.40.60.7-1.el8, but none of the providers can be installed
- package vdsm-hook-ethtool-options-4.40.70.1-1.el8.noarch requires vdsm =
4.40.70.1-1.el8, but none of the providers can be installed
- package vdsm-hook-ethtool-options-4.40.70.2-1.el8.noarch requires vdsm =
4.40.70.2-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.1-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.2-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.1-1.el8.noarch requires vdsm-yajsonrpc =
4.40.70.1-1.el8, but none of the providers can be installed
- package vdsm-jsonrpc-4.40.70.2-1.el8.noarch requires vdsm-yajsonrpc =
4.40.70.2-1.el8, but none of the providers can be installed
- cannot install both vdsm-yajsonrpc-4.40.70.4-1.el8.noarch and
vdsm-yajsonrpc-4.40.60.7-1.el8.noarch
- cannot install both vdsm-yajsonrpc-4.40.70.4-1.el8.noarch and
vdsm-yajsonrpc-4.40.70.1-1.el8.noarch
- cannot install both vdsm-yajsonrpc-4.40.70.4-1.el8.noarch and
vdsm-yajsonrpc-4.40.70.2-1.el8.noarch
- cannot install both vdsm-yajsonrpc-4.40.60.7-1.el8.noarch and
vdsm-yajsonrpc-4.40.70.4-1.el8.noarch
- package vdsm-hook-ethtool-options-4.40.70.3-1.el8.noarch requires vdsm =
4.40.70.3-1.el8, but none of the providers can be installed
- package vdsm-hook-ethtool-options-4.40.70.4-1.el8.noarch requires vdsm =
4.40.70.4-1.el8, but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-yajsonrpc-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-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)
6:14 p.m.
New subject: [ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing
On Wed, Jun 23, 2021 at 12:22 PM Sketch <ovirt(a)rednsx.org> wrote:
Installation fails on a CentOS Linux 8.4 host using yum update.
I had previously installed ceph and python3-os-brick from the
centos-oepnstrack-train and ceph-nautilus repos, but I removed the
packages and the repos and ran dnf distro-sync, and used yum list
installed just to be sure everything was in a clean state with no extra
packages installed from nonstandard repos.
Here's the output from yum update:
Last metadata expiration check: 2:31:18 ago on Tue 22 Jun 2021 11:26:39 PM PDT.
Error:
Problem 1: cannot install the best update candidate for package
vdsm-4.40.60.7-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
This version was not released yet for Centos. You need to wait until
this package
is released on Centos if you want to upgrade ovirt to 4.4.7.
If you want to use the latest oVirt version as soon as it is released,
you need to use
Centos Stream.
Nir
Problem 2: package vdsm-hook-fcoe-4.40.70.4-1.el8.noarch requires
vdsm = 4.40.70.4-1.el8, but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-hook-fcoe-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 3: package vdsm-hook-ethtool-options-4.40.70.4-1.el8.noarch requires vdsm =
4.40.70.4-1.el8, but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 4: cannot install the best update candidate for package
vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
- package vdsm-hook-vmfex-dev-4.40.70.4-1.el8.noarch requires vdsm = 4.40.70.4-1.el8,
but none of the providers can be installed
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 5: package ovirt-provider-ovn-driver-1.2.33-1.el8.noarch requires vdsm, 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.1-1.el8.x86_64 requires vdsm-http = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-http = 4.40.70.2-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.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.70.4-1.el8.noarch and
vdsm-http-4.40.60.7-1.el8.noarch
- cannot install both vdsm-http-4.40.70.4-1.el8.noarch and
vdsm-http-4.40.70.1-1.el8.noarch
- cannot install both vdsm-http-4.40.70.4-1.el8.noarch and
vdsm-http-4.40.70.2-1.el8.noarch
- cannot install both vdsm-http-4.40.17-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.18-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.19-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.20-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.21-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.22-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.26.3-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.30-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.31-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.32-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.33-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.34-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.35-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.35.1-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.36-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.37-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.38-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.39-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.40-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.50.8-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.50.9-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.60.6-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both vdsm-http-4.40.60.7-1.el8.noarch and
vdsm-http-4.40.70.4-1.el8.noarch
- cannot install both ovirt-imageio-common-2.0.6-0.el8.x86_64 and
ovirt-imageio-common-2.1.1-1.el8.x86_64
- cannot install the best update candidate for package
vdsm-http-4.40.60.7-1.el8.noarch
- cannot install the best update candidate for package
ovirt-provider-ovn-driver-1.2.33-1.el8.noarch
- cannot install the best update candidate for package
ovirt-imageio-common-2.1.1-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 6: package ovirt-hosted-engine-ha-2.4.7-1.el8.noarch requires vdsm >=
4.40.0, 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.1-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.1-1.el8, but
none of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.2-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.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.70.4-1.el8.noarch and
vdsm-jsonrpc-4.40.60.7-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.70.4-1.el8.noarch and
vdsm-jsonrpc-4.40.70.1-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.70.4-1.el8.noarch and
vdsm-jsonrpc-4.40.70.2-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.17-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.18-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.19-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.20-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.21-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.22-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.26.3-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.30-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.31-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.32-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.33-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.34-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.35-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.35.1-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.36-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.37-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.38-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.39-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.40-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.50.8-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.50.9-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.60.6-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both vdsm-jsonrpc-4.40.60.7-1.el8.noarch and
vdsm-jsonrpc-4.40.70.4-1.el8.noarch
- cannot install both ovirt-imageio-daemon-2.0.6-0.el8.x86_64 and
ovirt-imageio-daemon-2.1.1-1.el8.x86_64
- cannot install the best update candidate for package
vdsm-jsonrpc-4.40.60.7-1.el8.noarch
- cannot install the best update candidate for package
ovirt-imageio-daemon-2.1.1-1.el8.x86_64
- cannot install the best update candidate for package
ovirt-hosted-engine-ha-2.4.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 7: package ovirt-host-dependencies-4.4.7-1.el8.x86_64 requires vdsm >=
4.40.60, 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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-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
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.60.7-1.el8.noarch
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.70.1-1.el8.noarch
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.70.2-1.el8.noarch
- cannot install both vdsm-python-4.40.60.6-1.el8.noarch and
vdsm-python-4.40.70.4-1.el8.noarch
- cannot install both vdsm-python-4.40.60.7-1.el8.noarch and
vdsm-python-4.40.70.4-1.el8.noarch
- cannot install the best update candidate for package
vdsm-python-4.40.60.7-1.el8.noarch
- cannot install the best update candidate for package
ovirt-host-dependencies-4.4.6-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 8: package ovirt-host-dependencies-4.4.7-1.el8.x86_64 requires vdsm >=
4.40.60, 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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-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-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.1-1.el8.noarch requires vdsm-api = 4.40.70.1-1.el8, but
none of the providers can be installed
- package vdsm-python-4.40.70.2-1.el8.noarch requires vdsm-api = 4.40.70.2-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
- cannot install both vdsm-api-4.40.70.4-1.el8.noarch and
vdsm-api-4.40.60.7-1.el8.noarch
- cannot install both vdsm-api-4.40.70.4-1.el8.noarch and
vdsm-api-4.40.70.1-1.el8.noarch
- cannot install both vdsm-api-4.40.70.4-1.el8.noarch and
vdsm-api-4.40.70.2-1.el8.noarch
- cannot install both vdsm-api-4.40.60.6-1.el8.noarch and
vdsm-api-4.40.70.4-1.el8.noarch
- cannot install both vdsm-api-4.40.60.7-1.el8.noarch and
vdsm-api-4.40.70.4-1.el8.noarch
- package ovirt-host-4.4.7-1.el8.x86_64 requires ovirt-host-dependencies =
4.4.7-1.el8, but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-api-4.40.60.7-1.el8.noarch
- cannot install the best update candidate for package ovirt-host-4.4.6-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 9: problem with installed package vdsm-4.40.60.7-1.el8.x86_64
- 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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-1.el8, but none
of the providers can be installed
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.60.7-1.el8.noarch
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.70.1-1.el8.noarch
- cannot install both vdsm-python-4.40.70.4-1.el8.noarch and
vdsm-python-4.40.70.2-1.el8.noarch
- cannot install both vdsm-python-4.40.60.7-1.el8.noarch and
vdsm-python-4.40.70.4-1.el8.noarch
- package vdsm-client-4.40.70.4-1.el8.noarch requires vdsm-python = 4.40.70.4-1.el8,
but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-client-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 10: problem with installed package vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch
- package vdsm-hook-vmfex-dev-4.40.60.7-1.el8.noarch requires vdsm = 4.40.60.7-1.el8,
but none of the providers can be installed
- package vdsm-hook-vmfex-dev-4.40.70.1-1.el8.noarch requires vdsm = 4.40.70.1-1.el8,
but none of the providers can be installed
- package vdsm-hook-vmfex-dev-4.40.70.2-1.el8.noarch requires vdsm = 4.40.70.2-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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-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.1-1.el8.noarch requires vdsm-common = 4.40.70.1-1.el8,
but none of the providers can be installed
- package vdsm-python-4.40.70.2-1.el8.noarch requires vdsm-common = 4.40.70.2-1.el8,
but none of the providers can be installed
- cannot install both vdsm-common-4.40.70.4-1.el8.noarch and
vdsm-common-4.40.60.7-1.el8.noarch
- cannot install both vdsm-common-4.40.70.4-1.el8.noarch and
vdsm-common-4.40.70.1-1.el8.noarch
- cannot install both vdsm-common-4.40.70.4-1.el8.noarch and
vdsm-common-4.40.70.2-1.el8.noarch
- cannot install both vdsm-common-4.40.60.7-1.el8.noarch and
vdsm-common-4.40.70.4-1.el8.noarch
- package vdsm-hook-vmfex-dev-4.40.70.3-1.el8.noarch requires vdsm = 4.40.70.3-1.el8,
but none of the providers can be installed
- package vdsm-hook-vmfex-dev-4.40.70.4-1.el8.noarch requires vdsm = 4.40.70.4-1.el8,
but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-common-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 11: problem with installed package vdsm-hook-fcoe-4.40.60.7-1.el8.noarch
- package vdsm-hook-fcoe-4.40.60.7-1.el8.noarch requires vdsm = 4.40.60.7-1.el8, but
none of the providers can be installed
- package vdsm-hook-fcoe-4.40.70.1-1.el8.noarch requires vdsm = 4.40.70.1-1.el8, but
none of the providers can be installed
- package vdsm-hook-fcoe-4.40.70.2-1.el8.noarch requires vdsm = 4.40.70.2-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.1-1.el8.x86_64 requires vdsm-python = 4.40.70.1-1.el8, but none
of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-python = 4.40.70.2-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.1-1.el8.noarch requires vdsm-network = 4.40.70.1-1.el8,
but none of the providers can be installed
- package vdsm-python-4.40.70.2-1.el8.noarch requires vdsm-network = 4.40.70.2-1.el8,
but none of the providers can be installed
- cannot install both vdsm-network-4.40.70.4-1.el8.x86_64 and
vdsm-network-4.40.60.7-1.el8.x86_64
- cannot install both vdsm-network-4.40.70.4-1.el8.x86_64 and
vdsm-network-4.40.70.1-1.el8.x86_64
- cannot install both vdsm-network-4.40.70.4-1.el8.x86_64 and
vdsm-network-4.40.70.2-1.el8.x86_64
- cannot install both vdsm-network-4.40.60.7-1.el8.x86_64 and
vdsm-network-4.40.70.4-1.el8.x86_64
- package vdsm-hook-fcoe-4.40.70.3-1.el8.noarch requires vdsm = 4.40.70.3-1.el8, but
none of the providers can be installed
- package vdsm-hook-fcoe-4.40.70.4-1.el8.noarch requires vdsm = 4.40.70.4-1.el8, but
none of the providers can be installed
- cannot install the best update candidate for package
vdsm-network-4.40.60.7-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
Problem 12: problem with installed package
vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch
- package vdsm-hook-ethtool-options-4.40.60.7-1.el8.noarch requires vdsm =
4.40.60.7-1.el8, but none of the providers can be installed
- package vdsm-hook-ethtool-options-4.40.70.1-1.el8.noarch requires vdsm =
4.40.70.1-1.el8, but none of the providers can be installed
- package vdsm-hook-ethtool-options-4.40.70.2-1.el8.noarch requires vdsm =
4.40.70.2-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.1-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.1-1.el8, but
none of the providers can be installed
- package vdsm-4.40.70.2-1.el8.x86_64 requires vdsm-jsonrpc = 4.40.70.2-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.1-1.el8.noarch requires vdsm-yajsonrpc =
4.40.70.1-1.el8, but none of the providers can be installed
- package vdsm-jsonrpc-4.40.70.2-1.el8.noarch requires vdsm-yajsonrpc =
4.40.70.2-1.el8, but none of the providers can be installed
- cannot install both vdsm-yajsonrpc-4.40.70.4-1.el8.noarch and
vdsm-yajsonrpc-4.40.60.7-1.el8.noarch
- cannot install both vdsm-yajsonrpc-4.40.70.4-1.el8.noarch and
vdsm-yajsonrpc-4.40.70.1-1.el8.noarch
- cannot install both vdsm-yajsonrpc-4.40.70.4-1.el8.noarch and
vdsm-yajsonrpc-4.40.70.2-1.el8.noarch
- cannot install both vdsm-yajsonrpc-4.40.60.7-1.el8.noarch and
vdsm-yajsonrpc-4.40.70.4-1.el8.noarch
- package vdsm-hook-ethtool-options-4.40.70.3-1.el8.noarch requires vdsm =
4.40.70.3-1.el8, but none of the providers can be installed
- package vdsm-hook-ethtool-options-4.40.70.4-1.el8.noarch requires vdsm =
4.40.70.4-1.el8, but none of the providers can be installed
- cannot install the best update candidate for package
vdsm-yajsonrpc-4.40.60.7-1.el8.noarch
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.3-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.3-1.el8.x86_64
- nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
- nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-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)
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/CRJPHWJYSAI...
5:18 p.m.
New subject: [ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing
On Wed, 23 Jun 2021, Nir Soffer wrote:
On Wed, Jun 23, 2021 at 12:22 PM Sketch <ovirt(a)rednsx.org>
wrote:
>
> Installation fails on a CentOS Linux 8.4 host using yum update.
>
> Problem 1: cannot install the best update candidate for package
vdsm-4.40.60.7-1.el8.x86_64
> - nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
> - nothing provides sanlock >= 3.8.3-3 needed by vdsm-4.40.70.4-1.el8.x86_64
This version was not released yet for Centos. You need to wait until
this package
is released on Centos if you want to upgrade ovirt to 4.4.7.
If you want to use the latest oVirt version as soon as it is released,
you need to use
Centos Stream.
I suspected that might have been the case, but figured I'd mention it
since we're on RC4 now and the release notes say it's available for RHEL
8.4 a well as Stream. I checked the RHEL package browser and it doesn't
have sanlock >= 3.8.3-3 yet either. Is the oVirt 4.4.7 GA release waiting
on this update to be pushed?
11 a.m.
New subject: [ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing
On Thu, Jun 24, 2021 at 4:19 AM Sketch <ovirt(a)rednsx.org> wrote:
On Wed, 23 Jun 2021, Nir Soffer wrote:
> On Wed, Jun 23, 2021 at 12:22 PM Sketch <ovirt(a)rednsx.org> wrote:
>>
>> Installation fails on a CentOS Linux 8.4 host using yum update.
>>
>> Problem 1: cannot install the best update candidate for package
vdsm-4.40.60.7-1.el8.x86_64
>> - nothing provides python3-sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
>> - nothing provides sanlock >= 3.8.3-3 needed by
vdsm-4.40.70.4-1.el8.x86_64
> This version was not released yet for Centos. You need to wait until
> this package
> is released on Centos if you want to upgrade ovirt to 4.4.7.
>
> If you want to use the latest oVirt version as soon as it is released,
> you need to use
> Centos Stream.
I suspected that might have been the case, but figured I'd mention it
since we're on RC4 now and the release notes say it's available for RHEL
8.4 a well as Stream. I checked the RHEL package browser and it doesn't
have sanlock >= 3.8.3-3 yet either. Is the oVirt 4.4.7 GA release waiting
on this update to be pushed?
This package should be available in RHEL when oVirt 4.4.7 is released.
The relevant oVirt bug is:
https://bugzilla.redhat.com/1961752
The sanlock bugs:
https://bugzilla.redhat.com/1965481
https://bugzilla.redhat.com/1965483
Nir
1247
days inactive
1253
days old
4 comments
3 participants
participants (3)
-
Lev Veyde -
Nir Soffer -
Sketch