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

pc_repo yum resource idempotency issue with puppet_enterprise::profile::controller

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: puppet_agent
    • Labels:
    • Template:
      MODULES Bug Template
    • Team:
      Night's Watch
    • Story Points:
      3
    • Sprint:
      NW - 2020-08-06, NW - 2020-08-18
    • Method Found:
      Needs Assessment
    • CS Priority:
      Reviewed
    • Zendesk Ticket IDs:
      40090
    • Zendesk Ticket Count:
      1
    • Release Notes:
      Not Needed
    • QA Risk Assessment:
      Needs Assessment

      Description

      When Managing an agent with the puppet_agent class and also designating the same agent as a host for pe_client tools (https://puppet.com/docs/pe/2019.8/installing_pe_client_tools.html#install_pe_client_tools_on_a_managed_workstation)

      The puppet_agent class adds a repo called pc_repo and the puppet_enterprise::profile::controller class removes this repo, resulting in the following event on every puppet run:

       

      Notice: /Stage[main]/Puppet_agent::Osfamily::Redhat/Yumrepo[pc_repo]/ensure: created (corrective)
       Info: Yumrepo[pc_repo](provider=inifile): changing mode of /etc/yum.repos.d/pc_repo.repo from 600 to 644
       Notice: /Stage[main]/Puppet_enterprise::Repo::Config/File[/etc/yum.repos.d/pc_repo.repo]/ensure: removed (corrective)
       
      

       

      These functions should be able to co-exist

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              gheorghe.popescu Gheorghe Popescu
              Reporter:
              martin.ewings Marty Ewings
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support