Issue #3669 has been updated by Ben Hughes.
Ah-ha! I can't use env puppet:
<pre>
[root@hackday:puppet]# tcpdump -ntpi eth0 -v port 53 | grep SRV
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535
bytes
10.0.1.135.28940 > 10.0.1.20.53: 15878+ SRV? _x-puppet._tcp.example.org.
(44)
10.0.1.135.28940 > 10.0.1.20.53: 35005+ SRV?
_x-puppet._tcp.example.org.example.org. (56)
10.0.1.135.32001 > 10.0.1.20.53: 53744+ SRV?
_x-puppet-report._tcp.example.org. (51)
10.0.1.135.32001 > 10.0.1.20.53: 18766+ SRV?
_x-puppet-report._tcp.example.org.example.org. (63)
10.0.1.135.36640 > 10.0.1.20.53: 45958+ SRV? _x-puppet._tcp.example.org.
(44)
10.0.1.135.36640 > 10.0.1.20.53: 43641+ SRV?
_x-puppet._tcp.example.org.example.org. (56)
</pre>
With the 26ce9c79672d578e9aa03d8341d8c315fcf30c8b code base.
and with head:
<pre>
[root@hackday:puppet]# tcpdump -ntpi eth0 -v port 53 | grep SRV
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535
bytes
10.0.1.135.37645 > 10.0.1.20.53: 51039+ SRV? _x-puppet._tcp.example.org.
(44)
10.0.1.135.37645 > 10.0.1.20.53: 360+ SRV?
_x-puppet._tcp.example.org.example.org. (56)
10.0.1.135.4455 > 10.0.1.20.53: 4292+ SRV?
_x-puppet-report._tcp.example.org. (51)
10.0.1.135.4455 > 10.0.1.20.53: 24676+ SRV?
_x-puppet-report._tcp.example.org.example.org. (63)
10.0.1.135.39931 > 10.0.1.20.53: 6178+ SRV? _x-puppet._tcp.example.org. (44)
10.0.1.135.39931 > 10.0.1.20.53: 24194+ SRV?
_x-puppet._tcp.example.org.example.org. (56)
</pre>
Putting back in the SRV record...
<pre>
[root@hackday:~]# bash ~/src/puppet/ext/envpuppet puppet agent -t
info: Retrieving plugin
err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using
'eval_generate: getaddrinfo: Name or service not known
err: /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
info: Loading facts in /var/lib/puppet/lib/facter/myfact.rb
info: Caching catalog for hackday.example.org
....
</pre>
and see
<pre>
[root@hackday:puppet]# tcpdump -ntpi eth0 -v port 53 | grep SRV
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535
bytes
10.0.1.135.49497 > 10.0.1.20.53: 14566+ SRV? _x-puppet._tcp.example.org. (51)
10.0.1.20.53 > 10.0.1.135.49497: 14566* 1/1/2 _x-puppet._tcp.example.org.
SRV puppetmaster.example.com.:8140 0 0 (144)
10.0.1.135.60249 > 10.0.1.20.53: 47303+ SRV?
_x-puppet-report._tcp.example.org. (58)
</pre>
----------------------------------------
Feature #3669: Make puppet honor DNS SRV records
https://projects.puppetlabs.com/issues/3669#change-60668
Author: Martin Marcher
Status: Re-opened
Priority: Normal
Assignee:
Category:
Target version: Telly
Affected Puppet version: development
Keywords:
Branch:
https://github.com/jhelwig/puppet/tree/ticket/master/3669-make-puppet-honor-DNS-SRV-records
I'd like to be able to define where puppet looks for the master server.
I propose the following:
By default try in the following order:
1. Look for a "_x-puppet._tcp.example.com" SRV record (or any name that you
think is appropriate, but keep it a SRV record)
2. For backwards compatibility, if no SRV record is present look for
puppet.example.com as a fallback or any value that is configured in the puppet
config file
Reasoning:
A System Administrator can easily spread out the load over multiple puppet
servers in this way or define some split horizon which answers with the
"correct" hostname to use as a puppet master.
Thanks,
Martin
--
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
