FOUND IT!
It was a comedy of errors. The perms on the node.rb script were wrong (not
sure how they got that way, but...) and not only that there was some
residual configuration issues from an experiment I did two weeks ago that
was pointing to the hostname pocforman. instead of the FQDN of the
Fo
On 2015-02-24 16:09, Peter Berghold wrote:
What it looks like to me is going on is the YML file for the host ends
up on the Remote Master (which I can verify by looking for it) and the
node.rb is running on the Grand Master. Since the YML files isn't on the
Grand Master the lookup (of course) fai
What it looks like to me is going on is the YML file for the host ends up
on the Remote Master (which I can verify by looking for it) and the node.rb
is running on the Grand Master. Since the YML files isn't on the Grand
Master the lookup (of course) fails. So the real question is can we make
the
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'l
Using crude ascii art, here is what I have set up so far in my lab..
[Foreman/Puppet Grand Master] <-- foreman-proxy here
^
|
V
