Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-4044

AIO acceptance tests copies multiple versions of repo configs to the SUT

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: PUP 4.1.0
    • Component/s: None
    • Labels:
    • Template:
    • Story Points:
      2
    • Sprint:
      Client 2015-04-29

      Description

      Puppet has an install_repos_on method (separate from beaker) that scp's repo configs from builds.puppetlabs.lan to the coordinator node, and then scp's them to the SUT(s). The problem is that it copies more than the SHA being tested. For example, on an agent node:

      # find /root/puppet-agent
      .
      ./puppetlabs-release-el-7.noarch.rpm
      ./pl-puppet-agent-71aa130dc8e2931d75b218abd1308386e462b24c-el-7-x86_64.repo
      ./x86_64
      ./x86_64/puppet-agent-0.3.2.27.g3a63b02-1.el7.x86_64.rpm
      ./x86_64/puppet-agent-0.3.2.59.g7f9eb57-1.el7.x86_64.rpm
      ./x86_64/puppet-agent-0.3.2.61.g4c11bc2-1.el7.x86_64.rpm
      ./x86_64/puppet-agent-0.3.2.63.ge907309-1.el7.x86_64.rpm
      ./x86_64/puppet-agent-0.3.2.65.gbc00b6e-1.el7.x86_64.rpm
      ./x86_64/puppet-agent-0.3.2.78.g32bfbf9-1.el7.x86_64.rpm
      ./x86_64/puppet-agent-0.3.2.89.g71aa130-1.el7.x86_64.rpm
      

      Ideally, the method should not be transferring repo_configs to the coordinator, e.g. when trying to run acceptance tests over the VPN. If it transferred repo configs directly to the SUT then we wouldn't have multiple versions of repo configs.

      At a minimum it should only transfer the repo configs for the SHA that is being tested.

      Risk assessment N/A for test framework

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              josh Josh Cooper
              QA Contact:
              Kurt Wall
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support