are you sure foreman-report.rb is in your lib directory and named
"foreman.rb"? This caught me, but I think you would see error
messages about not being able to find a report named foreman. If you
copied it into a version specific location, and then updated your
puppet gem to a new version, puppe
of structure that would be great :)
> cheers,
> Ohad
> On Mon, Feb 22, 2010 at 11:11 PM, Andrew Dickson wrote:
>>
>> I've recently set up foreman with my existing puppet server, and I was
>> able to get all the host reporting working (I'm using storeconfigs),
>
I've recently set up foreman with my existing puppet server, and I was
able to get all the host reporting working (I'm using storeconfigs),
and once I ran:
RAILS_ENV=production rake puppet:import:puppet_classes
My puppet classes showed up on the settings page, however, it doesn't
seem to be assoc
when behavior in puppet changes, i think the docs would need to be
updated by someone familiar with the changes. is it a good idea to
just assume someone in the community will figure out the new behavior
through experimentation and take it upon themselves to correct the
docs?
-drew
On Mon, Nov 23
ohad,
the setup you describe is exactly what i am trying to do. the problem
seems to arise when i'm building a puppetmaster (host B) and it
generates it's certificates. puppetd stores it's ca.pem in the same
place that puppetmasterd tried to create ca.pem when it starts up.
this means the ca.pem
