Uploaded image for project: 'Forge Modules'
  1. Forge Modules
  2. MODULES-428

vcsrepo 0.1.2: Multiple default providers

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: vcsrepo
    • Labels:
    • Environment:

      Puppet 3.5+, 3.6+ with vcsrepo 0.1.2, 0.2.0, 1.0.0, 1.0.1, 1.1.0.

    • Template:
    • Story Points:
      2
    • Sprint:
      MODS 2014-09-17

      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

          Activity

          Hide
          miguel Miguel Di Ciurcio Filho added a comment - - edited

          I can't reproduce this problem using vcsrepo 0.2.0 and Puppet 3.4.2.

          Show
          miguel Miguel Di Ciurcio Filho added a comment - - edited I can't reproduce this problem using vcsrepo 0.2.0 and Puppet 3.4.2.
          Hide
          lvg 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.

          Show
          lvg 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.
          Hide
          miguel Miguel Di Ciurcio Filho added a comment -

          Problem is not reproducible on current version.

          Show
          miguel Miguel Di Ciurcio Filho added a comment - Problem is not reproducible on current version.
          Hide
          rzotter Robert Zotter added a comment -

          Problem apparent in Puppet 3.5.0 with and vcsrepo 0.2.0

          Show
          rzotter Robert Zotter added a comment - Problem apparent in Puppet 3.5.0 with and vcsrepo 0.2.0
          Hide
          smegthelight 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
          

          Show
          smegthelight 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
          Hide
          gpkfr 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

          Show
          gpkfr 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
          Hide
          BillWeiss Bill Weiss added a comment -

          I've just used Richard's workaround as well.

          Show
          BillWeiss Bill Weiss added a comment - I've just used Richard's workaround as well.
          Hide
          jantman 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

          Show
          jantman 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
          Hide
          gertvdijk Gert van Dijk added a comment -

          Still happens with vcsrepo 1.0.x, unfortunately. Added this info in 'Environment' field.

          Show
          gertvdijk Gert van Dijk added a comment - Still happens with vcsrepo 1.0.x, unfortunately. Added this info in 'Environment' field.
          Hide
          kloeri Bryan Østergaard added a comment -

          I'm also seeing this with puppet 3.5.1 and vcsrepo 1.0.2.

          Show
          kloeri Bryan Østergaard added a comment - I'm also seeing this with puppet 3.5.1 and vcsrepo 1.0.2.
          Hide
          GeneBean GeneBean added a comment -

          I am seeing this on Puppet 3.6.2 and vcsrepo 1.1.0

          Show
          GeneBean GeneBean added a comment - I am seeing this on Puppet 3.6.2 and vcsrepo 1.1.0
          Hide
          hunter Hunter (Hunner) Haugen added a comment -
          Show
          hunter Hunter (Hunner) Haugen added a comment - PR for fixing this warning: https://github.com/puppetlabs/puppetlabs-vcsrepo/pull/209

            People

            • Assignee:
              hunter Hunter (Hunner) Haugen
              Reporter:
              redmine.exporter redmine.exporter
            • Votes:
              16 Vote for this issue
              Watchers:
              28 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile