Project

General

Profile

Actions

Bug #1587

closed

Puppet's modulepath not interpreted correctly by proxy

Added by Josh Baird over 12 years ago. Updated over 12 years ago.

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

Description

Running foreman-proxy-0.3.3-0.1.noarch, installed on the PM.

My puppet.conf defines environments like:

[prod]
modulepath = /etc/puppetlabs/puppet/env/prod/modules:/etc/puppetlabs/puppet/env/common/modules:/opt/puppet/share/puppet/modules
manifest = /etc/puppetlabs/puppet/manifests/site.pp
pluginsync = true

When I query the proxy for classes in the "prod" environment, I see:

[root@fc-wrpupem01 manifests]# wget -q -O - http://localhost:8443/puppet/environments/prod {"paths":"/etc/puppetlabs/puppet/env/prod/modules/etc/puppetlabs/puppet/env/common/modules/opt/puppet/share/puppet/modules","name":"prod"}[root@fc-wrpupem01 manifests]#

It would appear that proxy is ignoring the delimiters (":") and concatenating the entire string.

Actions #1

Updated by Ohad Levy over 12 years ago

  • Category set to Puppet
  • Assignee set to Ohad Levy
  • Target version set to 1.0
Actions #2

Updated by Ohad Levy over 12 years ago

  • Status changed from New to Closed

fixed at 083405c8

Actions

Also available in: Atom PDF