Skip to content
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

Closed
pedroresende opened this issue Feb 4, 2016 · 9 comments
Closed

Error: Could not find a suitable provider for ldap_entry #70

pedroresende opened this issue Feb 4, 2016 · 9 comments
Labels

Comments

@pedroresende
Copy link

I have the following configuration

class { 'ldap::server':
  suffix  => 'dc=piu,dc=de',
  rootdn  => 'cn=admin,dc=piu,dc=de',
  rootpw  => '{MD5}FLasFExRTZnaVKq2ALMPAA==',
}

class { 'ldap::client':
  uri  => 'ldap://127.0.0.1',
  base => 'dc=piu,dc=de',
}

ldap_entry { 'cn=groups,dc=piu,dc=de':
  ensure      => present,
  base        => 'dc=piu,dc=de',
  host        => 'ldap://127.0.0.1',
  username    => 'cn=test,cn=groups,dc=piu,dc=de',
  password    => '{MD5}FLasFExRTZnaVKq2ALMPAA==',
}
@mattj-io
Copy link

mattj-io commented Feb 4, 2016

That's not a configuration problem, your puppet master doesn't know about the provider. Is the module installed correctly ?

@pedroresende
Copy link
Author

@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.
Apparently the part of the server and client it's working, the only problem is when I try to add a new ldap_entry.
Is there a way to call the ldap_entry from inside the class declaration ?

@mattj-io
Copy link

mattj-io commented Feb 4, 2016

Types and providers should just work in that configuration. Do other custom providers and types work ?

@pedroresende
Copy link
Author

The one that are generated by puphpnet work correctly

@mattj-io
Copy link

mattj-io commented Feb 4, 2016

I've never used puphpnet, so no idea how that's supposed to work I'm afraid.

@jwgmeligmeyling
Copy link

Same issue here, not using puphpnet, just puppet + librarian + vagrant.

@spjmurray
Copy link
Contributor

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.

@spjmurray spjmurray added the bug label Feb 23, 2016
@jwgmeligmeyling
Copy link

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?

@spjmurray
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants