-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Could not find a suitable provider for ldap_entry #70
Comments
That's not a configuration problem, your puppet master doesn't know about the provider. Is the module installed correctly ? |
@dc-mattj I'm trying to use it directly in a puphpet vagrant generated. I've downloaded the release and exported it to puppet/modules folder. |
Types and providers should just work in that configuration. Do other custom providers and types work ? |
The one that are generated by puphpnet work correctly |
I've never used puphpnet, so no idea how that's supposed to work I'm afraid. |
Same issue here, not using puphpnet, just puppet + librarian + vagrant. |
I take it you are all running puppet 4? This appears to be the secret sauce that's not been mentioned. I shall re-architect and get a fix out asap. |
I am on Puppet 3.x.x as I couldn't get 4.x.x to work with Vagrant:hashicorp/vagrant#5615 . Still have to look in that issue. Is this package not supported on puppet 3? |
Interesting, I've just run the above manifest on 3.8.5 fine, but it fails on 4.3.2. Either way it's flaking out due to the provider being confined to systems with the net_ldap feature. I'll fix that up/amend the documentation and add beaker acceptance testing for puppet 3.x and 4.x on centos 7 and ubuntu 14.04. |
I have the following configuration
The text was updated successfully, but these errors were encountered: