Description of problem: Version-Release number of selected component (if applicable): AlmaLinux 8.6 Beta How reproducible: Occurs with every dnf udpate when ansible is installed and when ansible-core cannot be installed Steps to Reproduce: 1. remove ansible sudo dnf remove ansible 2. install ansible core and community collection sudo dnf install ansible-collection-community-general and install fails due to version conflict and receive conflict listed below 3. try install insalling ansible with community collection sudo dnf install ansible-collection-community-general 4. run sudo dnf update from the cli or using ansible's dnf module Actual results: output from step 2: Last metadata expiration check: 0:32:45 ago on Fri 06 May 2022 11:30:43 PM CDT. Error: Problem: package ansible-collection-community-general-3.8.6-1.el8.noarch requires (ansible >= 2.9.0 or ansible-base > 2.10.0), 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.27-1.el8.noarch - cannot install the best update candidate for package ansible-collection-community-general-3.8.6-1.el8.noarch - cannot install the best update candidate for package ansible-2.9.27-1.el8.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) output from step 4: Error: Problem: package ansible-collection-community-general-3.8.6-1.el8.noarch requires (ansible >= 2.9.0 or ansible-base > 2.10.0), 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.27-1.el8.noarch - conflicting requests (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Expected results: install and updates completes successfully with ansible-core or ansible installed and community general collection like in fedora
We are aware of this issue. As a temporary workaround, you can install ansible-collection-community-general from epel8-next.
This fix worked after runn sudo dnf install epel-next-release thanks for the help
FEDORA-EPEL-2022-e22a656909 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-e22a656909
FEDORA-EPEL-2022-e22a656909 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-e22a656909 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-12a5ea8bb3 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-12a5ea8bb3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-12a5ea8bb3 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.