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

puppetlabs-puppet_agent : Exit early when apt repo config file has been modified

    XMLWordPrintable

    Details

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

      Description

      Basic Info
      Module Version: 3.0.2
      Puppet Version: n/a
      OS Name/Version: Debian platforms

      Describe your issue in as much detail as possible...

      Desired Behavior:

      Users who manually maintain the Puppet repo config file (i.e. puppet.list) on Debian platforms should be able to use the puppet_agent::install task without the task pausing at a prompt. If the task detects that the repo config file has been modified, it should skip attempting to install the agent for that target.

      Actual Behavior:

      Users who manually maintain the Puppet repo config file (i.e. puppet.list) on Debian platforms cannot use the puppet_agent::install task as expected. When the config file has been edited, dpkg will prompt the user if they want to keep the old config file or replace it with the config file provided by the repo. This causes the task to pause at a prompt, which the user is unable to answer. Specifying DEBIAN_FRONTEND=noninteractive does not pass this prompt. The only way to move past this prompt automatically is to force dpkg to accept either the old or new config file, which is undesirable as the task should not be making that decision.

        Attachments

          Activity

            People

            Assignee:
            thomas.beech Tom Beech
            Reporter:
            thomas.beech Tom Beech
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support