Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 2121892

Summary: ansible-2.9.27-3.fc35.noarch conflicts with ansible-base
Product: [Fedora] Fedora Reporter: Randy Barlow <randy>
Component: ansible-packagingAssignee: Maxwell G <maxwell>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: aaron.lwe, a.badger, dmsimard, kevin, maxwell, ngompa13, patrick, sergio
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ansible-packaging-1-8.fc35 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-31 10:14:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Randy Barlow 2022-08-27 02:58:49 UTC
Hello Kevin!

Description of problem:
I noticed that there was a conflict with an ansible update when I went to dnf update an F35 system today.


Version-Release number of selected component (if applicable):
ansible-2.9.27-3.fc35.noarch


How reproducible:
Every time on this particular system.


Steps to Reproduce:
1. dnf upgrade


Actual results:
 Problem 1: package ansible-packaging-1-7.fc35.noarch requires ansible-core, but none of the providers can be installed
  - package ansible-2.9.27-3.fc35.noarch conflicts with ansible-base > 2.10.0 provided by ansible-core-2.11.5-1.fc35.noarch
  - package ansible-2.9.27-3.fc35.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.11.5-1.fc35.noarch
  - package ansible-core-2.11.5-1.fc35.noarch conflicts with ansible <= 2.9.99 provided by ansible-2.9.27-3.fc35.noarch
  - package ansible-2.9.27-3.fc35.noarch conflicts with ansible-base > 2.10.0 provided by ansible-core-2.12.7-1.fc35.noarch
  - package ansible-2.9.27-3.fc35.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.7-1.fc35.noarch
  - package ansible-core-2.12.7-1.fc35.noarch conflicts with ansible <= 2.9.99 provided by ansible-2.9.27-3.fc35.noarch
  - cannot install the best update candidate for package ansible-packaging-1-5.fc35.noarch
  - cannot install the best update candidate for package ansible-2.9.27-3.fc35.noarch
 Problem 2: problem with installed package ansible-2.9.27-3.fc35.noarch
  - package ansible-2.9.27-3.fc35.noarch conflicts with ansible-base > 2.10.0 provided by ansible-core-2.12.7-1.fc35.noarch
  - package ansible-2.9.27-3.fc35.noarch conflicts with ansible-core > 2.11.0 provided by ansible-core-2.12.7-1.fc35.noarch
  - package ansible-core-2.12.7-1.fc35.noarch conflicts with ansible <= 2.9.99 provided by ansible-2.9.27-3.fc35.noarch
  - package ansible-packaging-1-7.fc35.noarch requires ansible-core, but none of the providers can be installed
  - package ansible-packaging-1-7.fc35.noarch conflicts with ansible-core < 2.12.1-3 provided by ansible-core-2.11.5-1.fc35.noarch
  - problem with installed package ansible-packaging-1-5.fc35.noarch
  - package ansible-packaging-1-5.fc35.noarch requires ansible-srpm-macros = 1-5.fc35, but none of the providers can be installed
  - cannot install both ansible-srpm-macros-1-7.fc35.noarch and ansible-srpm-macros-1-5.fc35.noarch
  - cannot install the best update candidate for package ansible-srpm-macros-1-5.fc35.noarch


Expected results:
No conflicts.


Additional info:
dnf does prompt me that I can use --allowerasing if I want to.

Comment 1 Maxwell G 2022-08-27 04:27:06 UTC
This is my fault[1]. ansible-packaging now requires ansible-core, as ansible 2.9 does not properly support `build_ignore` in galaxy.yml or unit testing, which I am starting to use for collections packaging. It used to have a boolean dependency. However, ansible still has

```
# Require packaging macros if rpm-build exists
# This makes the transition seamless for other packages
Requires: (ansible-packaging if rpm-build)
```

The ansible collection macros used to be part of `ansible` and they've since been split out.

After I confirm that every package that needs the macros actually BuildRequires the correct package, I'll probably remove the compat lines above. I already fixed many, if not all of the collections packages. I guess removing this could be considered a breaking change, but this package is not meant to be installed by users, anyways. I'll give it some thought.

In the meantime, I plan on temporarily reverting [1] in f35. Fedora 35 is the only supported release that still has ansible 2.9.

[1]: https://src.fedoraproject.org/rpms/ansible-packaging/c/a5b014cf2998723b2a3de55a806330d41008e4b6?branch=rawhide

Comment 2 Maxwell G 2022-08-27 04:42:12 UTC
I've submitted a PR. I will test it more and merge it tomorrow.

Comment 3 Sergio Basto 2022-08-27 19:04:24 UTC
(In reply to Maxwell G from comment #2)
> I've submitted a PR. I will test it more and merge it tomorrow.

I cant find your PR ? I also like to test it , thank you

Comment 4 Sergio Basto 2022-08-27 19:09:55 UTC
I found the PR is in ansible-packing

https://src.fedoraproject.org/rpms/ansible-packaging/pull-request/5#request_diff

Comment 5 Maxwell G 2022-08-27 19:33:52 UTC
I linked the PR to the Bugzilla under the Bugzilla's Links section.

Comment 6 Maxwell G 2022-08-27 19:38:53 UTC
(In reply to Maxwell G from comment #5)
> I linked the PR to the Bugzilla under the Bugzilla's Links section.

s/to the Bugzilla//

Comment 7 Fedora Update System 2022-08-27 19:43:02 UTC
FEDORA-2022-5fa642c334 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5fa642c334

Comment 8 Fedora Update System 2022-08-28 23:29:18 UTC
FEDORA-2022-5fa642c334 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-5fa642c334`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5fa642c334

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Maxwell G 2022-08-31 02:25:18 UTC
*** Bug 2122845 has been marked as a duplicate of this bug. ***

Comment 10 Fedora Update System 2022-08-31 10:14:52 UTC
FEDORA-2022-5fa642c334 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.