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 2004397 - Sync of a Kickstart repo to the N-1 capsule fails
Summary: Sync of a Kickstart repo to the N-1 capsule fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-15 08:13 UTC by Vladimír Sedmík
Modified: 2021-11-16 14:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: Attempting to synchronize a Kickstart repository to a Satellite 6.9 Capsule (running Pulp 2) fails with an importer error. Consequence: Synchronization of kickstart repository to Satellite 6.9 Capsule fails. Workaround (if any): 1. Set the Download Policy of the kickstart repository to 'Immediate' 2. Synchronize the repository at the Satellite 3. Synchronize the environment containing the repository to the Capsule. If the repository is in a non-Library environment, the content view that it is a member of must be published and promoted to that environment. Result: The synchronization of the Satellite 6.9 capsule will be successful.
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 9325 0 Normal CLOSED - CURRENTRELEASE Backport #9213 "DNF gets wrong rpm download size, until package downloaded with curl, then works" to 3.14.z 2021-09-29 21:07:30 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:13:58 UTC

Description Vladimír Sedmík 2021-09-15 08:13:16 UTC 
Description of problem:
Sync of a Kickstart repo to the N-1 capsule (pulp3 -> pulp2) fails with an importer error.


Version-Release number of selected component (if applicable):
6.10.0 snap 18


How reproducible:
always


Steps to Reproduce:
1. Have a blank 6.10 Satellite with registered 6.9 Capsule with immediate policy (Satellite was upgraded from 6.9)
2. Sync a KS repo to the SAT (I used 'Red Hat Enterprise Linux 7 Server Kickstart x86_64 7.9' and later retried with 'Red Hat Enterprise Linux 8 for x86_64 - BaseOS Kickstart 8.4')
3. Create an LCE, assign the Capsule to the LCE
4. Create a CV with the KS repo, publish and promote it to the LCE


Actual results:
Capsule is being synced with the KS repo but the task fails with error
'PLP0000: Importer indicated a failed response'


Expected results:
Successful sync


Additional information:
There is a workaround: Set the immediate download policy to the Kickstart repo, resync it and then resync the Capsule.
Comment 2 Brad Buckingham 2021-09-15 17:28:19 UTC 
Justin,

Based upon the description, should this be proposed for Satellite 6.9.z or 6.10?

I am assuming 6.9.z as it appears the error is on the Capsule (running 6.9).

Thanks!
Comment 3 Justin Sherrill 2021-09-15 18:54:57 UTC 
I'm not sure we know enough about whether this is a problem with the 6.10 Satellite server or the 6.9 capsule server.  The error was thrown on the capsule server, but that may not be where the fix (if there is one) ends up.  I think the pulp team needs to investigate to figure that out.
Comment 4 Daniel Alley 2021-09-24 15:39:25 UTC 
I suspect this is the same issue as https://pulp.plan.io/issues/9213

Which was fixed by pulpcore 3.14.6, released Sept 2, but not in the latest snaps yet.
Comment 6 pulp-infra@redhat.com 2021-09-29 21:07:31 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 7 pulp-infra@redhat.com 2021-09-29 21:07:32 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 8 Vladimír Sedmík 2021-10-01 14:37:19 UTC 
Verified on 6.10.0 snap 21 with python3-pulpcore-3.14.7-1.el7pc.noarch - successfully synced rhel-7-server-kickstart, rhel-8-for-x86_64-baseos-kickstart and rhel-8-for-x86_64-appstream-kickstart to the 6.9.6 capsule
Comment 11 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.