Bug #36477
closedExporting repositories that have architecture restrictions results in bogus data that can't be properly imported
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.
Updated by Quinn James over 1 year ago
- Target version set to Katello 4.9.0
- Triaged changed from No to Yes
Updated by The Foreman Bot over 1 year ago
- Status changed from New to Ready For Testing
- Assignee set to Partha Aji
- Pull request https://github.com/Katello/katello/pull/10598 added
Updated by Jeremy Lenz over 1 year ago
- Target version changed from Katello 4.9.0 to Katello 4.9.1
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases Katello 4.10.0 added
Updated by Partha Aji over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|79ad3adf14ed97a9bd3eaa13191cfc2dadab24ff.
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases Katello 4.9.1 added