Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-16337

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

XMLWordPrintable

    • 0
    • False
    • Moderate
    • Sprint 117, Sprint 118, Sprint 119, Sprint 120
    • None
    • None
    • None
    • None

      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:

              rhn-engineering-paji Partha Aji
              jira-bugzilla-migration RH Bugzilla Integration
              David Moore David Moore (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: