Project

General

Profile

Actions

Bug #13182

closed

Puppet repositories are not exposed via HTTP even with 'unprotected' flag set.

Added by Brad Buckingham over 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Repositories
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1032178
Description of problem:

As part of 1aa2292c20cf11bb2fcdf8a9006eb43719bd40c7 we switched from the PuppetDistributor to the PuppetInstallDistributor. This enabled us to deploy modules to a puppet master but makes it so they are not exposed over http.

We should add the PuppetDistributor back so that they are exposed.

Version-Release number of selected component (if applicable):
6.0.2

How reproducible:
Always

Steps to Reproduce:
1. Create a new puppet repository and check 'unprotected'
2. Either sync content from puppetforge or push content to it via katello cli
3. Visit the repository details page and look for the repo url
4. Click the repo url

Actual results:
404

Expected results:
Puppet repository is displayed/


Related issues 1 (0 open1 closed)

Related to Katello - Tracker #13186: Replacing Pulp NodesResolvedJohn Mitsch01/20/201601/20/2016

Actions
Actions #1

Updated by John Mitsch over 8 years ago

Actions #2

Updated by John Mitsch over 8 years ago

  • translation missing: en.field_release set to 86
Actions #3

Updated by The Foreman Bot about 8 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Brad Buckingham
  • Pull request https://github.com/Katello/katello/pull/5717 added
Actions #4

Updated by Brad Buckingham about 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #5

Updated by Bryan Kearney about 8 years ago

  • Category changed from Web UI to Repositories
Actions

Also available in: Atom PDF