Bug 1684697 - Unable to sync 3 SLES Update repositories
Summary: Unable to sync 3 SLES Update repositories
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.4.0
Hardware: x86_64
OS: Linux
high
unspecified
Target Milestone: 6.4.3
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-01 21:50 UTC by Mike McCune
Modified: 2021-04-06 17:47 UTC (History)
11 users (show)

Fixed In Version: pulp-rpm-2.16.4.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1673215
Environment:
Last Closed: 2019-04-29 18:15:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 4397 0 Normal CLOSED - CURRENTRELEASE Unable to sync 3 SLES Update repositories 2019-04-02 21:01:28 UTC
Red Hat Product Errata RHBA-2019:0903 0 None None None 2019-04-29 18:15:41 UTC

Comment 1 pulp-infra@redhat.com 2019-03-11 13:32:12 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 2 pulp-infra@redhat.com 2019-03-11 13:32:13 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2019-03-20 09:31:45 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 5 pulp-infra@redhat.com 2019-04-02 21:01:29 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 6 jcallaha 2019-04-08 19:43:23 UTC 
Verified in satellite 6.4.3 Snap 1 

Created two repositories, based on the same upstream repo: https://repos.fedorapeople.org/pulp/pulp/fixtures/srpm-duplicate/

The first was not set to skip anything
The second was set to skip src rpms

Both repos synced successfully
The first brought in the two expected source rpms
The second ignored all source rpms
Comment 8 errata-xmlrpc 2019-04-29 18:15:35 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/RHBA-2019:0903
Note You need to log in before you can comment on or make changes to this bug.