Hi Brian,
Sorry about the delay in responding. Unfortunately eval didn't work or at
least fqdn does not output the value I set it to in test_values.
I am just going to rework my testing to dump a file into
/etc/facter/facts.d and remove it after use. Not ideal but it works with
the least amo
On Wednesday, May 7, 2014 1:31:03 PM UTC-7, twm...@gmail.com wrote:
>
> Hi,
>
> I am very new to Puppet. I am running 3.5.1 via Foreman proxy.
>
> I unfortunately getting the following error on my client when I attempt to
> register its cert with the master.
>
> # puppet agent --server myse
Hi,
You need to include the puppet logging in you rspec file.
I can't remember what that is off the top of my head but I'm pretty sure this
will help you along the way.
http://www.ruempler.eu/2012/04/03/puppet-rspec-debugging/?mobile=1
> On 8 May 2014, at 0:42, choffee wrote:
>
> Am I doin
Hi,
I am very new to Puppet. I am running 3.5.1 via Foreman proxy.
I unfortunately getting the following error on my client when I attempt to
register its cert with the master.
# puppet agent --server myserver.domain --waitforcert 60 --test
Error: Could not request certificate: Error 400 o
Hi Team,
I am using below info in my manifest. URIEncoding="UTF-8" is not present
in server.xml. Trying to inject URIEncoding using below augeas syntax.
augeas { 'update_server.xml':
lens=> 'Xml.lns',
incl => "/opt/apphome/apache-tomcat-7.0.53/conf/server.xml",
And this is aside from the significant resistance we've been getting from
our traditional Windows admins over using Puppet, which is a problem that
Puppet definitely can't solve. Their partnership with Microsoft is a very
good thing, in my opinion though.
Oh, and Chocolatey. :D
--Alex
On Wedn
I'm sorry, I misspoke, I should have said that for us Puppet (PE actually)
has been a moving target in a number of ways.
For instance, we started out heavily using the PE dashboard to define what
classes specific nodes would get and related variables, pretty quickly
realized that that wasn't ve
Right, after dropping into #Puppet-dev and hashing the issue out with Andy
(zaphod42), have managed to find a fix...
The failures I was seeing on 1.9.3 were due to a difference in how
asadmin.rb:6 was being interpreted between Ruby 1.8.7 and 1.9.3, as Andy
outlined:
17:11 <+zaphod42> fatmcgav
On Wed, May 7, 2014 at 6:24 AM, Antoine Cotten wrote:
> Thanks Josh,
>
> This seems to work better indeed, although I can still observe a decrease
> in performances. The config retrieval time is higher than with config-based
> environments (9 sec -> 26 sec on average), and CPU-wise I can also noti
Am I doing this wrong?
I create a test that says "check for a file named foo", write some code
that should create the file. It fails for whatever reason and the test just
says no.
How do I get a clue what I am doing wrong? It seems obvious to me that
having the catalog that was tested against
Further to the below, it looks like I appear to be getting differing
behaviour in various environments :(
TravisCI passes on Ruby 1.8.7 [1] but fails on Ruby 1.9.3 [2].
Running the tests on a local CentOS 6 box with RVM, I get failures with
both versions of Ruby... So not sure why TravisCI can
Working with the excellent Austin DevOps meetup, we're setting up a Puppet
Meetup and starting to plan out events. Please join us and let us know
what you hope to get out of a meetup/user group and what times may work
best for you.
Meetup: http://www.meetup.com/austin-devops/events/181672382
On Tuesday, May 6, 2014 7:24:53 PM UTC-5, Phani wrote:
>
> How to dynamically assign variable to each node. If I had a 30 nodes and I
> had a file which is managed by puppet and I need to assign different values
> for each nodes from a array of values. How to do it other than making it
> stati
Thanks Josh,
This seems to work better indeed, although I can still observe a decrease
in performances. The config retrieval time is higher than with config-based
environments (9 sec -> 26 sec on average), and CPU-wise I can also notice
an increase but this is hard to quantify without prolonged
I am trying to debug why my test is failing and not producing a file that I
thought it should be.
Is there a simple way to view the catalogue that rspec is testing against?
I tried --debug in the .rspec file with the debugger gem and it gives no
extra errors is there something more I need to ad
Is there a known way to do this or anything on the horizon that would make
this functionality easier?
I am attempting to use facts.d to establish a list of 'roles' that resolve
to locations in my hiera hierarchy (- roles/%{::roles}). Unfortunately it
doesn't actually work as expected right now
How to dynamically assign variable to each node. If I had a 30 nodes and I
had a file which is managed by puppet and I need to assign different values
for each nodes from a array of values. How to do it other than making it
static.
--
You received this message because you are subscribed to th
On 05/07/2014 12:52 AM, Ramin K wrote:
>
> I find it best not to change my workflow or methodology until it
> makes sense on my system regardless of what the community or even Puppet
> Labs has said.
Ramin, I could hardly agree more. Even your ignored practices resemble
my own personal choice
18 matches
Mail list logo
