similar to: Invalid resource type anchor.

I''ve installed the puppet labs lvm module. After fixing the missing "}" at line 20 in init.pp (really?!?!), I''m getting this:'' err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type physical_volume at /truth/sauce/env/prod/modules/role/manifests/common.pp:43

Hi, I have a fresh CentOS 5.8 Vagrant VM that I''m using to emulate a customer''s server. During the first Puppet run, it takes 13 minutes and 48 seconds to sync the Puppet Labs stdlib module. On a similar Ubuntu 12.04.1 Vagrant VM, Puppet starts up, and almost instantly goes from plugin sync to facter load. Is this load time for stdlib on a RHEL variant normal?

I am running puppet 3.1.1 and have a site.pp which roughly looks like this site.pp: node basenode { include common } node ''server1'' inherits basenode { include role::appserver } node ''server2'' inherits basenode { include role::webserver } And my common module includes lots of different types of classes for creating base directories, adding in

My issue may be related to this bug: http://projects.puppetlabs.com/issues/13858 "Custom types in environments require loading into master''s libdir" However, now I''m not so sure, This was working previously with a given client. However, after trying on a fresh client, it''s failing with: err: Could not run Puppet configuration client: Could not find a

Hello, I''m encountering an issue which I think is a bug, but I want to propose it here before filing it for good @puppetlabs, and be sure it''s not just a misunderstanding. Actually, I often use a construction where a "main" class would include some small others that build a complete service (install, config, service ) Relationship are given (and respected) in the main

I am trying to get a custom fact to sync. The fact is in a module. It will sync if I run puppet with "--pluginsync" but not otherwise. I have "pluginsync=true" in my puppet.conf. Shouldn''t the command line option and puppet.conf option have the same results? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group.

I''ve upgraded to puppet v2.6.2 on ubuntu (clients and server) and now I get this error messages related to pluginsync: info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate'': wrong header line format err: /File[/var/lib/puppet/lib]: Could not evaluate: wrong header line format Could not retrieve file

I am trying to figure out if I am missing something simple here. After upgrading to puppet 3.0 running puppet-rspec tests that use custom resources from modules in the fixtures directory are failing. I have a module that uses the anchor type and with 2.7.19 it works fine. After upgrading to 3.0 all of the tests are failing with Puppet::Error: Puppet::Parser::AST::Resource failed with

I have written a custom puppet fact using a ruby script. It is very simple - it just adds a string to a fact. However I have written a module but it appears to me that the custom fact has been applied to all my machines without me specifying any node definitions. When I run a puppet agent --test --noop, I see the custom fact appear in /var/lib/puppet/lib/facter. Info: Loading facts in

Is it normal that "facter --puppet" does not show the environment variable? is there a way to have it include it? Thanks a lot, Mohamed. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to

New install of 2.5.1 on Ubuntu 10.10 server. Multiple (6) new installs on Ubuntu 12.04 clients running agent 2.7.14-1puppetlabs1 from the puppetlabs repo generating the following error. err: Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param ‘undef’ at /opt/puppet/share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node

How can I pass an array to a define? It''s not documented in the puppet language guide. I''ve got: define lvm::create_vg ( $pvdisks ) { exec { ''pvcreate'': command => "/sbin/pvcreate -yf $pvdisks", unless => "/sbin/pvdisplay $pvdisks", ... } } class someclass { lvm::create_vg {

Hello, I''ve mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2 setup from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML. Now I''ve create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/ customer_status.rb. On the client; Running facter customer_status works. Running ''puppet agent --test'' works, customer_status

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 =

So we run puppetd as a long running ruby process on the hosts. When we update a fact that gets auto sync''d to the host it seems when puppetd wakes up and starts its catalog run it doesn''t re-sync the facts. It you run it standalone it will or if you restart the service then it will do the right thing. Do other people see this? Or have you all gone to running out of cron?

HI all, I''m trying to demo the puppetlabs-openstack module following the the simple example, but not getting very far. the puppetlabs-keystone module is presenting a weird failure state claiming: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type keystone_tenant at

Does anyone have any insight into this error message? err: Could not retrieve catalog from remote server: Error 400 on SERVER: The fact named fact_stomp_server does not appear to be a valid hostname. The value of '''' does not match ''^[a-zA-Z0-9.-]+$''. A common cause of this problem is running puppet agent as a normal user instead of root, or the fact is

I am finding that the puppetlabs-apache module is somehow adding 30-60 seconds onto a host''s catalog compile time when the puppetmaster has no other hosts contacting or generating catalogs. The Puppetmaster is setup to use Puppet-2.7.18 - Apache & Passenger. RIght now only 2 hosts are even configured to use this new PM, the PM itself and a Foreman host. With neither hosts

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

I have been working on adding some predicate functions to puppetlabs-stdlib that test things based on ''interfaces'' and related facts. The functions themselves seem to work fine in my manifest-based smoketests, but I am running into trouble that may or may not be due to my ignorance about rspec or Facter. Something needs to be done to initialize Facter because