Issue #16840 has been updated by Andrew Rankin.

I've also hit this bug.  I had to defined "pluginsource = puppet:///plugins" in 
my puppet.conf in order to not get:

[root@puppet0 puppet]# puppet agent --test
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources 
using 'eval_generate': Connection timed out - connect(2)
Error: Could not retrieve plugin: execution expired

When using SRV records.

Andrew

----------------------------------------
Bug #16840: Default setting for pluginsource problematic for deployments using 
SRV records
https://projects.puppetlabs.com/issues/16840#change-101260

* Author: Shane Madden
* Status: Investigating
* Priority: Normal
* Assignee: eric sorenson
* Category: 
* Target version: 
* Affected Puppet version: 3.0.0
* Keywords: srv
* Branch: 
----------------------------------------
The current default for the `pluginsource` setting is 
`puppet://$server/plugins`.  This works well with a `server` set, but in 
deployments that utilize 3.0's SRV record feature, the `server` setting is 
likely not utilized at all for communication with a master, and will often be 
unset.

If SRV records are in use the `pluginsource` still gets filled in with the 
contents of the `server` setting - and if it's unset, then the default is 
`puppet`.  This causes failure of the pluginsync process, which is a non-fatal 
error for the agent run:
    
    Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources 
using 'eval_generate: getaddrinfo: Name or service not known
    Error: /File[/var/lib/puppet/lib]: Could not evaluate: getaddrinfo: Name or 
service not known Could not retrieve file metadata for puppet://puppet/plugins: 
getaddrinfo: Name or service not known

I believe that changing the default setting for `pluginsource` from 
`puppet://$server/plugins` to `puppet:///plugins` is functionally equivalent 
for 'normal' deployments not running `use_srv_records`, while it will cause the 
pluginsync process to find a working master in cases where `use_srv_records` is 
utilized.

Simply setting `pluginsource = puppet:///plugins` is an effective workaround 
for SRV record deployments in the interim.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to