Bug 1378514

Summary: kickstart with 'on demand' repository using file:// repo does not work (error populating transaction)
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: RepositoriesAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: medium    
Version: 6.2.2CC: bbuckingham, cdonnell, dalley, dkliban, jcallaha, jortel, jsherril, ktordeur, mhrivnak, pcreech, rvdwees, ttereshc
Target Milestone: 6.4.0Keywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:20:04 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:

Description Justin 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 2 pulp-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 3 pulp-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.

Comment 4 Michael Hrivnak 2016-12-12 04:21:58 UTC
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.

Comment 5 Michael Hrivnak 2016-12-19 20:35:10 UTC
Jeff, check out the upstream issue and the questions there. Thanks!

Comment 6 Jeff Ortel 2017-01-05 19:43:23 UTC
Done.

Comment 7 Michael Hrivnak 2017-01-05 19:59:23 UTC
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?

Comment 8 Justin Sherrill 2017-01-05 20:04:16 UTC
Katello is made to handle pulp validation errors, but the messaging would be better if it were caught in katello.  So yes, i'd agree!

Comment 9 Michael Hrivnak 2017-01-06 16:43:13 UTC
Ok, thanks. I'll change the component, remove the pulp redmine issue, and let you katello folks ponder next steps.

Comment 10 Michael Hrivnak 2017-01-09 17:24:10 UTC
re-removing per discussion with @dkliban

Comment 14 pulp-infra@redhat.com 2017-09-07 12:22:51 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

Comment 15 pulp-infra@redhat.com 2017-09-07 12:22:55 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 16 Justin Sherrill 2018-03-05 14:11:05 UTC
Connecting redmine issue http://projects.theforeman.org/issues/22769 from this bug

Comment 17 Satellite Program 2018-03-07 03:17:07 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22769 has been resolved.

Comment 18 Tanya Tereshchenko 2018-03-07 06:40:00 UTC
BZ is resolved as per comment#17 and is no longer blocked on Pulp, thus removing the Pulp issue.

Comment 19 Peter Ondrejka 2018-06-20 11:56:32 UTC
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

Comment 20 Bryan Kearney 2018-10-16 19:20:04 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, 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