Issue #4203 has been updated by Markus Roberts.
This appears to be a result of trying to use the ldap user provider without
having ldap configured properly (specifically, no --ldapuer option or config
item). It may also be a consequence of not having useradd visible to the user
puppet is running as, or explicitly (but unintentionally) specifying provider
=> ldap in the resource.
At worst, I think it's a badly worded / mostly useless error message, but I'm
not seeing how to improve it without refactoring the confiner system.
Did you get other messages at the same time that would have led you to the
conclusion above (and thus given the putative user a handle on fixing it) or
was this the only sign?
Also, were you trying to manage users or was this just puppet muttering to
itself during start up ("Hmph. Can't use ldap, there's no quaffing ldapuser in
the speckled config. Nudzh! How they expect me to do anything, I don't
know.")?
And finally, is this actually new in 2.6.x or does it happen in 0.25.x as well
(looking at the code, it appears that it should).
----------------------------------------
Bug #4203: debug: Puppet::Type::User::ProviderLdap: true value when expecting
false
http://projects.puppetlabs.com/issues/4203
Author: James Turnbull
Status: Needs more information
Priority: Normal
Assigned to: James Turnbull
Category: LDAP
Target version: 2.6.0
Affected version: 2.6.0rc1
Keywords:
Branch:
Not sure what this means but think it's not quite right...
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
