On Sun, Nov 16, 2014 at 6:27 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 11/14/2014 10:38 AM, David Schmitt wrote:
> > Puppet evaluates which provider to use only once per agent run.
>
> Hmm, are you sure about that?
>
> As far as I know, providers *will* become suitable during
On 11/14/2014 10:38 AM, David Schmitt wrote:
> Puppet evaluates which provider to use only once per agent run.
Hmm, are you sure about that?
As far as I know, providers *will* become suitable during the agent
transaction. Support for this has been added, seeing as it is not an
uncommon occurence
On 2014-11-14 06:53, Rohit Gupta wrote:
Hi David,
Apologies for the short description of the problem, I am new to puppet
and still trying to understand the problem for myself.
However, I dug a little deeper in the issue and I now have a little
better understanding of whats wrong.
I have a pupp
Hi David,
Apologies for the short description of the problem, I am new to puppet and
still trying to understand the problem for myself.
However, I dug a little deeper in the issue and I now have a little better
understanding of whats wrong.
I have a puppet-rabbitmq library that manages setti
Hi Rohit,
please post the actual error messages and - if at all possible - the
relevant source snippets.
That makes it infinitely easier to help you with your problem.
To guess about the problem you're seeing:
* the first run changes something, so that subsequent runs work
* your user en
I am deploying a VM using Vagrant which installs a puppet agent on that VM
and executes puppet agent as a background process.
In the very first puppet run, I get a failed dependency error. However if I
manually run puppet agent -t, things work fine.
I have tried running puppet agent from the p
