Setting up foreman reporting

Jean-Louis_Mas · January 3, 2013, 4:30pm

I'm trying to set up foreman with puppet. Puppet is already running for
testing purpose

Foreman is installed and configured to be an ENC but for now the reports
tab does not report anything

I have followed the wiki
http://theforeman.org/projects/foreman/wiki/Puppet_Reports

On the puppet agent

grep report /etc/puppet/puppet.conf

report=true

On the puppetmaster/foreman (it's on the same server)

ll /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb

-rw-r–r-- 1 root root 1145 21 dï¿½c. 16:02
/usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb

grep "foreman_url=" /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb

$foreman_url='https://puppettest.imag.fr'

grep foreman /etc/puppet/puppet.conf

 reports = log, foreman

It should be obvious, but I cannot see my mistake.

Any ideas for the next move ?

Cheers

···

-- Jean Louis Mas

ohadlevy · January 3, 2013, 6:46pm

> I'm trying to set up foreman with puppet. Puppet is already running for
> testing purpose
>
> Foreman is installed and configured to be an ENC but for now the reports
> tab does not report anything
>
> I have followed the wiki
> http://theforeman.org/**projects/foreman/wiki/Puppet_Reports<Puppet Reports - Foreman>
>
> * On the puppet agent
>
> # grep report /etc/puppet/puppet.conf
> report=true
>
> * On the puppetmaster/foreman (it's on the same server)
>
> # ll /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb
> -rw-r–r-- 1 root root 1145 21 déc. 16:02 /usr/lib/ruby/site_ruby/1.8/
> puppet/reports/foreman.rb
>
> # grep "foreman_url=" /usr/lib/ruby/site_ruby/1.8/
> puppet/reports/foreman.rb
> $foreman_url='https://**puppettest.imag.fr <https://puppettest.imag.fr>'
>
> # grep foreman /etc/puppet/puppet.conf
> reports = log, foreman
>
> It should be obvious, but I cannot see my mistake.
>
> Any ideas for the next move ?
>
> by default, only reports with some meaningful info are shown, try clearing
the search bar and look again?

Ohad

···

On Thu, Jan 3, 2013 at 6:30 PM, Jean-Louis Mas wrote:

Cheers

–
Jean Louis Mas

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com**.
To unsubscribe from this group, send email to foreman-users+unsubscribe@**
googlegroups.com foreman-users%2Bunsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/**
group/foreman-users?hl=enhttp://groups.google.com/group/foreman-users?hl=en
.

Daniel_Piddock · January 24, 2013, 3:40pm

Hi all,

I'm suffering the same fate except I've just upgraded from a Puppet 2.6
master to 2.7. Running foreman 1.0.1 from the theforeman.org's deb
packages. Reports were working correctly and now I'm not getting any
come in at all. Clients are still running puppet 2.6. Clients don't
report errors when running and there's nothing interesting in
/var/log/puppet/ or /var/log/foreman/ on the master.

Client /etc/puppet/puppet.conf has:
[agent]
report = true

Master /etc/puppet/puppet.conf has:
…
[master]
…
reports = log, foreman

What changed between 2.6 and 2.7?

Thank you,
Dan

···

On 03/01/13 16:30, Jean-Louis Mas wrote: > I'm trying to set up foreman with puppet. Puppet is already running > for testing purpose > > Foreman is installed and configured to be an ENC but for now the > reports tab does not report anything > > I have followed the wiki > http://theforeman.org/projects/foreman/wiki/Puppet_Reports > > * On the puppet agent > > # grep report /etc/puppet/puppet.conf > report=true > > * On the puppetmaster/foreman (it's on the same server) > > # ll /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb > -rw-r--r-- 1 root root 1145 21 dï¿½c. 16:02 > /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb > > # grep "foreman_url=" > /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb > $foreman_url='https://puppettest.imag.fr' > > # grep foreman /etc/puppet/puppet.conf > reports = log, foreman > > It should be obvious, but I cannot see my mistake. > > Any ideas for the next move ?

Dominic_Cleal1 · January 24, 2013, 3:56pm

Some of the more recent packages use the vendor_ruby directory instead,
you might want to double check the foreman.rb is in the correct
location, e.g. /usr/lib/ruby/vendor_ruby/puppet/reports/

Check the puppetmaster's syslog and client logs for any errors too, it
tends to log when unable to run reports.

···

On 24/01/13 15:40, Daniel Piddock wrote: > On 03/01/13 16:30, Jean-Louis Mas wrote: >> I'm trying to set up foreman with puppet. Puppet is already running >> for testing purpose >> >> Foreman is installed and configured to be an ENC but for now the >> reports tab does not report anything >> >> I have followed the wiki >> http://theforeman.org/projects/foreman/wiki/Puppet_Reports >> >> * On the puppet agent >> >> # grep report /etc/puppet/puppet.conf >> report=true >> >> * On the puppetmaster/foreman (it's on the same server) >> >> # ll /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb >> -rw-r--r-- 1 root root 1145 21 dï¿½c. 16:02 >> /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb >> >> # grep "foreman_url=" >> /usr/lib/ruby/site_ruby/1.8/puppet/reports/foreman.rb >> $foreman_url='https://puppettest.imag.fr' >> >> # grep foreman /etc/puppet/puppet.conf >> reports = log, foreman >> >> It should be obvious, but I cannot see my mistake. >> >> Any ideas for the next move ? > > Hi all, > > I'm suffering the same fate except I've just upgraded from a Puppet 2.6 > master to 2.7. Running foreman 1.0.1 from the theforeman.org's deb > packages. Reports were working correctly and now I'm not getting any > come in at all. Clients are still running puppet 2.6. Clients don't > report errors when running and there's nothing interesting in > /var/log/puppet/ or /var/log/foreman/ on the master. > > Client /etc/puppet/puppet.conf has: > [agent] > report = true > > Master /etc/puppet/puppet.conf has: > .. > [master] > ... > reports = log, foreman > > What changed between 2.6 and 2.7?

–
Dominic Cleal
Red Hat Engineering

Daniel_Piddock · January 24, 2013, 4:20pm

I checked syslog and it was failing the run the foreman report:
puppet-master[9541]: Report processor failed: Could not send report to
Foreman at https://foreman/reports/create?format=yml: undefined method
`use_ssl=' for #<Net::HTTP foreman:443 open=false>

Turns out I needed to update my foreman.rb to something suitable for the
current version of ruby.

The puppet upgrade was just a coincidence as it caused me to restart
passenger.

Thank you for the help Dominic. It's all working now.

Dan

···

On 24/01/13 15:56, Dominic Cleal wrote: > On 24/01/13 15:40, Daniel Piddock wrote: >> Hi all, >> >> I'm suffering the same fate except I've just upgraded from a Puppet >> 2.6 master to 2.7. Running foreman 1.0.1 from the theforeman.org's >> deb packages. Reports were working correctly and now I'm not >> getting any come in at all. Clients are still running puppet 2.6. >> Clients don't report errors when running and there's nothing >> interesting in /var/log/puppet/ or /var/log/foreman/ on the >> master. >> >> Client /etc/puppet/puppet.conf has: [agent] report = true >> >> Master /etc/puppet/puppet.conf has: .. [master] ... reports = log, >> foreman >> >> What changed between 2.6 and 2.7? > > Some of the more recent packages use the vendor_ruby directory > instead, you might want to double check the foreman.rb is in the > correct location, e.g. /usr/lib/ruby/vendor_ruby/puppet/reports/ > > Check the puppetmaster's syslog and client logs for any errors too, > it tends to log when unable to run reports.