search for: modulepaths

...d on the client and specify the environment as "prod" or "test", it will find the correct manifest file but it does not pick up any of the modules. If set modulepath in the "main"section like this, so that the module path is set to one of the environment''s modulepaths: [main] environment = prod environments=prod,test modulepath = /base/prod/modules [prod] modulepath = /base/prod/modules manifest = /base/prod/site.pp [test] modulepath = /base/test/modules manifest = /base/test/site.pp then puppetd on the...

So I''m trying to get multiple environments to work with puppet 0.25.1 on ubuntu 8.04 and no matter what I do, puppet just completely ignores any environment setting. There''s really next to no information in terms of configuration on the multiple environments documentation page (http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments) other than saying that the

Question... for those that have multiple environments, dev, prod etc... do you share your modules directory, or does each environment have it''s own copy of the modules directory? Which one has worked better? Doug -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

I''m running puppet in a local VM to do some testing, and all of our systems are behind a proxy. I''ve got the http_proxy environment variable set properly, but when I try to use puppet module install <foo> it doesn''t seem to honor it and can''t connect. I used wget to download it, but even when I use modulepath it still tries to connect to the forge and

Hi List, I'm currently setting up an openldap server and included the following lines in my slapd.conf : modulepath /usr/lib/ldap moduleload back_hdb after finishing up my config and i run slaptest on it i get an error saying that the modulepath doesn't exist. I checked and it indeed isn't there , in fact i can find it anywhere on my system (centos 5.7). the packages i've

If I externalise my Puppet module config to a directory outside of Puppet using the modulepath / manifestdir settings: [main] pluginsync=true modulepath=/home/ec2-user/projects/qmg-puppet/etc/puppet/modules manifestdir=/home/ec2-user/projects/qmg-puppet/etc/puppet/ manifests the agents log the following error: "Could not evaluate: Could not retrieve information from source(s)

Hi, I am running puppet version 0.25.1 on both the server and client and am getting the following error on a puppet run: err: Could not apply complete catalog: Could not retrieve dependency ''Class[http]'' of Class[puppet::http] Class http is defined in the "http" module like so: class http { package { httpd: ensure => installed } file {

Hi, Puppet 3.1 now uses YARD to generate its API documentation. Is anybody aware of the possibility to generate nice YARD docs for a given module path, replacing the default RDOC-style site from "puppet doc --modulepath ..."? Could the YARD Template from Puppet 3.1 be used for this? -- You received this message because you are subscribed to the Google Groups "Puppet Users"

I also made the changes below in the puppet.conf file to tell puppet where to look for the the modules and manifests. I then restart the puppet master then ran puppet command to apply changes to a puppet client it did not find anything to change just got these three lines "info: Caching catalog for pdlnx-adpt03.kareoprod.ent, info: Applying configuration version

My understanding was that at the beginning of each run the puppetmaster imports all modules so that any includes at the top level are applied directly. However, I am not so sure anymore. I''ve been tracing how this works and it seems like modules are included more lazily. In other words, when able_to_import is called seems like when the magic happens, rather than up front when the run

Greetings all Am trying to solve a problem, not entirely sure I''m approaching it from the right angle. Setting up a reasonably big site (servercount in the four digits) with puppetmaster and clients (puppet 2.6.x). We are required to have versioned modules (base SOE module, app X module, app Y module, etc - all with multiple classes etc inside) managed on an underlying SVN repository. A

Hi, When I execute *puppet agent --test --debug --verbose* on the target host, I receive the following error message: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pe_accounts for targethost on node targethost warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run I enabled debugging for the Puppet Master, and

Hello, I''m writing my first puppet function rspec test and am having a problem which I don''t see how to solve. The function (and the test) involve access to files through the File Server. In order for the function (and the test) to work I need to pass "--fileserverconf=fileserver.conf" parameter to Puppet. So far I haven''t found a way to do that. If I

Hi, We are using pxelinux at my company to test our product. And there are limitations that we have hit in the past w.r.t. the max length of a path, or the max length of a module name (in mboot.c / mboot.c32). We've used workarounds in the past, and reorganized the directory structure, but we face that problem again. Out of the 128 / FILENAME_MAX chars that can be used, 110 - 120 go to the

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hi all We''ve just released version 0.3.4 of the puppet-module tool used to create and retrieve modules from the Puppet Labs Forge (http://forge.puppetlabs.com). You can update using Ruby gems: $ gem install puppet-module There are several important changes in this release: * Add ability to install modules with hyphens * Add check for symlink when installing * Install modules to their

Hello All, Moving from 2.5 to 2.6.2 and I was wondering if there is a preferred directory structure for using multiple environments? Does it work much different in 2.6 than in 2.5? When I made the move I assumed (I know) that my current structure and configurations would just roll over but that isn''t the case. Thanks, Jim -- You received this message because you are subscribed to the

Hi, I''ve got some problems with setting up environments. On the master: [main] [...] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [...] environments = production,staging [production] manifestdir = /etc/puppet/manifests modulepath = /etc/puppet/modules [staging] manifestdir = /opt/puppet-staging/manifests modulepath = /opt/puppet-staging/modules [puppetmasterd]

Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet

I want to install a module into the modulepath. I can provide either a http url to a tar that contains the modules (like puppetforge but the path is not as structured) or I could provide a git url and path under that url where the module is. I want to first run puppet standalone on the vagrant vm host. This should download the appropriate modules and make them available on the filesystem