Re: [Puppet Users] Metaparams break rake tests - how to avoid it ?

I believe what Martin was saying is, try `$stage_name` instead of `$stage` (or similar), because `$stage_name` would not be a reserved word/metaparameter name. Rob Nelson rnels...@gmail.com On Wed, Oct 26, 2016 at 8:35 PM, Jakov Sosic wrote: > On 10/22/2016 04:32 PM, Martin

Re: [Puppet Users] Metaparams break rake tests - how to avoid it ?

On 10/22/2016 04:32 PM, Martin Alfke wrote: This code is fine. You just declare a stage resource type. Except for: why do you want to make use of stages? Stages have been introduced as a high level ordering concept which is no longer best practice. You should use standard ordering instead

Re: [Puppet Users] Role vs hiera

It may not be as difficult as you think, and, you can *just* use it to insert a fake Fact, you don't have to start actually classifying your node classes with it. I supplied our ENC to the list a while ago, it's just a bit of Python that reads YAML:

Re: [Puppet Users] "Error: Could not request certificate: Error 500 on SERVER" after updating certificate

So you did remove the SSL certificate on the _agent_ as well? -- Lowe Schmidt | +46 723 867 157 On 26 October 2016 at 08:22, wrote: > In the log: > > Could not prepare for execution: The certificate retrieved from the master > does not match the agent's private key. >

Re: [Puppet Users] "Error: Could not request certificate: Error 500 on SERVER" after updating certificate

In the log: *Could not prepare for execution: The certificate retrieved from the master does not match the agent's private key.* *Certificate fingerprint: XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:...* *To fix this, remove the certificate from both the master and the agent and then