Mcollective is the right way to trigger puppet run.
On Wednesday, October 31, 2012 11:57:42 AM UTC-7, Nishant Jain wrote:
>
> Hello Everybody,
> I am looking for a way to trigger puppet rum
> remotely. so that i don't need to login into individual nodes and perform
> t
Same issue here.
[root@puppet ucla_gateway]# mco package puppet update -F
foreman_env=testing -v
Discovering hosts using the redisdiscovery method 58
/ [ ==> ] 29 / 58
The package application failed to run, use -v for full error det
I have the same issue but if I use "puppet apply --parser future" it works.
On Monday, May 27, 2013 11:50:50 PM UTC-7, thijso wrote:
>
> First off, I was under the impression from what I have been able to find
> about the future parser that old manifests should remain working. If there
> are bac
I solved my issue. Cloned the shared db for Foreman (emptied the type
column @ hosts table) and updated the external_node.rb with the latest one.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving
Hi Ohad,
I have the same issue since I've upgraded to 1.2. What do you mean with
"would need to dump the db into a new foreman db (or puppet)"?
Currently I'm sharing the same database for puppet and foreman. Should I
just clone the same database and reconfigure Foreman and Puppet to use both
d
