Uploaded image for project: 'Community Package Repository'
  1. Community Package Repository
  2. CPR-565

puppet-agent 5.3.6 in PC1 repo

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:

      Error rendering 'issue-templates-customfield'. Please contact your Jira administrators.

    • Team:
      Release Engineering
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      On an Ubuntu host, puppet-agent 5.3.6 exist in the PC1 repo. (pushed on 17 Apr)

      apt-cache policy puppet-agent
      puppet-agent:
      {{ Installed: 5.3.6-1xenial}}
      {{ Candidate: 5.3.6-1xenial}}
      {{ Version table:}}
      {{ *** 5.3.6-1xenial 500}}
      {{ 500 http://apt.puppetlabs.com xenial/PC1 amd64 Packages}}
      {{ 100 /var/lib/dpkg/status}}
      {{ 1.10.12-1xenial 500}}
      {{ 500 http://apt.puppetlabs.com xenial/PC1 amd64 Packages}}
      {{ 1.10.10-1xenial 500}}
      {{ 500 http://apt.puppetlabs.com xenial/PC1 amd64 Packages}}
      {{ 1.10.9-1xenial 500}}
      {{ 500 http://apt.puppetlabs.com xenial/PC1 amd64 Packages}}
      {{ 1.10.8-1xenial 500}}
      {{ 500 http://apt.puppetlabs.com xenial/PC1 amd64 Packages}}

      This is appearing in other distributions too, e.g. https://yum.puppetlabs.com/el/7/PC1/x86_64/

      In puppet documentation (https://puppet.com/docs/puppet/4.10/puppet_collections.html#repository-organization)

      > Numbered collections maintain the same major version of each component package during its lifetime

       

      I think this upgrade puppet-agent major version, which is what PC repo are meant to prevent.

        Attachments

          Activity

            People

            Assignee:
            bradejr Rob Braden
            Reporter:
            waipeng Jake Yip
            Votes:
            6 Vote for this issue
            Watchers:
            14 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support