Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2103699

Summary: Update ansible-core to 2.13.1
Product: Red Hat Enterprise Linux 8 Reporter: Dimitri Savineau <dsavinea>
Component: ansible-coreAssignee: Dimitri Savineau <dsavinea>
Status: CLOSED ERRATA QA Contact: Matt Clay <mclay>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.7CC: jhughes, maxwell
Target Milestone: rcKeywords: Rebase, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ansible-core-2.13.1-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-08 09: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:
Attachments:
Description Flags
ansible-core-2.13.1.patch none

Description Dimitri Savineau 2022-07-04 14:25:48 UTC
Description of problem:

Update ansible-core to a newer version (2.13.1)

The RPM package will also be built with python 3.9 instead of 3.8

Comment 1 Maxwell G 2022-07-04 15:24:50 UTC
Will this come with a bump from python38 > python39, as well?

Comment 2 Dimitri Savineau 2022-07-04 15:28:23 UTC
That's right, I forgot to mentioned it in this BZ but it's included in the commit message as well as the RPM spec changelog.

This probably means we need a BZ for the centos stream 8 component to track this change too.

Comment 3 Maxwell G 2022-07-04 16:12:14 UTC
> That's right, I forgot to mentioned it in this BZ but it's included in the commit message as well as the RPM spec changelog.

Yeah, I was asking, because outsiders cannot see PRs for c8s[1]. Thanks for the clarification! It would be nice if you could upload the patch here, so I can start testing ansible in EPEL 8 Next and have the appropriate updates prepared by the time it gets pushed out to the CentOS Stream 8 mirrors.

[1]: Technically, they're made against RHEL 8, but they still propagate over to c8s before RHEL, assuming there isn't some issue with the finicky sync process.

Comment 4 Maxwell G 2022-07-04 16:18:58 UTC
> This probably means we need a BZ for the centos stream 8 component to track this change too.

Technically, CentOS Stream (for both RHEL 8 and 9) shares a product with RHEL. It just has its own entry in the Version field. Does this need to be built against a separate python39 build target just like it did for python38? If so, that probably should be clarified to the CentOS Stream team.

Comment 5 Dimitri Savineau 2022-07-04 16:42:16 UTC
Created attachment 1894549 [details]
ansible-core-2.13.1.patch

Comment 6 Dimitri Savineau 2022-07-04 16:46:07 UTC
> Technically, CentOS Stream (for both RHEL 8 and 9) shares a product with RHEL. It just has its own entry in the Version field. Does this need to be built against a separate python39 build target just like it did for python38? If so, that probably should be clarified to the CentOS Stream team.

Yes, the package needs a separate build target and that one needs to be updated to use python 3.9

I can only see python38-3.8 module stream in the current c8s build tag for ansible-core [1]

[1] https://koji.mbox.centos.org/koji/taginfo?tagID=dist-c8-stream-ansible-build

Comment 10 Maxwell G 2022-07-18 03:14:52 UTC
(In reply to Dimitri Savineau from comment #6)
> > Does this need to be built against a separate python39 build target just like it did for python38? If so, that probably should be clarified to the CentOS Stream team.
> 
> Yes, the package needs a separate build target and that one needs to be
> updated to use python 3.9
> 
> I can only see python38-3.8 module stream in the current c8s build tag for
> ansible-core [1]
> 
> [1]
> https://koji.mbox.centos.org/koji/taginfo?tagID=dist-c8-stream-ansible-build

@jhughes, can you please take a look at this? This update has failed to build in c8s. It seems that this package gets rebuilt every day and keeps failing, as the python39 packages are not in the buildroot:

```
DEBUG util.py:439:  No matching package to install: 'python39-devel'
DEBUG util.py:439:  No matching package to install: 'python39-pip'
DEBUG util.py:439:  No matching package to install: 'python39-pyyaml'
DEBUG util.py:439:  No matching package to install: 'python39-rpm-macros'
DEBUG util.py:439:  No matching package to install: 'python39-setuptools'
DEBUG util.py:439:  No matching package to install: 'python39-wheel'
```

Comment 13 errata-xmlrpc 2022-11-08 09:14:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (ansible-core bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7456

Comment 14 Red Hat Bugzilla 2023-09-18 04:41:08 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days