Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Repository sync for some RHEL repos fails with:
~~~
Artifact() got an unexpected keyword argument 'sha'
~~~~
Version-Release number of selected component (if applicable):
Satellite 6.10.1
How reproducible:
Always
Steps to Reproduce:
1. Enable 'Red Hat Enterprise Linux 5 Server Kickstart x86_64 5.10' repository
2. Start the sync
Actual results:
Repo fails to sync (task ends in stopped/warning state).
Expected results:
Repo syncs successfully.
Additional info:
I am able to reproduce this on fresh Satellite 6.10 install.
Comment 4pulp-infra@redhat.com
2021-12-08 20:09:24 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2021-12-08 20:09:25 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2021-12-08 21:07:55 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 7pulp-infra@redhat.com
2021-12-22 17:18:35 UTC
The Pulp upstream bug status is at CLOSED - DUPLICATE. Updating the external tracker on this bug.
Steps to retest:
1. Import a manifest
2. enabled 'Red Hat Enterprise Linux 6 Server RPMs x86_64 6.5' and 'Red Hat Enterprise Linux 6 Server RPMs x86_64 6.5'
3. Sync repo
Expected:
Syncing should complete successfully
Actual:
Syncing does complete successfully
I tried the KS 5, but there's issues with the repo. Since this issue's main focus is on 'sha' and the two repos above does have it and it complete successfully, then I would say this issue is resolved.
Verified on 6.11_snap18 with python38-pulp-rpm-3.17.3-2.el8pc.noarch on both rhel8 and rhel7
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.11 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-2022:5498