toll13445
2010-Sep-02 16:28 UTC
[Puppet Users] err: Could not run Puppet configuration client: Invalid parameter stage at ...
Hi, I am getting the following error on my CentOS clients; err: Could not run Puppet configuration client: Invalid parameter stage at /etc/puppet/manifests/nodes.pp:32 The server is CentOS 5.4 with packages from the epel-puppet repos; # rpm -qa | grep puppet puppet-dashboard-1.0.3-3 puppet-2.6.1-0.3.rc3.el5 puppet-server-2.6.1-0.3.rc3.el5 The clients are; # rpm -qa | grep puppet puppet-0.25.5-1.el5 and my code to bootstrap the puppet install in nodes.pp looks like this; node default { include puppet if versioncmp($puppetversion, ''2.6.0'') < 0 { case $operatingsystem { CentOS: { notice(''In the centos cases'') file { "/etc/puppet/puppet.conf": owner => root, group => root, mode => 644, source => "puppet:///bpcommon/basenode/etc/puppet/puppet- centos.conf", **line 32 } } debian: { file { "/etc/puppet/puppet.conf": owner => root, group => root, mode => 644, source => "puppet:///bpcommon/basenode/etc/puppet/ puppet.deb.conf", } } } } } any suggestions what the error is about, I am guessing that the server is providing a stage parameter which the client is rejecting. but I was under the impression the server should work with older clients.. Any Suggesions? -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
toll13445
2010-Sep-02 21:56 UTC
[Puppet Users] Re: err: Could not run Puppet configuration client: Invalid parameter stage at ...
here is the output from a client that was previously working; # puppetd --test --debug debug: Creating default schedules debug: Failed to load library ''ldap'' for feature ''ldap'' debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/certs/cirrusj1626.hpl.hp.com.pem]: Autorequiring File[/var/ lib/puppet/ssl/certs] debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/ puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl] debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/public_keys/cirrusj1626.hpl.hp.com.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/ state] debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/etc/ puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/ certs] debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/ puppet/state]: Autorequiring File[/var/lib/puppet] debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/private_keys/cirrusj1626.hpl.hp.com.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/ lib/puppet/classes.txt]: Autorequiring File[/var/lib/puppet] debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/ puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/ puppet/ssl/csr_cirrusj1626.hpl.hp.com.pem]: Autorequiring File[/var/ lib/puppet/ssl] debug: Finishing transaction 70100229842160 with 0 changes debug: Loaded state in 0.00 seconds debug: Retrieved facts in 0.30 seconds debug: Retrieving catalog debug: Calling puppetmaster.getconfig debug: Retrieved catalog in 0.35 seconds debug: Puppet::Network::Client::File: defining fileserver.describe debug: Puppet::Network::Client::File: defining fileserver.list debug: Puppet::Network::Client::File: defining fileserver.retrieve debug: /File[/etc/puppet/puppet.conf]: {:stage=>:main} err: Could not create /etc/puppet/puppet.conf: Class file does not accept argument(s) stage at /etc/puppet/manifests/nodes.pp:41 warning: Not using cache on failed catalog warning: Configuration could not be instantiated: Class file does not accept argument(s) stage at /etc/puppet/manifests/nodes.pp:41 node default { include puppet if versioncmp($puppetversion, ''2.6.0'') < 0 { case $operatingsystem { redhat: { file { "/etc/puppet/puppet.conf": owner => root, group => root, mode => 644, source => "puppet:///bpcommon/basenode/etc/puppet/puppet.conf", } } CentOS: { notice(''In the centos cases'') file { "/etc/puppet/puppet.conf": owner => root, group => root, mode => 644, source => "puppet:///bpcommon/basenode/etc/puppet/puppet- centos.conf", } } debian: { file { "/etc/puppet/puppet.conf": owner => root, group => root, mode => 644, source => "puppet:///bpcommon/basenode/etc/puppet/ puppet.deb.conf", } } } } if versioncmp($puppetversion, ''2.6.0'') >= 0 { case $operatingsystem { redhat: { err(''something is pulling the redhat version 2.6.0 config, quick go write a config!!'') } debian: { file { "/etc/puppet/puppet.conf": owner => root, group => root, mode => 644, source => "puppet:///bpcommon/basenode/etc/puppet/puppet-2.6.0- deb.conf", } file { "/etc/default/puppet": owner => root, group => root, mode => 644, source => "puppet:///bpcommon/basenode/etc/default/puppet- deb-2.6", } } } } } -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
James Turnbull
2010-Sep-02 22:17 UTC
Re: [Puppet Users] Re: err: Could not run Puppet configuration client: Invalid parameter stage at ...
We''re taking a look at this and the "nested" stages issue currently. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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 puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Possibly Parallel Threads
- client not getting updates no error message
- $concat_basedir not defined
- err: Could not call list: header too long
- err: Could not run Puppet configuration client: execution expired
- Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'