Try quoting your node names, e.g.
node 'ubuntu2.ttinet' {
--
Peter M. Bukowinski
Systems Engineer
Janelia Farm Research Campus, HHMI
On Tuesday, June 14, 2011 at 11:26 AM, Craig White wrote:
>
> On Jun 13, 2011, at 5:02 PM, Nan Liu wrote:
>
> > On Mon, Jun 13, 2011 at 4:19 PM, Craig White <craig.wh...@ttiltd.com
> > (mailto:craig.wh...@ttiltd.com)> wrote:
> > >
> > > On Jun 13, 2011, at 3:10 PM, Nan Liu wrote:
> > >
> > > > On Mon, Jun 13, 2011 at 1:57 PM, Craig White <craig.wh...@ttiltd.com
> > > > (mailto:craig.wh...@ttiltd.com)> wrote:
> > > > > I've gone over the documentation several times now and I can't figure
> > > > > out how to 'apply' a manifest to a client.
> > > > >
> > > > > The client does have a signed certificate but the only thing in the
> > > > > /etc/puppet folder on the client is an ssl directory.\
> > > >
> > > > If you are running puppet against a remote puppet master, you should
> > > > run puppet agent rather than puppet apply. puppet apply is only when
> > > > you have a copy of the manifest locally.
> > > >
> > > > > I have a manifest that works fine on the puppet 'master'
> > > > >
> > > > > I have added the client into /etc/puppet/manifests/nodes.pp
> >
> > Didn't notice this earlier, the default manifests file puppet master
> > compiles is /etc/puppet/manifests/site.pp, you need to import nodes.pp
> > in site.pp, or simply write the node information in site.pp manifest.
> >
> > > if the puppet agent command would have worked for me, I wouldn't have
> > > asked. My puppet master has manifests/nodes.pp which lists the client
> > > fqdn (matches the cert too) and it includes 'ntp' which is found in
> > > modules/ntp/manifests/ntp.pp (see my original e-mail) but it doesn't seem
> > > to happen no matter how many times I invoke the 'puppet agent command
> > > from the client system). The client system did however get a certificate
> > > from the server.
> >
> > If the suggestion above doesn't work, try to include a default node in
> > site.pp:
> > node default {
> > include ntp
> > }
> >
> > Beyond that, start running puppet master with the option
> > --no-daemonize --verbose (add --debug as necessary) and send any
> > applicable output. It should autoload classes in modules and compile
> > catalog for the taget node successfully (see sample below):
> ----
> still no joy ;-(
>
> # cat site.pp
> import "templates"
> import "nodes"
>
> # cat nodes.pp
> node ubuntu.ttinet {
> include ntp
> }
>
> node ubuntu2.ttinet {
> include ntp
> package { "apt":
> ensure => installed,
> }
> file{"/etc/apt/sources.list":
> ensure => present,
> owner => root,
> require => Package["apt"]
> }
> }
>
> # cat templates.pp
> class baseclass {
> }
>
> node default {
> include baseclass
> }
>
> root@ubuntu:/etc/puppet/manifests# puppet master --no-daemonize --verbose
> --debug
> debug: Failed to load library 'shadow' for feature 'libshadow'
> debug: Puppet::Type::User::ProviderUser_role_add: file roledel does not exist
> debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does
> not exist
> debug: Puppet::Type::User::ProviderLdap: true value when expecting false
> debug: Puppet::Type::User::ProviderPw: file pw does not exist
> debug: Failed to load library 'selinux' for feature 'selinux'
> debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
> microsoft_windows is missing
> debug: Failed to load library 'ldap' for feature 'ldap'
> debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/server_data]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/public_keys/ubuntu.ttinet.pem]: Autorequiring
> File[/etc/puppet/ssl/public_keys]
> debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/auth.conf]: Autorequiring File[/etc/puppet]
> debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/yaml]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/manifests]: Autorequiring File[/etc/puppet]
> debug: /File[/etc/puppet/ssl/private_keys/ubuntu.ttinet.pem]: Autorequiring
> File[/etc/puppet/ssl/private_keys]
> debug: /File[/etc/puppet/ssl/certs/ubuntu.ttinet.pem]: Autorequiring
> File[/etc/puppet/ssl/certs]
> debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/reports]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/bucket]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/manifests/site.pp]: Autorequiring
> File[/etc/puppet/manifests]
> debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
> debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/log/masterhttp.log]: Autorequiring
> File[/var/lib/puppet/log]
> debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
> File[/etc/puppet/ssl/certs]
> debug: /File[/var/lib/puppet/rrd]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
> File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
> File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/fileserver.conf]: Autorequiring File[/etc/puppet]
> debug: Finishing transaction 33589420
> debug: /File[/etc/puppet/ssl/ca/private/ca.pass]: Autorequiring
> File[/etc/puppet/ssl/ca/private]
> debug: /File[/etc/puppet/ssl/ca/ca_pub.pem]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: /File[/etc/puppet/ssl/ca/serial]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: /File[/etc/puppet/ssl/ca/ca_key.pem]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: /File[/etc/puppet/ssl/ca/signed]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: /File[/etc/puppet/ssl/ca/ca_crt.pem]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: /File[/etc/puppet/ssl/ca/ca_crl.pem]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: /File[/etc/puppet/ssl/ca/inventory.txt]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: /File[/etc/puppet/ssl/ca/requests]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: /File[/etc/puppet/ssl/ca/private]: Autorequiring
> File[/etc/puppet/ssl/ca]
> debug: Finishing transaction 32855280
> debug: Using cached certificate for ca
> debug: Using cached certificate for ca
> debug: Using cached certificate for ubuntu.ttinet
> notice: Starting Puppet master version 2.6.8
> debug: Finishing transaction 31427660
> info: mount[files]: allowing 10.0.0.0/8 access
> debug: No modules mount given; autocreating with default permissions
> debug: No path given for plugins mount; creating a special PluginMount
> info: access[^/catalog/([^/]+)$]: allowing 'method' find
> info: access[^/catalog/([^/]+)$]: allowing $1 access
> info: access[/certificate_revocation_list/ca]: allowing 'method' find
> info: access[/certificate_revocation_list/ca]: allowing * access
> info: access[/report]: allowing 'method' save
> info: access[/report]: allowing * access
> info: access[/file]: allowing * access
> info: access[/certificate/ca]: adding authentication no
> info: access[/certificate/ca]: allowing 'method' find
> info: access[/certificate/ca]: allowing * access
> info: access[/certificate/]: adding authentication no
> info: access[/certificate/]: allowing 'method' find
> info: access[/certificate/]: allowing * access
> info: access[/certificate_request]: adding authentication no
> info: access[/certificate_request]: allowing 'method' find
> info: access[/certificate_request]: allowing 'method' save
> info: access[/certificate_request]: allowing * access
> info: access[/]: adding authentication any
> info: Inserting default '/status'(auth) ACL because none were found in
> '/etc/puppet/auth.conf'
> info: Expiring the node cache of ubuntu2.ttinet
> info: Not using expired node for ubuntu2.ttinet from cache; expired at Tue
> Jun 14 08:16:51 -0700 2011
> info: Caching node for ubuntu2.ttinet
> debug: importing '/etc/puppet/manifests/templates.pp' in environment
> production
> debug: importing '/etc/puppet/manifests/nodes.pp' in environment production
> err: Could not parse for environment production: Syntax error at '.' at
> /etc/puppet/manifests/nodes.pp:1 on node ubuntu2.ttinet
> err: Could not parse for environment production: Syntax error at '.' at
> /etc/puppet/manifests/nodes.pp:1 on node ubuntu2.ttinet
>
> --
> 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
> (mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com
> (mailto:puppet-users+unsubscr...@googlegroups.com).
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
