Hi.
Previously I have had issues with OL8 based OLVM 4.4 systems when Ansible 2.9.x dep was moved to anisble-core
issue 1 : https://forums.oracle.com/ords/apexds/post/olvm-4-4-x-ol8-based-nodes-updates-failing-all-of-them-due-4729
This was fixed by excluding ansible-core
Shortly after we then had another problem (on all OLVM nodes)
Issue 2 : After doing the above change later I needed to remove the exclusion then
# rpm -e --nodeps anisble
# dnf install ansible-core
Then updates worked as normal
My issue is one node hasn't been updated in the last year and now none of the solutions work at all
i.e if I try solution 1 (above)
# dnf update --exclude=ansible-core
Last metadata expiration check: 0:13:02 ago on Thu 14 Mar 2024 11:19:04 UTC.
Error:
Problem 1: package gluster-ansible-repositories-1.0.1-5.module+el8.8.0+90097+18e1d3b8.noarch requires ansible-core >= 2.12, but none of the providers can be installed
- cannot install the best update candidate for package gluster-ansible-repositories-1.0.1-3.module+el8.4.0+20194+c25df5f0.noarch
- package ansible-core-2.12.2-3.1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.12.2-4.el8_6.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-2.el8_7.x86_64 is filtered out by exclude filtering
- package ansible-core-2.14.2-3.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.15.3-1.el8.x86_64 is filtered out by exclude filtering
Problem 2: package gluster-ansible-maintenance-1.0.1-12.module+el8.8.0+90097+18e1d3b8.noarch requires ansible-core >= 2.12, but none of the providers can be installed
- cannot install the best update candidate for package gluster-ansible-maintenance-1.0.1-10.module+el8.4.0+20194+c25df5f0.noarch
- package ansible-core-2.12.2-3.1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.12.2-4.el8_6.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-2.el8_7.x86_64 is filtered out by exclude filtering
- package ansible-core-2.14.2-3.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.15.3-1.el8.x86_64 is filtered out by exclude filtering
Problem 3: package gluster-ansible-infra-1.0.4-22.0.1.module+el8.8.0+90097+18e1d3b8.noarch requires ansible-core >= 2.12, but none of the providers can be installed
- cannot install the best update candidate for package gluster-ansible-infra-1.0.4-18.module+el8.4.0+20194+c25df5f0.noarch
- package ansible-core-2.12.2-3.1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.12.2-4.el8_6.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-2.el8_7.x86_64 is filtered out by exclude filtering
- package ansible-core-2.14.2-3.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.15.3-1.el8.x86_64 is filtered out by exclude filtering
Problem 4: package gluster-ansible-features-1.0.5-15.module+el8.8.0+90097+18e1d3b8.noarch requires ansible-core >= 2.12, but none of the providers can be installed
- cannot install the best update candidate for package gluster-ansible-features-1.0.5-9.module+el8.4.0+20194+c25df5f0.noarch
- package ansible-core-2.12.2-3.1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.12.2-4.el8_6.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-2.el8_7.x86_64 is filtered out by exclude filtering
- package ansible-core-2.14.2-3.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.15.3-1.el8.x86_64 is filtered out by exclude filtering
Problem 5: package gluster-ansible-cluster-1.0-5.module+el8.8.0+90097+18e1d3b8.noarch requires ansible-core >= 2.12, but none of the providers can be installed
- cannot install the best update candidate for package gluster-ansible-cluster-1.0-2.1.module+el8.4.0+20194+c25df5f0.noarch
- package ansible-core-2.12.2-3.1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.12.2-4.el8_6.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-1.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.13.3-2.el8_7.x86_64 is filtered out by exclude filtering
- package ansible-core-2.14.2-3.el8.x86_64 is filtered out by exclude filtering
- package ansible-core-2.15.3-1.el8.x86_64 is filtered out by exclude filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
and if I try solution 2
[root@ng2-olvm-stbdb2 mcox]# dnf update
Last metadata expiration check: 0:25:28 ago on Thu 14 Mar 2024 11:19:04 UTC.
Error:
Problem: package ovirt-ansible-collection-1.6.6-1.0.8.el8.noarch requires ansible >= 2.9.21, but none of the providers can be installed
- package ansible-core-2.15.3-1.el8.x86_64 conflicts with ansible < 2.10.0 provided by ansible-2.9.27-2.el8.noarch
- package ansible-2.9.27-2.el8.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.15.3-1.el8.x86_64
- cannot install the best update candidate for package ovirt-ansible-collection-1.6.6-1.0.7.el8.noarch
- cannot install the best update candidate for package ansible-core-2.15.3-1.el8.x86_64
I have also tried
# dnf update --nobest - and that looks like it will nearly work but gives at the end
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
ansible noarch 2.9.27-2.el8 ovirt-4.4-extra 17 M
Skipping packages with broken dependencies:
ovirt-ansible-collection noarch 1.6.6-1.0.8.el8 ovirt-4.4 292 k
Is doing the above ok or can anyone suggest anything to fix this without reinstalling the entire system
Thanks