Project

General

Profile

Actions

Bug #2738

closed

smart-proxy for puppet not picking up whole module path

Added by David Blank-Edelman over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Smart Proxy
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Using 1.2 of foreman-proxy package from the Ubuntu precise repo, I find that the smart proxy isn't picking up my whole modulepath and hence classes importing is problematic.

The proxy config says:

:puppet: true
:puppet_conf: /etc/puppet/puppet.conf

The relevant parts of /etc/pupet/puppet.conf say:

[main]
    confdir = /etc/puppet-master-conf/master-conf
...
[master]
    environment = production
    manifest = $confdir/environments/$environment/manifests/site.pp
    modulepath = $confdir/environments/$environment/modules:$confdir/environments/$environment/service

But when I talk to my proxy, I see:

$ curl proxy:8443/puppet/environments
["master","msimmons","production","dnb","cmccoy"]

$ curl proxy:8443/puppet/environments/dnb
{"name":"dnb","paths":["/etc/puppet-master-conf/master-conf/environments/dnb/services"]}

when indeed the $confdir/environments/$environment/module path is there and is readable by
the proxy user:

# sudo -u foreman-proxy ls -l /etc/puppet-master-conf/master-conf/environments/dnb/modules

drwxrwxr-x 7 puppet puppet 4096 Jun 28 16:20 activemq
drwxrwxr-x 5 puppet puppet 4096 Jun 28 16:20 apt
drwxrwxr-x 4 puppet puppet 4096 Jun 28 16:20 autofs
...

Any help you can offer would be much appreciated.


Related issues 1 (0 open1 closed)

Has duplicate Smart Proxy - Bug #2768: importing classes partially fails when dynamic modulepath has multiple entriesRejected07/10/2013Actions
Actions

Also available in: Atom PDF