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
2016-09-22 15:29:19 UTC
Description of problem:
Kickstarting against a repo set to on demand for its download policy does not work. The kickstart will fail with:
error populating transaction after 10 retries: failure
Seems to work fine against an http:// repo. More details here: https://pulp.plan.io/issues/2276
Version-Release number of selected component (if applicable):
6.2.2 (pulp 2.8.7)
How reproducible:
always
Steps to Reproduce:
1. Create a repository pointing somewhere on the filesystem (file:///foo/bar) that contains a kickstart tree
2. Sync the repo
3. Try to kickstart against the tree
Actual results:
Failure
Expected results:
Success
Additional info:
Comment 2pulp-infra@redhat.com
2016-11-21 18:51:33 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 3pulp-infra@redhat.com
2016-11-21 18:51:36 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
TL;DR from the upstream bug: the design of on-demand content access requires HTTP, so this cannot be supported.
If things could fail more gracefully, please comment on the upstream bug with ideas.
Justin, it sounds like we'll only make these changes upstream:
- document the limitation
- enforce the limit with validation
I'm not sure Katello or Satellite should depend on either of those. It would probably be best for Katello to also enforce the limit with its own validation. Would you agree?
Given all that, I think there are probably no steps for Pulp to take that impact downstream, so this issue can be either closed, or converted to track a Katello validation change. What do you think?
Verifed on Sat 6.4 snap 7, a warning is displayed when attempting to create a repo with file:// url and on demand or background policy, same when editing the policy for existing file repo
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, 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-2018:2927