2166435 – Exporting repositories that have architecture restrictions results in bogus data that can't be properly imported

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 2166435 - Exporting repositories that have architecture restrictions results in bogus data that can't be properly imported

Summary: Exporting repositories that have architecture restrictions results in bogus d...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Inter Satellite Sync
Sub Component:
Version:	6.12.1
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	medium
Target Milestone:	6.14.0
Assignee:	Partha Aji
QA Contact:	David Moore
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2023-02-01 20:01 UTC by Joniel Pasqualetto
Modified:	2024-03-07 15:30 UTC (History)
CC List:	7 users (show)
Fixed In Version:	rubygem-katello-4.9.0.2-1
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-11-08 14:18:30 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	36477	Normal	New	Exporting repositories that have architecture restrictions results in bogus data that can't be properly imported	2023-06-06 14:07:55 UTC
Red Hat Issue Tracker	SAT-16337	None	None	None	2023-03-07 00:23:49 UTC
Red Hat Product Errata	RHSA-2023:6818	None	None	None	2023-11-08 14:19:06 UTC

Description Joniel Pasqualetto 2023-02-01 20:01:43 UTC

Description of problem:

When exporting a repository that has the option "Restrict to architecture" set, results in bogus metadata. The exported content, when being imported, only generates an empty repository.

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

Observed on Satellite 6.11 and 6.12

How reproducible:
Always

Steps to Reproduce:
1. Enable a repository and configure it to immediate download
2. Edit the repository options and define "Restrict to architecture" to x86_64
3. Export the repository
4. Try importing the exported repository in another Satellite. 

Actual results:
The task itself success (no errors are reported), but the result is an empty repository.
On pulp logs, we can see a warning like this:

~~~
Feb 01 19:51:52 sat611.jpasqualetto.local pulpcore-worker-1[99534]: pulp [749ed56e-880f-4d1b-ac19-e17e6b18cadf]: pulpcore.app.tasks.importer:WARNING: Could not find destination repo for Red_Hat_Satellite_Client_6_for_RHEL_9_x86_64_RPMs-127736. Skipping.
~~~

Looking at the task details on dynflow, one can see a very small number of steps being executed. 

Expected results:

Should be able to import the data into another Satellite and bring the content.

Additional info:

Comment 1 Joniel Pasqualetto 2023-02-01 20:11:29 UTC

Workaround for those hitting the problem: remove the restrictions from the repositories and export them again.

Comment 2 Brad Buckingham 2023-02-02 15:06:52 UTC

Does this only apply to Custom (i.e. not Red Hat) repositories?

Thanks!

Comment 3 Joniel Pasqualetto 2023-02-02 15:18:09 UTC

Hello Brad

No! I actually didn't test on custom, only on Red Hat repositories. The customers I saw facing this issue were also using Red Hat repositories.

Comment 5 Partha Aji 2023-06-06 14:07:54 UTC

Connecting redmine issue https://projects.theforeman.org/issues/36477 from this bug

Comment 6 Bryan Kearney 2023-06-10 00:02:53 UTC

Upstream bug assigned to paji

Comment 7 Bryan Kearney 2023-06-10 00:02:55 UTC

Upstream bug assigned to paji

Comment 8 Bryan Kearney 2023-06-30 00:02:40 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36477 has been resolved.

Comment 13 errata-xmlrpc 2023-11-08 14:18:30 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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818

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