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

vcsrepo: cvs working copy from source not detected

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: vcsrepo
    • Labels:
      None
    • Template:
      MODULES Bug Template
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: latest
      Puppet Version: 4.10.8
      OS Name/Version: Ubuntu 16.04.1

      The following code should detect after the second run the working copy correctly:

      vcsrepo { '/tmp/JamochaMUD':
        ensure => 'present',
        provider => 'cvs',
        source => ':pserver:anonymous@jamochamud.cvs.sourceforge.net:/cvsroot/jamochamud',
        module => 'JamochaMUD',
      }
      

      But this happens:

      rm -rf /tmp/JamochaMUD
       
      puppet apply --modulepath=/tmp/modules testvcsrepo.pp
      Notice: Compiled catalog for test.example.com in environment production in 0.30 seconds
      Notice: /Stage[main]/Main/Vcsrepo[/tmp/JamochaMUD]/ensure: created
      Notice: Applied catalog in 6.38 seconds
       
      puppet apply --modulepath=/tmp/modules testvcsrepo.pp
      Notice: Compiled catalog for test.example.com in environment production in 0.31 seconds
      Error: Path /tmp/JamochaMUD exists and is not the desired repository.
      Error: /Stage[main]/Main/Vcsrepo[/tmp/JamochaMUD]/ensure: change from absent to present failed: Path /tmp/JamochaMUD exists and is not the desired repository.
      Notice: Applied catalog in 0.68 seconds
      

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            vicinus Reinhard Vicinus
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support