Thanks for the advice, now something really nasty happened, lucky me this
is the test environment, I lost all the client keys
Before enabling foreman I had:
reports = store, puppetdb
Then I changed to the following and restarted the service:
reports = log, foreman
When I executed puppet agent
Thanks Sean - perfect.
--
"Mission Statement: To provide hope and inspiration for collective action,
to build collective power, to achieve collective transformation, rooted in
grief and rage but pointed towards vision and dreams."
- Patrisse Cullors, *Black Lives Matter founder*
On 6 July
The guide you referenced is for foreman 1.3, I assume you are using a later
version of foreman? Here is the latest documentation:
https://theforeman.org/manuals/1.15/index.html#3.5.4PuppetReports
On Thu, Jul 6, 2017 at 12:35 PM, Kernel Panic
wrote:
> Hi guys, hope you
Hi guys, hope you are doing well.
I'm trying to configure puppet reports using this
guide: https://theforeman.org/manuals/1.3/index.html#3.5.4PuppetReports
I copied the file
to /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb
and the I configured the following:
It's coming from Katello...
Go the Content host where packages & errata are you'll see an extra tab
named "Traces" it will show you processes required to be restarted.
You can also run "tracer -ea" on the client.
On Wed, 5 Jul 2017 at 23:28, Lachlan Musicman wrote:
> On 5
Hi,
not sure if that is a Foreman/Katello issue but maybe someone does have any
idea.
I am just trying to sync the Puppetlabs Forge repo. I created a new Product
as described
here:
https://www.theforeman.org/plugins/katello/3.4/user_guide/puppet_integration/index.html
When i starting the