Foreman upgrade troubles with reports (1.1 to 1.2)

Im having a problem with reports with an upgrade from 1.1. Two big issues
to note I have been version locked on puppet 2.7 for a long time; and my
foreman instance has been installed on the puppet master.

Now Im ready to upgrade so I am starting with foreman and moving it to a
new box off of the puppet server. Upgrade to 1.2 is perfect but I cannot
get the puppetmaster to send reports to this box.

There is nothing in the puppet logs about not being able to reach the new
foreman box and there is never even any tcp traffic to the new box
(checking via tcpdump) Does anyone have any idea what I might be doing
wrong… or what I can look at?

puppet master version 2.7.18
puppet.conf (master section)


ssldir = $vardir/ssl

ssl_client_header = SSL_CLIENT_S_DN

ssl_client_verify_header = SSL_CLIENT_VERIFY

storeconfigs = true

storeconfigs_backend = puppetdb

rrddir = $vardir/rrd

rrdinterval = $runinterval

rrdgraph = true
  • reports = log, foreman*
autosign = /etc/puppet/autosign.conf { mode = 664 }

external_nodes = /etc/puppet/external_node.rb

node_terminus  = exec

foreman.rb is this file:
with the ssl variables commented out, and my foreman hostname for

Any ideas what too look for?? Also, If I switch back to the foreman
instance on the puppetmaster (still at 1.1) reports all work, and oddly
enough reports still work on that instance even without point foreman.rb to
it (perhaps it is reading local files?)

Correction to the above, the reports only work on the puppetmaster when I
set foreman.rb to point to it.

Well, crap. I figured it out. I dont have my puppet servers in dns,
they are in hosts files. I never put the entries in new foreman server
hosts files. so they were being denied access. as for the tcpdump I dont
know why I wasnt seeing traffic…