I am experiencing the behavior reported in another bug report (http://
projects.puppetlabs.com/issues/1006) in version 0.25.5, that is:
puppetrun --host xyz.def.com --class apache --debug --trace
gives this:
You must be using LDAP to specify host classes
My puppet.conf looks like this:
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
[puppetmasterd]
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
reports=log,foreman
node_terminus=ldap
ldapserver=192.168.1.214
ldapbase=ou=Hosts,dc=abc,dc=com
ldapuser=cn=admin,dc=abc,dc=com
ldappassword=secret
And a sample node entry like this:
dn: cn=xyz.def.com,ou=Hosts,dc=abc,dc=com
objectClass: device
objectClass: ipHost
objectClass: puppetClient
objectClass: top
cn: xyz.def.com
ipHostNumber: 192.168.1.158
puppetClass: dovecot
puppetClass: apache
puppetClass: imapproxy
environment: production
The above behavior is see only when mentioning a class explicitly,.
Without the —class argument, it works.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
