Hi Fran,
There's a couple of things you can try. First, make sure you have the
module in your modules directory. I'm fairly sure you have this step done
but just in case. Then, since vcsrepo uses plugins to accomplish it's
tasks you need to ensure that the plugins are on both the puppet mast
Ellison is right, it really doesn't make much sense to create one resource
with create_resources. In fact, I'm not even sure it will work with
classes because I've never tried it. However, it works great for defined
types. I think I understand what you're trying to do so let me give an
examp
On Monday, February 18, 2013 12:21:11 AM UTC-6, John Warburton wrote:
>
>
>> Is this mcollective version 3.x or 2.3.x?
>
Deprecation warning occurs in 2.3. Complete removal will occur in the 3.x
production branch.
>
>
>> So you should be good to continue using it for a few months to come
Sy,
Welcome to Puppet. Hopefully we can help you get going so you can
experiment further.
First, what version of Puppet are you running? I'm guessing by your
commands that it's definitely prior to version 3. I recommend updating to
Puppet 3 before going further, especially since you're just
We're having a very strange issue with Puppet running on Passenger. Every
day or 2, our clients start receiving Passenger back traces. It's the
generic "Ruby (Rack) application could not be started." My initial thought
was that this is a resource/configuration problem. Maybe we're overrunnin
On Tuesday, August 27, 2013 7:26:41 PM UTC-5, François Lafont wrote:
>
> I thought about another way with the extlookup function.
>
> ---
> snmp:
> community: extvalue_community
>
> monitoring:
> community: extvalue_community
>
> And in a common.csv file:
>
> extvalue_community,abcd1234
I am running the latest version of the PuppetLabs F5 module and also
running latest version 11 on the F5s. I can successfully retrieve resources
from the F5 via `puppet resource f5_user`, etc. However, when I run puppet
and try to apply F5 resources I see the following output:
Debug: Puppet::Ut
