Bug 1687938 - Incremental update with errata should copy all modules over to resulting cv
Summary: Incremental update with errata should copy all modules over to resulting cv
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Released
Assignee: Partha Aji
QA Contact: Omkar Khatavkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 17:21 UTC by Justin Sherrill
Modified: 2019-10-07 17:19 UTC (History)
7 users (show)

Fixed In Version: tfm-rubygem-katello-3.10.0.40-1,tfm-rubygem-katello-3.10.0.42-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-14 19:57:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Incremental Update (49.35 KB, image/png)
2019-04-09 12:11 UTC, Omkar Khatavkar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26364 0 Normal Closed Incremental update with errata should copy all modules over to resulting cv 2020-02-06 16:38:01 UTC

Description Justin Sherrill 2019-03-12 17:21:18 UTC 
Description of problem:

The following issue https://pulp.plan.io/issues/4518

indicates that when copying errata in pulp from one repo to another, the associated modules are not copied.  The only use case in katello for this is incremental update.  To work around this (and to match what cv w/ filters does today), we could just copy all modules across (without rpms) as part of inc publish
Comment 3 pulp-infra@redhat.com 2019-03-12 19:02:02 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2019-03-12 19:02:03 UTC 
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 5 Robin Chan 2019-03-12 20:53:35 UTC 
If there is a low risk/effort work around that katello can implement, I'd like to spend our resources getting Pulp 2.19.0 done ASAP. I'm inclined to close the upstream pulp issue as a no-fix. will there be a katello issue for the work around and the removal of the work around when katello takes Pulp 2.19.0? I'd like to link all those issues so we can track what gets done when.
Comment 6 pulp-infra@redhat.com 2019-03-13 15:31:45 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 7 pulp-infra@redhat.com 2019-03-13 16:01:53 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 8 Justin Sherrill 2019-03-14 15:27:35 UTC 
Created redmine issue https://projects.theforeman.org/issues/26364 from this bug
Comment 9 Justin Sherrill 2019-03-14 15:34:01 UTC 
Removing the pulp issue, since that will resolve this in 6.6 and this bz is for 6.5
Comment 11 Bryan Kearney 2019-03-28 18:01:04 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26364 has been resolved.
Comment 14 Omkar Khatavkar 2019-04-09 12:10:20 UTC 
Verified Satellite 6.5 Snap 22, I was able to do an incremental update with errata as same steps followed based on https://github.com/Katello/katello/pull/8048#issuecomment-477646725. 

Works fine and attached the screenshot.
Comment 15 Omkar Khatavkar 2019-04-09 12:11:03 UTC 
Created attachment 1553830 [details]
Incremental Update
Comment 16 Omkar Khatavkar 2019-04-23 13:02:37 UTC 
Marking this as verified based on my own comment made earlier.
Comment 17 Bryan Kearney 2019-05-14 19:57:31 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, 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-2019:1222
Note You need to log in before you can comment on or make changes to this bug.