So that explains what happened but we still don't have a solution to
make this go away, correct?
FTR, I did try `dnf reinstall --disablerepo='*'
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm` but things
are no different afterwards.
John Florian
On 2022-03-03 11:37, Klaas Demter wrote:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OANKECW6C4SM6USKJP7DJIAHUN5RALFI/
On 3/3/22 17:20, John Florian wrote:
FWIW, I'm getting what appears to be the same dependency errors on my
oVirt Hosts that were installed new on C8S not all that long ago. I
have to do upgrades manually with `dnf upgrade --no-best` otherwise I
get:
[root@orthosie ~]# dnf upgrade
Last metadata expiration check: 1:24:59 ago on Thu 03 Mar 2022
09:52:40 AM EST.
Error:
Problem: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
requires ansible, but none of the providers can be installed
- package ansible-2.9.27-2.el8.noarch conflicts with ansible-core >
2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.27-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.27-1.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.17-1.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.18-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.20-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.21-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.23-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.24-2.el8.noarch
- cannot install the best update candidate for package
cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
- cannot install the best update candidate for package
ansible-2.9.27-2.el8.noarch
- package ansible-2.9.20-1.el8.noarch is filtered out by exclude
filtering
- package ansible-2.9.16-1.el8.noarch is filtered out by exclude
filtering
- package ansible-2.9.19-1.el8.noarch is filtered out by exclude
filtering
- package ansible-2.9.23-1.el8.noarch is filtered out by exclude
filtering
- package ansible-1:2.9.27-4.el8.noarch is filtered out by exclude
filtering
(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)
[root@orthosie ~]# dnf repolist
repo id repo name
appstream CentOS Stream 8 - AppStream
baseos CentOS Stream 8 - BaseOS
dell-system-update_dependent dell-system-update_dependent
dell-system-update_independent dell-system-update_independent
extras CentOS Stream 8 - Extras
ovirt-4.4 Latest oVirt 4.4 Release
ovirt-4.4-centos-advanced-virtualization CentOS-8 - Advanced
Virtualization
ovirt-4.4-centos-ceph-pacific CentOS-8-stream - Ceph Pacific
ovirt-4.4-centos-gluster8 CentOS-8-stream - Gluster 8
ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch
ovirt-4.4-centos-openstack-victoria CentOS-8 - OpenStack victoria
ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-opstools-vault CentOS-8 - OpsTools - collectd - vault
ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr
repo for gluster-ansible owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr
repo for EL8_collection owned by sbonazzo
ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64
ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what
will be shipped in upcoming RHEL
powertools CentOS Stream 8 - PowerTools
John Florian
On 2022-02-21 08:05, Andrea Chierici wrote:
Dear all,
lately the engine started notifying me about some "errors":
"Failed to check for available updates on host XYZ with message
'Task Ensure Python3 is installed for CentOS/RHEL8 hosts failed to
execute. Please check logs for more details"
I do understand this is not something that can impact my cluster
stability, since it's only a matter of checking updates, anyway it
annoys me a lot.
I checked the logs and apparently the issue is related to some repos
that are missing/unresolved.
Right now on my hosts I have these repos:
ovirt-release44-4.4.8.3-1.el8.noarch
epel-release-8-13.el8.noarch
centos-stream-release-8.6-1.el8.noarch
puppet5-release-5.0.0-5.el8.noarch
The problems come from:
Error: Failed to download metadata for repo
'ovirt-4.4-centos-gluster8': Cannot prepare internal mirrorlist: No
URLs in mirrorlist
Error: Failed to download metadata for repo
'ovirt-4.4-centos-opstools': Cannot prepare internal mirrorlist: No
URLs in mirrorlist
Error: Failed to download metadata for repo
'ovirt-4.4-openstack-victoria': Cannot download repomd.xml: Cannot
download repodata/repomd.xml: All mirrors were tried
If I disable these repos "yum update" can finish but then I get a
large number of unresolved dependencies and "problems":
Error:
Problem 1: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
requires ansible, but none of the providers can be installed
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.25-1.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.27-1.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.17-1.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.18-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.20-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.21-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.23-2.el8.noarch
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.24-2.el8.noarch
- package ansible-2.9.27-2.el8.noarch conflicts with ansible-core
> 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64
- package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible <
2.10.0 provided by ansible-2.9.27-2.el8.noarch
- cannot install the best update candidate for package
cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
- cannot install the best update candidate for package
ansible-2.9.25-1.el8.noarch
- package ansible-2.9.20-1.el8.noarch is filtered out by exclude
filtering
Problem 2: package fence-agents-ibm-powervs-4.2.1-84.el8.noarch
requires fence-agents-common = 4.2.1-84.el8, but none of the
providers can be installed
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-84.el8.noarch
- cannot install the best update candidate for package
fence-agents-ibm-powervs-4.2.1-77.el8.noarch
- cannot install the best update candidate for package
fence-agents-common-4.2.1-77.el8.noarch
Problem 3: cannot install both
fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires
fence-agents-common = 4.2.1-84.el8, but none of the providers can be
installed
- package fence-agents-amt-ws-4.2.1-88.el8.noarch requires
fence-agents-common >= 4.2.1-88.el8, but none of the providers can
be installed
- cannot install the best update candidate for package
fence-agents-ibm-vpc-4.2.1-77.el8.noarch
- cannot install the best update candidate for package
fence-agents-amt-ws-4.2.1-77.el8.noarch
Problem 4: problem with installed package
fence-agents-ibm-vpc-4.2.1-77.el8.noarch
- package fence-agents-ibm-vpc-4.2.1-77.el8.noarch requires
fence-agents-common = 4.2.1-77.el8, but none of the providers can be
installed
- package fence-agents-ibm-vpc-4.2.1-78.el8.noarch requires
fence-agents-common = 4.2.1-78.el8, but none of the providers can be
installed
- package fence-agents-ibm-vpc-4.2.1-82.el8.noarch requires
fence-agents-common = 4.2.1-82.el8, but none of the providers can be
installed
- package fence-agents-ibm-vpc-4.2.1-83.el8.noarch requires
fence-agents-common = 4.2.1-83.el8, but none of the providers can be
installed
- package fence-agents-ibm-vpc-4.2.1-84.el8.noarch requires
fence-agents-common = 4.2.1-84.el8, but none of the providers can be
installed
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-77.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-78.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-82.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-83.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-apc-4.2.1-88.el8.noarch requires
fence-agents-common >= 4.2.1-88.el8, but none of the providers can
be installed
- cannot install the best update candidate for package
fence-agents-apc-4.2.1-77.el8.noarch
Problem 5: problem with installed package
fence-agents-ibm-powervs-4.2.1-77.el8.noarch
- package fence-agents-ibm-powervs-4.2.1-77.el8.noarch requires
fence-agents-common = 4.2.1-77.el8, but none of the providers can be
installed
- package fence-agents-ibm-powervs-4.2.1-78.el8.noarch requires
fence-agents-common = 4.2.1-78.el8, but none of the providers can be
installed
- package fence-agents-ibm-powervs-4.2.1-82.el8.noarch requires
fence-agents-common = 4.2.1-82.el8, but none of the providers can be
installed
- package fence-agents-ibm-powervs-4.2.1-83.el8.noarch requires
fence-agents-common = 4.2.1-83.el8, but none of the providers can be
installed
- package fence-agents-ibm-powervs-4.2.1-84.el8.noarch requires
fence-agents-common = 4.2.1-84.el8, but none of the providers can be
installed
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-77.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-78.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-82.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-83.el8.noarch
- cannot install both fence-agents-common-4.2.1-88.el8.noarch and
fence-agents-common-4.2.1-84.el8.noarch
- package fence-agents-apc-snmp-4.2.1-88.el8.noarch requires
fence-agents-common >= 4.2.1-88.el8, but none of the providers can
be installed
- cannot install the best update candidate for package
fence-agents-apc-snmp-4.2.1-77.el8.noarch
My question is: since I am not willing to update anything right now,
and I just want to get rid of the stupid python3 error, should I
disable these repos, even if now I get some dep issues or the
solution is another?
Any suggestion?
Thanks,
Andrea
_______________________________________________
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/UX4J2G5VDZR76I4XMOF5BDCTSK3D4ETS/
_______________________________________________
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-le...@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/2PFW37RSBC6USJQE375DDXYWZOF7XQCV/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PJI6M4D2LRW2UVFHAXCFUFPUYKP6K4X6/
