Project

Profile

Help

Issue #680

closed

puppet repo publish with install_path set, installs to wrong directory

Added by jsherril@redhat.com about 9 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.5
Platform Release:
2.6.0
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Description of problem:

Publishing a puppet repo with an install path causes repo to be 'installed' to the wrong directory.

For example, given this distributor config:

{"repo_id"=>"Default_Organization-Library-puppet1comp", "_ns"=>"repo_distributors", "last_publish"=>"2015-01-27T14:08:31Z", "auto_publish"=>true, "scheduled_publishes"=>[], "distributor_type_id"=>"puppet_install_distributor", "_id"=>{"$oid"=>"54c79bdd5ca01357c0612249"}, "config"=>{"install_path"=>"/etc/puppet/environments/KT_Default_Organization_Library_puppet1comp_12/modules", "auto_publish"=>true}, "id"=>"Default_Organization-Library-puppet1comp"}

it gets published to:

/etc/puppet/environments/KT_Default_Organization_Library_puppet1comp_12/pulp1bKXUS/

Version-Release number of selected component (if applicable):
pulp-puppet-plugins-2.5.1-1.el6.noarch
pulp-server-2.5.1-1.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a puppet repo with an install_path set to some path: /etc/puppet/environments/foo/modules
2. Upload one or more puppet modules
3. Examine the install path to verify that the modules made it there

Actual results:
modules are not there, but are in one directory up in a randomly named directory.

Expected results:
puppet modules are deployed to /etc/puppet/environments/foo/module

+ This bug was cloned from Bugzilla Bug #1186445 +


Files

86c9f59f50b24ddf20664e5b423b68f2 (1.25 KB) 86c9f59f50b24ddf20664e5b423b68f2 jsherril@redhat.com, 03/01/2015 12:21 AM

Also available in: Atom PDF