Details
Major
Description
I'm having the same issue as Bug #16958 (reported in vcsrepo 0.1.0) which was a dupplicate of #6403 which was solved in vcsrepo 0.1.1. Apparently the issue came back in vcsrepo 0.1.2...:
warning: Found multiple default providers for vcsrepo: git, svn, cvs, hg, bzr; using git
Issue Links
- is duplicated by
-
MODULES-835
Multiple default providers
-
- Closed
-
-
MODULES-1290
Warning: Found multiple default providers for vcsrepo: cvs, dummy, svn, git; using cvs
-
- Closed
-
- clones
- links to
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Explorer
I'm also using 0.2.0 and that solved the problem for me. (We're still on Puppet 2.7.x) I suggest this issue can be closed.
Luitzen van Gorkum
added a comment - I'm also using 0.2.0 and that solved the problem for me. (We're still on Puppet 2.7.x) I suggest this issue can be closed. Problem is not reproducible on current version.
Miguel Di Ciurcio Filho
added a comment - Problem is not reproducible on current version. Problem apparent in Puppet 3.5.0 with and vcsrepo 0.2.0
Robert Zotter
added a comment - Problem apparent in Puppet 3.5.0 with and vcsrepo 0.2.0 puppetlabs/vcsrepo version '0.2.0'
puppetversion => 3.5.1
Issue exists for above versions.
|
/vcsrepo/lib/puppet/provider/vcsrepo/dummy.rb |
defaultfor :vcsrepo => :dummy
|
As far as I can tell, the above defaultfor can never match as there is no fact called 'vcsrepo'.
puppet/provider.rb seems to indicate you can trigger defaltfor based on a feature instead of a fact, but my ruby is only slightly beyond 'hello world', so I can't make sense of how to trigger it.
As a proof and a cludge work around, adding the 'vcsrepo' fact = 'dummy' resolves the warning.
|
/vcsrepo/lib/facter/vcsrepo.rb |
Facter.add('vcsrepo') do
|
setcode do
|
"dummy"
|
end
|
end
|
Richard Clark
added a comment - - edited puppetlabs/vcsrepo version '0.2.0'
puppetversion => 3.5.1
Issue exists for above versions.
/vcsrepo/lib/puppet/provider/vcsrepo/dummy.rb
defaultfor :vcsrepo => :dummy
As far as I can tell, the above defaultfor can never match as there is no fact called 'vcsrepo'.
puppet/provider.rb seems to indicate you can trigger defaltfor based on a feature instead of a fact, but my ruby is only slightly beyond 'hello world', so I can't make sense of how to trigger it.
As a proof and a cludge work around, adding the 'vcsrepo' fact = 'dummy' resolves the warning.
/vcsrepo/lib/facter/vcsrepo.rb
Facter.add('vcsrepo') do
setcode do
"dummy"
end
end
i can confirm, this bug exist with vcrepo 0.2.0 and puppet 3.5.1. Thanks Richard for your workaround 
Guillaume PAncak
added a comment - i can confirm, this bug exist with vcrepo 0.2.0 and puppet 3.5.1. Thanks Richard for your workaround I've just used Richard's workaround as well.
Bill Weiss
added a comment - I've just used Richard's workaround as well. yeah I can confirm that with vcsrepo 0.2.0, we didn't see this until we upgraded from puppet 3.4.1 to 3.6.1
Jason Antman
added a comment - yeah I can confirm that with vcsrepo 0.2.0, we didn't see this until we upgraded from puppet 3.4.1 to 3.6.1 Still happens with vcsrepo 1.0.x, unfortunately. Added this info in 'Environment' field.
Gert van Dijk
added a comment - Still happens with vcsrepo 1.0.x, unfortunately. Added this info in 'Environment' field. I'm also seeing this with puppet 3.5.1 and vcsrepo 1.0.2.
Bryan Østergaard
added a comment - I'm also seeing this with puppet 3.5.1 and vcsrepo 1.0.2. I am seeing this on Puppet 3.6.2 and vcsrepo 1.1.0
GeneBean
added a comment - I am seeing this on Puppet 3.6.2 and vcsrepo 1.1.0 PR for fixing this warning: https://github.com/puppetlabs/puppetlabs-vcsrepo/pull/209
Hunter (Hunner) Haugen
added a comment - PR for fixing this warning: https://github.com/puppetlabs/puppetlabs-vcsrepo/pull/209 
I can't reproduce this problem using vcsrepo 0.2.0 and Puppet 3.4.2.