Bug 1980509 - Upgrade Pulpcore version to 3.14 in katello
Summary: Upgrade Pulpcore version to 3.14 in katello
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.10.0
Assignee: Ian Ballou
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-08 18:00 UTC by Ian Ballou
Modified: 2021-11-16 14:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:12:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32933 0 Normal Closed Upgrade Pulpcore and plugins to 3.14 for Katello master 2021-07-08 19:21:37 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:12:42 UTC

Description Ian Ballou 2021-07-08 18:00:41 UTC
The Pulpcore version in Satellite 6.10 needs to be upgraded to 3.14 to get the latest tasking system among other numerous fixes.

Comment 1 Ian Ballou 2021-07-08 18:03:10 UTC
I'll be making a downstream MR to Katello to get these changes in.

Comment 2 Ian Ballou 2021-07-08 19:19:21 UTC
I didn't realize that 6.10 was still being built with upstream gems, so no MR should be needed.

Comment 3 Bryan Kearney 2021-07-08 20:01:10 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32933 has been resolved.

Comment 7 errata-xmlrpc 2021-11-16 14:12:32 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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702


Note You need to log in before you can comment on or make changes to this bug.