Hi Peter,
you might be running into http://projects.theforeman.org/issues/5925 .
I'm wondering whether subsequent runs work.
Also, the node.rb will run on the remote client's puppet master, so,
probably your "Remote Master". Since the default node.rb from foreman
requires this yaml file, it'll not work on your "Grand Master" unless
the agent has tried to contact that one too.
Regards, David
On 2015-02-24 14:45, Peter Berghold wrote:
Using crude ascii art, here is what I have set up so far in my lab..
[Foreman/Puppet Grand Master] <-- foreman-proxy here
^
|
V
[Puppet Remote Master] <-- foreman-proxy
running here.
^
|
V
[Simulated Remote Client]
The Foreman/Puppet Grand Master seem to be working swimmingly so far.
The Remote Master is getting its directions from the Grand Master. So
far so good.
Add the client and things start getting sideways. When I run the Puppet
agent on the remote client I get an error such that:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Failed when searching for node FQDN: Failed to find FQDN via
exec: Execution of '/etc/puppet/node.rb FQDN' returned 1:
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
I went over to the Grand Master and ran the /etc/puppet/node.rb from the
command line and it complains that it cannot find the yaml file in its
proper place. OK so I went over to the remote master and sure enough it
was there.
Needless to say Foreman has no idea the host is there.
What's the right electric acid Kool Aid foo to make this work
correctly? It would seem the YAML file needs to be on the Grand Master
and not the remote master... or does it? Is there a way the
foreman-proxy can help here?
--
Peter L. Berghold salty.cowd...@gmail.com <mailto:salty.cowd...@gmail.com>
h <http://blog.berghold.net>ttp://science-fiction.berghold.net
<http://science-fiction.berghold.net>
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to puppet-users+unsubscr...@googlegroups.com
<mailto:puppet-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAArvnv2Hnia87teGgq8Wt%3DpzSJOvUTgesHH1F7mkvFy1WTsGFA%40mail.gmail.com
<https://groups.google.com/d/msgid/puppet-users/CAArvnv2Hnia87teGgq8Wt%3DpzSJOvUTgesHH1F7mkvFy1WTsGFA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
* Always looking for people I can help with awesome projects *
Twitter: @dev_el_ops G+: https://plus.google.com/+DavidSchmitt
Blog: http://club.black.co.at/log/
LinkedIn: http://at.linkedin.com/in/davidschmitt
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/54EC84DD.8090400%40dasz.at.
For more options, visit https://groups.google.com/d/optout.
