Reporting to Foreman Not Working After Upgrade to ver. 1.5

Hello!

After upgrading Foreman to ver. 1.5.x, I am noticing that my clients are
failing to successfully submit reports to the Foreman server, which is
running RHEL 6.x. I did have to turn on the Red Hat Software Collections
repository, which I believe changed Foreman's 'reports' directory from
'/usr/lib/ruby/site_ruby/1.8/puppet/reports' to
'/opt/rh/ruby193/root/usr/share/ruby/vendor_ruby/puppet/reports'.

Accordingly, I have followed the instructions here
<http://www.theforeman.org/manuals/1.5/index.html#3.5.4PuppetReports> to
download the 'foreman-report_v2.rb.erb' file to the new 'reports'
directory. However, whether I rename 'foreman-report_v2.erb' to
'foreman-report.rb' or simply to 'foreman.rb' (as the documentation
suggests), I still fail to see new reports in the web interfaces.

I have restarted both 'httpd' and 'foreman', to no avail, and have also
been sure to update the 'foreman.rb' file with the appropriate
$foreman_url, $foreman_ssl_ca, $foreman_ssl_cert, and $foreman_ssl_key
variable definitions.

Any assistance would be greatly appreciated. Thanks!
– Adam

The Puppet master is not normally run under SCL, so I doubt that's the
correct directory for the foreman.rb report processor. Probably worth
doublechecking that before going further.

Greg

··· On 13 August 2014 14:23, Adam Craig wrote: > Hello! > > After upgrading Foreman to ver. 1.5.x, I am noticing that my clients are > failing to successfully submit reports to the Foreman server, which is > running RHEL 6.x. I did have to turn on the Red Hat Software Collections > repository, which I believe changed Foreman's 'reports' directory from > '/usr/lib/ruby/site_ruby/1.8/puppet/reports' to > '/opt/rh/ruby193/root/usr/share/ruby/vendor_ruby/puppet/reports'.

Thanks, Greg! Your tip pointed me in the right direction. Since there was a
'foreman.rb' file in the SCL directory
('/opt/rh/ruby193/root/usr/share/ruby/vendor_ruby/puppet/reports'), I made
the presumption that Foreman was using that directory. It turns out that it
was still using the original directory
('/usr/lib/ruby/site_ruby/1.8/puppet/reports'), but the 'foreman.rb' file
simply needed to be replaced with the 'foreman-report_v2.rb.erb' file as
linked in the documentation, and the variables updated.

Best,
– Adam

··· On Wednesday, August 13, 2014 1:07:42 PM UTC-4, Greg Sutcliffe wrote: > > On 13 August 2014 14:23, Adam Craig <jadam...@gmail.com > > wrote: > > Hello! > > > > After upgrading Foreman to ver. 1.5.x, I am noticing that my clients are > > failing to successfully submit reports to the Foreman server, which is > > running RHEL 6.x. I did have to turn on the Red Hat Software > Collections > > repository, which I believe changed Foreman's 'reports' directory from > > '/usr/lib/ruby/site_ruby/1.8/puppet/reports' to > > '/opt/rh/ruby193/root/usr/share/ruby/vendor_ruby/puppet/reports'. > > The Puppet master is not normally run under SCL, so I doubt that's the > correct directory for the foreman.rb report processor. Probably worth > doublechecking that before going further. > > Greg >