Bug 2024889 - Syncing RHEL 5 KS repository fails with: " Artifact() got an unexpected keyword argument 'sha' "
Summary: Syncing RHEL 5 KS repository fails with: " Artifact() got an unexpected key...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.0
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
: 2033970 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-19 12:36 UTC by Jan Senkyrik
Modified: 2023-03-30 20:51 UTC (History)
12 users (show)

Fixed In Version: tfm-pulpcore-python-pulp-rpm-3.17.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2043704 (view as bug list)
Environment:
Last Closed: 2022-07-05 14:30:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulp_rpm issues 2319 0 None closed Artifact() got an unexpected keyword argument 'sha' 2022-01-11 21:22:20 UTC
Pulp Redmine 9580 0 Normal CLOSED - DUPLICATE Artifact() got an unexpected keyword argument 'sha' 2021-12-22 17:18:34 UTC
Red Hat Knowledge Base (Solution) 6962828 0 None None None 2022-06-12 17:46:32 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:30:16 UTC

Description Jan Senkyrik 2021-11-19 12:36:20 UTC
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 4 pulp-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 5 pulp-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 6 pulp-infra@redhat.com 2021-12-08 21:07:55 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 7 pulp-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.

Comment 8 Grant Gainey 2022-01-11 21:22:20 UTC
Pulp upstream moved to github-issues, adding the upstream tracker

Comment 9 Grant Gainey 2022-01-11 21:22:46 UTC
*** Bug 2033970 has been marked as a duplicate of this bug. ***

Comment 23 Lai 2022-04-27 21:18:05 UTC
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

Comment 26 errata-xmlrpc 2022-07-05 14:30:00 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 (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


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