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.
Bug 2094840 - Capsule sync fails with "Could not lookup a publication_href for repo <repo_id>
Summary: Capsule sync fails with "Could not lookup a publication_href for repo <repo_id>
Keywords:
Status: CLOSED DUPLICATE of bug 2103522
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.5
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-08 12:24 UTC by Jan Senkyrik
Modified: 2023-09-18 04:38 UTC (History)
12 users (show)

Fixed In Version: pulp_rpm 3.14.20, pulp_rpm 3.17.10
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-25 16:21:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulp_rpm issues 2407 0 None closed Conflicting content being published 2022-08-05 16:34:25 UTC
Red Hat Knowledge Base (Solution) 6962444 0 None None None 2022-06-08 12:42:51 UTC

Description Jan Senkyrik 2022-06-08 12:24:40 UTC 
Description of problem:

Capsule sync fails for centreon repository [0] with:
~~~
A file located at the url https://ktordeur-satellite-latest.sysmgmt.lan/pulp/content/Default_Organization/jsenkyri-test/centreon_rhel7/custom/centreon/centreon_rhel7/Packages/l/lua-curl-3.0.11-2.el7.centos.x86_64.rpm failed validation due to checksum. Could not lookup a publication_href for repo 219
~~~


Version-Release number of selected component (if applicable):
Satellite 6.10.5
Capsule 6.10.3


How reproducible:
Always


Steps to Reproduce:
1. Synchronize the following repo on Satellite:

# hammer repository info --id 216
~~~
Id:                      216
Name:                    centreon_rhel7
Label:                   centreon_rhel7
Description:             
Organization:            Default Organization
Red Hat Repository:      no
Content Type:            yum
Mirror on Sync:          no
Url:                     https://yum.centreon.com/standard/21.10/el7/stable/x86_64/
Publish Via HTTP:        yes
Published At:            https://ktordeur-satellite-latest.sysmgmt.lan/pulp/content/Default_Organization/Library/custom/centreon/centreon_rhel7/
Relative Path:           Default_Organization/Library/custom/centreon/centreon_rhel7
Download Policy:         immediate
Ignorable Content Units: 
HTTP Proxy:              
    HTTP Proxy Policy: global_default_http_proxy
Product:                 
    Id:   638
    Name: centreon
GPG Key:                 

Sync:                    
    Status:         Success
    Last Sync Date: 22 minutes
Created:                 2022/06/08 11:47:40
Updated:                 2022/06/08 11:55:18
Content Counts:          
    Packages:       261
    Source RPMS:    0
    Package Groups: 0
    Errata:         0
    Module Streams: 0
~~~

2. Add it to CV and sync the CV to Capsule
3. The capsule sync fails with the following error:

# hammer> capsule content synchronize --lifecycle-environment 'jsenkyri-test' --id 2 --organization-id 1
[............................................................................................................................................................................] [100%]
Error: A file located at the url https://ktordeur-satellite-latest.sysmgmt.lan/pulp/content/Default_Organization/jsenkyri-test/centreon_rhel7/custom/centreon/centreon_rhel7/Packages/l/lua-curl-3.0.11-2.el7.centos.x86_64.rpm failed validation due to checksum.
Could not lookup a publication_href for repo 219


Actual results:
Capsule sync fails.


Expected results:
Capsule sync succeeds.


Additional info:
It doesn't seem to matter which download policy is chosen. I tried both On-Demand and Immediate (Capsule sync policy was set to 'Inherit from repository' and got the same result.

I can provide logs and/or access to reproducer.


[0] https://yum.centreon.com/standard/21.10/el7/stable/x86_64/
Comment 3 Daniel Alley 2022-06-15 20:12:49 UTC 
This is an issue with the repository, 6.10.6 does a better job about warning (or failing outright) about metadata issues like this when they are encountered.

Here's the output from one of my repo-analysis tools.

(.env) [dalley@thinkpad test]$ rpmrepo download centreon --only-metadata https://yum.centreon.com/standard/21.10/el7/stable/x86_64/
(.env) [dalley@thinkpad test]$ rpmrepo check centreon
[ERROR] Package 'lua-curl-0:3.0.11-2.el7.centos.x86_64' has duplicated 'file' entries: 28 paths listed but only 7 are unique.
[ERROR] Duplicate package 'lua-curl-0:3.0.11-2.el7.centos.x86_64'
 appears 2 times with pkgids ['20bea7dbced139683c9597a127e41df7fe909d8783724996089674a097331e09', '2efefa686471c97fa5742eebcb37059d2bddd684d1be7151f21b4d3454dac8f5']


I will keep investigating to see if there's something we can handle better but to start with lets try to reach out to the repo owners and get this resolved.  I would do that myself but they seem to be a French company, so I have no idea what the correct channel is.
Comment 4 Daniel Alley 2022-06-15 20:14:08 UTC 
(we can leave this open for now, "something we can handle better" == "make sure there's not a bug I don't already know about")
Comment 5 Daniel Alley 2022-06-15 20:27:51 UTC 
There's a valid bug here, and it's already filed upstream, so I'm attaching it
Comment 7 pulp-infra@redhat.com 2022-08-05 16:34:26 UTC 
The Pulp upstream bug status is at closed. Updating the external tracker on this bug.
Comment 8 pulp-infra@redhat.com 2022-08-05 16:34:29 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 9 Georgios Atsigkioz 2022-08-22 07:42:47 UTC 
We have the error with :


A file located at the url https://xxxxx/pulp/content/content/dist/rhel8/8/x86_64/baseos/os/repodata/323df47ae81d284fa76908bb679bf04f9d1a7c425ec748ad7162652b10232107-primary.sqlite.bz2 failed validation due to checksum.
Could not lookup a publication_href for repo 8238

Satellite og Capsule version 6.10.7
Comment 11 Daniel Alley 2022-08-22 13:16:21 UTC 
Georgios,

>> A file located at the url https://xxxxx/pulp/content/content/dist/rhel8/8/x86_64/baseos/os/repodata/323df47ae81d284fa76908bb679bf04f9d1a7c425ec748ad7162652b10232107-primary.sqlite.bz2 failed validation due to checksum.
Could not lookup a publication_href for repo 8238

Being a metadata file, the root cause for this cannot be the same as the likely root cause for the initially reported issue - if this is a consistent error, the most probable explanation I can think of is that this specific file is corrupted on disk.  I would suggest working with a support tech to test whether this is the case or if there is a bug.
Comment 13 Daniel Alley 2022-08-25 16:21:31 UTC 
I'm closing this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2103522

The problem is the same but the visible impacts are different due to the capsules having different versions of 6.10.  The capsules in this case are 6.10.3 which, instead of yielding a hard error when they hit this, yield a soft and somewhat confusing error message.  Otherwise the root cause is the same - Satellite published a repo with multiple RPMs sharing the same name-epoch-version-release-architecture combination.

*** This bug has been marked as a duplicate of bug 2103522 ***
Comment 14 Georgios Atsigkioz 2022-09-29 06:41:04 UTC 
Following the bug 2103522.
Comment 15 Red Hat Bugzilla 2023-09-18 04:38:49 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.