Project

General

Profile

Actions

Bug #36477

closed

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

Added by Partha Aji over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Inter Server Sync
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

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 Katello 4.8
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-199534: 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 server and bring the content.

Actions

Also available in: Atom PDF