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.
DescriptionJustin Sherrill
2021-06-04 13:25:31 UTC
Description of problem:
If you try to kickstart against a pulp3 on_demand repo, anaconda will fail when it tries to download the rpm headers
Version-Release number of selected component (if applicable):
6.10
How reproducible:
always
Steps to Reproduce:
1. Sync a kickstart repo using on_demand (or use an on_demand capsule)
2. Try to kickstart a client using it
Actual results:
Failure, anaconda can't download the package headers
Expected results:
Success!
Additional info:
It looks like Range requests aren't be fulfilled properly in pulp with on_demand content.
Comment 1pulp-infra@redhat.com
2021-06-04 14:14:18 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 2pulp-infra@redhat.com
2021-06-04 14:14:19 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 3pulp-infra@redhat.com
2021-06-08 15:07:56 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2021-06-09 02:13:49 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2021-06-14 15:08:18 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2021-07-01 00:26:53 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2021-07-07 15:10:10 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 8pulp-infra@redhat.com
2021-07-08 16:16:04 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 9pulp-infra@redhat.com
2021-07-09 21:07:17 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 10pulp-infra@redhat.com
2021-07-09 22:07:33 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 12Tanya Tereshchenko
2021-07-23 13:45:17 UTC
Released in pulpcore 3.14.2
Comment 13pulp-infra@redhat.com
2021-07-23 14:07:24 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 14pulp-infra@redhat.com
2021-07-23 14:07:27 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
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.10 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-2021:4702