Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 2010207 - RHEL6.10 kickstart repo sync error "incompatible with 'mirror' sync"
Summary: RHEL6.10 kickstart repo sync error "incompatible with 'mirror' sync"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-04 08:01 UTC by Stephen Wadeley
Modified: 2021-11-16 14:13 UTC (History)
8 users (show)

Fixed In Version: python-pulp-rpm-3.14.6,python-pulpcore-3.14.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:13:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 9486 0 Normal CLOSED - CURRENTRELEASE Some repositories are unnecessarily prevented from using mirror-metadata sync 2021-10-20 20:08:13 UTC
Pulp Redmine 9487 0 Normal CLOSED - CURRENTRELEASE Backport #9486 "Some repositories are unnecessarily prevented from using mirror-metadata sync" to 3.14.z 2021-10-05 14:56:53 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:13:58 UTC

Description Stephen Wadeley 2021-10-04 08:01:06 UTC 
Description of problem:

Attempting to sync a RHEL 6.10 kickstart repo with default settings fails


Version-Release number of selected component (if applicable):
Sat 6.10 snap 21
foreman-2.5.2.13-1.el7sat.noarch
katello-4.1.1-1.el7sat.noarch


How reproducible:
TBA


Steps to Reproduce:
1. Add 6.9 manifest (no 6.10 available at time of testing)
2. In web UI, navigate Content > Red Hat Repositories. Enable rhel-6-server-kickstart repo (Red Hat Enterprise Linux 6 Server Kickstart x86_64 6.10)
3. Navigate Content > Sync Status
4. Select the repo and click Synchronize Now

Actual results:
Task page displays:
This repository uses features which are incompatible with 'mirror' sync. Please sync without mirroring enabled.

Expected results:
Default settings should work


Additional info:
After changing repo to "Mirror on Sync No" I could sync it.
Comment 1 Brad Buckingham 2021-10-04 13:06:56 UTC 
Is this a regression from Satellite 6.9?
Comment 2 Justin Sherrill 2021-10-04 13:29:42 UTC 
This is a regression, granted there will be some repos where this will regress due to the nature of the change.  However we didn't expect this with any RH repos.

Daniel, 
any idea why this repo wouldn't support mirror mode?  I can attach the repomd.xml and primary.xml, nothing stood out to me.
Justin
Comment 5 Daniel Alley 2021-10-04 17:49:08 UTC 
The issue is that a subrepo, a "variant" in the kickstart repo, uses relative paths to packages which are contained in the repo. This is actually compatible with mirroring in a conceptual sense, but our heuristics didn't take it into account.

This is relatively straightforwards to fix, I've just filed a PR upstream to do so, and then we can backport it.
Comment 6 pulp-infra@redhat.com 2021-10-04 18:11:04 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 7 pulp-infra@redhat.com 2021-10-04 18:11:05 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 8 pulp-infra@redhat.com 2021-10-04 21:07:00 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 9 pulp-infra@redhat.com 2021-10-05 14:56:54 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 10 pulp-infra@redhat.com 2021-10-05 14:56:56 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 12 pulp-infra@redhat.com 2021-10-11 20:08:13 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 13 pulp-infra@redhat.com 2021-10-11 20:08:14 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 14 pulp-infra@redhat.com 2021-10-20 20:08:14 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 17 errata-xmlrpc 2021-11-16 14:13:51 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.