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

"server" param setting in puppet.conf behaves inconsistently

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Cannot Reproduce
    • Affects Version/s: PUP 4.9.4, PUP 4.10.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Puppet agent 4.9 or 4.10 on CentOS 7

    • Template:
    • QA Risk Assessment:
      Needs Assessment

      Description

      When puppet agent is run as a service, and when the server field is set only in the [agent] section of puppet.conf, the server value is not correctly picked up.

      Steps to reproduce:

      1. Configure /etc/puppetlabs/puppet/puppet.conf so that server is set to some non-default value only in the [agent] section
      2. Run /opt/puppetlabs/puppet/bin/puppet config print | grep server – note that server shows as "puppet"
      3. Edit /etc/puppetlabs/puppet/puppet.conf so that server is set to some non-default value in the [main] section
      4. again run /opt/puppetlabs/puppet/bin/puppet config print | grep server – note that server now shows (correctly) as the non-default value you set.

      This manifests itself in an odd way – when puppet agent is run as a service, it fails with

      getaddrinfo: Name or service not known
      

      But when it is run manually, e.g. /opt/puppetlabs/puppet/bin/puppet agent -t -v it runs correctly.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ChrisOwens Chris Owens
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support