similar to: Environments; function error

I started getting the following errors from my puppet master: > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider at /some/module/manifests/foo.pp The module would vary, but the error was always the same. I started googling, searching lists, etc. And turned up a whole bucket load of issues that all seem related and are all unresolved:

Hi List, Puppet Version: v2.7.13 Question - If I correctly setup multiple manifestdir''s in the puppet.conf file how can I import a node pp file located in a different directory tree to site.pp? My configuration information is below. In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and

I would like to use additional puppet environment for "fast response" configuration and run it every minute. For that I''ve created new light environment with only one module. But I don''t know how to configure puppet master manifests for one node with two environments? Is it possible? I''ve found a manual

I''ve setup dynamic environments using git but I''m confused about how environments are actually supposed to be used. We''re a small ISP and have freeradius servers, VPN servers and web servers. I''ve been using environments to enable me as the sysadmin to build and test new manifests/modules before deploying them to our production servers. I have dedicated

Hey there, I''m new to hiera and I'' m looking to configure it to use multiple environments. I''m able to query hiera keys from using the hiera CLI, however my clients seem to be having problems identifying the look up variables. *On the puppet master, CLI query* [root@puppet-dev puppet]# hiera -a sshpackages environment=development ["openssh",

Hi all, I think i''m forgetting something. If i do: "puppet apply manifiests/site.pp" it works perfectly, loading modules i have include in site.pp file. site.pp: cat manifiests/site.pp node default { include ntp, motd } But it does not work if i run puppet agent. puppet agent --test --server=debianita.user.arinso --environment production Info: Retrieving plugin Info:

Hi Guys, Im trying to turn on storeconfigs with a mysql db backend. On my testing server in our lab, i configured this successfully and can see if keeping information on all test hosts. When trying to implent the same idea onto our production puppet server, I get the following errors: Aug 26 16:35:53 opsynxsr0097 puppetmasterd[27003]: (/Settings[/etc/

I have a node that has some bad stored configs (namely the wrong ssh host keys) that I''m trying to clear out. Looking around it seems I''m supposed to do: puppet node clean foo.example.com However, that keeps bailing out because it''s trying to open a SQLite3 db where stored configs are normally kept, but my stored configs are kept in puppetdb (http://pastie.org/7814483

Hi all, We are currently using the regsubst function of Puppet to generate some information out of our hostnames (customer, environment, and so.). The manifest is running fine since months. 7: $customer = regsubst($::fqdn, ''(^[^-]*)-[^-]*.*'', "\\1") 8: $environment = regsubst($::fqdn, ''^[^-]*-([^-]*).*'', "\\1") 9: $product =

Hiera was properly working in my environment. But puppet was looking at old version even when I have the latest hiera gem installed. So I could''nt use json backend. But puppet is not looking at my latest hiera gem. Not sure when went wrong here. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0

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]

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

Good evening, folks. Using the module''s puppet forge to create a database I get an error below. Could you help me? *puppetlabs-mysql (v1.0.0) * *class mysql_default {* * * * mysql::db { ''mydb'':* * user => ''root'',* * password => ''123456'',* * host => ''localhost'',* * grant

I''ve created cloudstack_resources as a module, have setup the transport.yaml and can successfully run "puppet resource cloudstack_instance" against my cloudstack environment. The following cloudstack_instance files have been created /var/lib/puppet/lib/puppet/provider/cloudstack_instance /var/lib/puppet/lib/puppet/provider/cloudstack_instance/default.rb

I''m running a previously working set of modules with the Puppet master version 3.1.0-rc2. I''m getting the Error: stack level too deep Here is a chunk of the debug Debug: Scope(Class[Zabbix]): Retrieving template zabbix/zabbix.conf.php.erb Debug: template[/etc/puppet/environments/production/modules/zabbix/templates/zabbix.conf.php.erb]: Bound template variables for

Hi all, I am new to Puppet and now I do some test with 2 Virtual Machines running Centos 6.4 and puppet 3.3.1 And I manage to sign the client cert, but still I can not get any file updated on the client VM. If I run the client in test mode puppet agent --server=p-master.localdomain --noop --test There is no errors in the output. Info: Retrieving plugin Info: Caching catalog for

I am trying out having multiple environments so that I can push a test config to a single server in production. The idea being that I could push out a config change to one server and see if the change works in production. If it does then I can merge the change into the production environment and push the change out to all the clients. So to test this I made a change to a config file in testing

We are in the process of evaluating our puppet related test and release process and interested in knowing what other folks are doing. We are in a position that is not ideal but is not unique from what I can tell. Our current testing process is basically the responsibility of each person making a change. Small changes are committed and pushed to dev/qa/prod in one swoop with the committer spot

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

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