Jira (PUP-7434) "server" param setting in puppet.conf behaves inconsistently

[Chris Owens (JIRA)]

Title: Message Title

Chris Owens created an issue   Puppet / PUP-7434 "server" param setting in puppet.conf behaves inconsistently Issue Type: Bug Affects Versions: PUP 4.10.0, PUP 4.9.4 Assignee: Unassigned Created: 2017/04/06 9:43 PM Environment: Puppet agent 4.9 or 4.10 on CentOS 7 Priority: Normal Reporter: Chris Owens 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: Configure /etc/puppetlabs/puppet/puppet.conf so that server }} is set to some non-default value only in the {{[agent] section Run /opt/puppetlabs/puppet/bin/puppet config print | grep server – note that server shows as "puppet" Edit /etc/puppetlabs/puppet/puppet.conf so that server is set to some non-default value in the [main] section 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. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.