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.

Bug 1953106

Summary:	[pulp3] content from non-sha256 'on_demand' repos is not available
Product:	Red Hat Satellite	Reporter:	Vladimír Sedmík <vsedmik>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	ggainey, jsherril, rchan, ttereshc, zhunting
Target Milestone:	6.9.2	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	pulpcore-3.7.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-20 18:05:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vladimír Sedmík 2021-04-23 21:55:33 UTC

Description of problem:
I tried to measure the sync time of ~100 particular repos with on-demand policy after migration+switchover (Satellite with pulp3) to an external Capsule (with pulp2 and immediate download policy). The sync task lasted 2x longer than for unmigrated setup and got lots of 404s. I also got 404 when tried to get some of the content to a host registered to the Satellite.


Version-Release number of selected component (if applicable):
6.9.1 snap 3


How reproducible:
2/2


Steps to Reproduce:
1. have a SAT with an external CAPS
2. sync 9 RH repos with on_demand download policy and publish each of them into 10 CVs
3. run the migration and switchover on the SAT
4. add the external capsule to the Library env and trigger the complete sync
(or ping me for the reproducer)


Actual results:
the task lasts too long and content is not synchronized properly

Comment 1 Tanya Tereshchenko 2021-04-24 15:41:24 UTC

The problem is with repositories which have content checksum type other than sha256.
It was introduced in 6.9.1 (pulpcore 3.7.5), 6.9.0 does not have this problem.

Comment 2 pulp-infra@redhat.com 2021-04-24 16:19:34 UTC

The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

Comment 3 pulp-infra@redhat.com 2021-04-24 16:19:35 UTC

The Pulp upstream bug priority is at Urgent. Updating the external tracker on this bug.

Comment 4 pulp-infra@redhat.com 2021-04-25 19:16:26 UTC

The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.

Comment 5 pulp-infra@redhat.com 2021-04-25 21:10:19 UTC

The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

Comment 6 pulp-infra@redhat.com 2021-04-26 19:16:32 UTC

The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 7 pulp-infra@redhat.com 2021-04-26 20:12:16 UTC

All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 8 Vladimír Sedmík 2021-05-07 18:40:24 UTC

Verified on 6.9.2 snap 2 (python3-pulpcore-3.7.6-1.el7pc.noarch)
I was able to sync the content from a pulp3 satellite to a pulp2 capsule and also install it on a registered host from the capsule. The scenario from comment#0 also passed without issues.

Using these particular repos:
https://fixtures.pulpproject.org/rpm-with-md5/
https://fixtures.pulpproject.org/rpm-with-sha-1-modular/
https://fixtures.pulpproject.org/rpm-with-sha-512/

I was able to reproduce the KeyError: 'name' issue, which is tracked separately by https://bugzilla.redhat.com/show_bug.cgi?id=1954839.

Comment 13 errata-xmlrpc 2021-05-20 18:05:30 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 (Satellite 6.9.2 Async Bug Fix Update), 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/RHBA-2021:2074

Comment 18 pulp-infra@redhat.com 2021-05-25 22:11:11 UTC

The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.