or other debug messages. The structure of the data
directory and manifests is exactly the same. The production environment
has puppetDB operating, but the staging environment was newly created and
only has puppetserver.
Any suggestions on how to debug this would be appreciated.
Thank you,
Jon
Fair enough. Some parts of our Puppet code base is almost 10 years old,
and usually only gets updated when a deprecation requires it. We'll have
to put some time into reorganizing things a bit one of these days.
Jon
On Wednesday, 29 August 2018 07:58:32 UTC-6, Henrik Lindberg wrote:
&
Guess I should have read to point 6 in PUP-1434, init.pp is special. Got
it, thanks a bunch.
Jon
On Tuesday, 28 August 2018 10:08:16 UTC-6, j...@jnjschneider.com wrote:
>
> So does this mean if the path is '$module_path/seed/manifests/init.pp' then
> the define name will n
So does this mean if the path is '$module_path/seed/manifests/init.pp' then
the define name will now need to be 'seed::init::remote_file' in place of
'remote_file'?
Thanks,
Jon
On Tuesday, 28 August 2018 09:50:48 UTC-6, Branan Purvine-Riley wrote:
>
> Hi
ht have on why this warning has
started to pop up.
Jon
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.co
Same problem with AutoFS
On Thursday, May 5, 2016 at 8:51:41 AM UTC+2, amateo wrote:
>
> Hello,
>
> I'm testing my puppet code in the new ubuntu 16.04.
>
> I'm using razorsedge/snmp module from the forge to manage snmpd.
> In
> this module, it manages snmpd service with:
>
>
I had this issue as well. To get around it you can pass an extra option:
--certname
This way it won't try to use your current host's FQDN as the certname
(which will fail if it's already registered with the CA)
So, e.g.
puppet certificate generate treydock --certname treydock
On Tuesday,
and instead use
this custom command for maintenance/troubleshooting activities.
On Thursday, September 11, 2014 10:11:10 AM UTC-4, Jon McKenzie wrote:
>
> Hi all,
>
> We're thinking about implementing the "puppet facts upload" pattern to
> send facts up to the Puppetma
Hi all,
We're thinking about implementing the "puppet facts upload" pattern to send
facts up to the Puppetmaster (and into Foreman) out-of-band. Basically, we
need a way to distinguish hosts which are alive, but just have their agent
disabled (e.g. for troubleshooting), and hosts which are jus
I am interested in starting one if one does not yet exist.
I'd like to talk about and collaborate on usage of puppet.
Anyone can hit me up if there is such a group here in town, I know there is
one in Portland but I won't be going any time soon.
--
You received this message because you are sub
like this because they help me
learn more about Puppet.
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegrou
the problem.
I'm not sure why this works. I suspect it's because adding the ".x86-64"
somehow prevents the pattern from matching Percona. I'm going to
check this.
This approach is easier than creating a custom fact.
Thanks for all the suggestions.
Jon Forrest
--
You
that you want not only that package absent, but also all
its configuration files and any other packages that depend on it.
This is indeed the critical fact that I wasn't aware of. Thanks
for clearing this up.
Jon
--
You received this message because you are subscribed to the Google Groups &q
ebuild to change what Percona provides
2) Use something like (untested)
exec { "/usr/bin/yum -y remove mysql":
onlyif => "/bin/rpm -qa |/bin/fgrep mysql"
3) Just presume that MySQL won't be installed in the first place.
I could do this but I'd like my modules to be mor
deleted. However, this package wasn't
actually installed, e.g.
# rpm -qa | fgrep PackageKit
#
Why would that second message appear? I didn't ask for the
package to be created, plus the package wasn't actually created.
Thanks,
Jon Forrest
--
You received this message because you
On Wed, Apr 23, 2014 at 8:54 AM, jcbollinger wrote:
>
>
> On Tuesday, April 22, 2014 2:16:22 PM UTC-5, Jon Forrest wrote:
>>
>> (I found a discussion from 6/22/09 on this topic, but that was a long time
>> ago.)
>
> Did the discussion give you reason to think that
yum -d 0 -e 0 -y install
PackageKit-purge' returned 1: Error: Nothing to do
Wrapped exception:
This looks like a bug to me.
I ended up using
exec { "/usr/bin/yum -y remove PackageKit":
onlyif => "/bin/rpm -qa |/bin/fgrep PackageKit",
}
but this is a step i
#x27;t care about typos, grammar, style, or
formatting can ignore all that and only look at the true errors.
I knew that not everyone would be interested in what I found. That's
why I clearly labeled my postings so that people who didn't care about
issues in the book could ignore what I
://www.dropbox.com/s/qmcdgdo4bvq620q/propuppet2.txt
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To v
Here are the issues I found in Chapters 11 and 12.
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(U) Pg. 249 Most readers won't know what "an orchestration framework" is.
I know I don't.
(C) Pg. 249 "commands dispatched to systems in this
s still empty, even after everything I've posted.
Jon
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@go
Here are the issues I found in Chapters 10.
Jon Forrest
M = mistake - all readers should be aware of this
U = unclear - chances are readers will wonder about this
T = typo - a trivial uncontroversial text change
E = text change - most readers won't care but editors should
C = comment -
Here are the issues I found in Chapters 8 and 9.
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(T) Pg. 191 "like librarian puppet" ->
"like librarian-puppet"
(T) Pg. 191 "rspec-puppet, rspec-system and integrating" ->
"rspec-p
ob is located, or whether telecommuting
is allowed.
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.co
Here are the issues I found in Chapter 7. Short chapter - many typos.
Only 5 more chapters to go.
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(M) Pg. 169 "an external node carrier (ENC)" ->
"an external node classifier (ENC)"
(C) Pg. 169
't commit to anything with fixed deadlines. It wouldn't be fair
to you or Apress.
> I don't think its realistic to open source the book at this point, but I'll
> open the
> conversation with Apress and the other authors.
OK. If you do change your mind then I'd be
On Wednesday, March 5, 2014 10:29:07 AM UTC-8, Spencer Krum wrote:
Hi Jon,
> My name is Spencer Krum. I am one of the authors of Pro Puppet. I want to
thank you for going through the book with such a fine toothed comb.
> I wish I had known you were so committed to making this book a s
Here are the issues I found in Chapter 6. There were an awful lot
of typos.
Jon Forrest
M = mistake
U = unclear
T = typo
E = text change
C = comment
(E) Pg. 155 "multiple hosts that have a relationship" ->
"multiple related hosts"
(E) Pg. 155 "resources and their i
On 3/5/2014 1:26 PM, Alessandro Franceschi wrote:
Hei Jon,
your text correction and errors hunting skills are impressive.
Thanks. I try.
I'm writing a book about Puppet too and am definitively in time to
correct it before printing.
There are already technical reviewers doing a great
Here are the issues I found in Chapter 5.
M = mistake
U = unclear
T = typo
E = text change
C = comment
(T) Pg. 141 "classes, inheritance, variables and environment configuration" ->
"classes, inheritance, variables, and environment configuration"
(E) Pg. 141 "This integration is used" ->
"This i
Again, nothing that a good proof edit couldn't fix.
Jon Forrest
(U) Pg. 100 Listing 4-2 shows package resource definitions appearing as
the result
of running 'puppet resource service'. Are we supposed to do anything
with these definitions?
(U) Pg. 100 In Listing 4-2 why
again
in the 2nd edition. This error even appears in their errata for
the 1st edition.
In spite of what appears below, I think Pro Puppet is pretty good,
and is definitely worth reading. But Apress better be careful, because
they're in danger of becoming as bad as Packt in their editorial
qua
; with the ";vdsmdummy;" bridge device.
>
I'm having the same problem on a node without Infiniband, but with VDSM
installed. This is with
version 1.7.5 of facter on CentOS 6.5 (with all patches).
This doesn't seem to prevent anything from working. It would be nice if it
ything else) is wasteful. In time, the lack of
client parallelization
could be a competitive weakness as Puppet competes in the marketplace.
(I don't know
what the status of client parallelization is in the competition right now).
Jon Forrest
--
You received this message because you are sub
ow which actions
it should do safely in parallel.
If any other the experts have anything to add I'd love
to hear it.
Jon Forrest
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiv
location. The new define includes a 'proxmox_workaround' flag to handle
this special case. I updated the wiki page to show this workaround:
http://jaroker.org/technical_notes/issues/software/puppet/start
Regards,
Jon
---
Jon Jaroker
http://jaroker.com
On Thu, Jan 30, 2014 at 9:
I'm trying to debug a new ENC setup. I created a short perl script to
output a few lines of YAML. It runs fine on the puppet server but when I
try it on a client I get this error:
Warning: Error 400 on SERVER: Failed to find client.domain.org via exec:
Execution of the '/etc/puppet/ENC/plug0.pl
:
>
>
>
>
> On Mon, Feb 3, 2014 at 9:45 AM, Jon Yeargers
> > wrote:
>
>> Right. So how would I declare this dependency setup if I stop using node
>> files?
>>
>
> Even if you use an ENC, Puppet will still consult your site manifest, so
> using an ENC does
?
>
> Regards,
> El 03/02/2014 16:13, "Jon Yeargers" >
> escribió:
>
>> I need to convert my resource based system to ENC. It's mostly
>> straightforward but I'm not sure how to handle operations like these:
>>
>> Class['apt']
I need to convert my resource based system to ENC. It's mostly
straightforward but I'm not sure how to handle operations like these:
Class['apt'] -> Package<| |>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group a
path=> $bind_conf,
content =>
template('openvz/mount.conf.erb','common/header.sh.erb'),
mode=> 740, #(Proxmox file system unable to chmod)
}
Any suggestions on how to troubleshoot this?
Thank you,
Jon
--
You received thi
The URI scheme for 'source' is either 'puppet' or 'file'. Here is the man
page:
http://docs.puppetlabs.com/references/latest/type.html#file-attribute-source
To pull from a repository, you should use a subversion manifest that
implements checkout.
Jon
On Monda
age is appending (what appears to be) the temporary
file name used in generating a diff to the managed resource.
I put the error message and relevant manifest on a web page as well as
excerpt them below.
Can someone offer suggestions on how I can debug this?
Thank you,
Jon
Full m
I corrected the problem by including this in my /etc/init.d/
I have a group of services that are supposed to be maintained by puppet
agent. Up until I moved from 2.6 to 3.4 they were kept up to date and
running (as expected).
Since the upgrade of the puppet agent these services are no longer being
monitored. I'm sure that the server is still seeing the f
Running 'puppet agent --test' - after 5-10 minutes of execution this error
appeared:
err: Could not run Puppet configuration client: execution expired
When I ran the same command the execution resumed and continued to
completion.
--
You received this message because you are subscribed to the
I'm using the puppetforge 'apt' module to deal with some repositories. It
has 'always-apt-update' as a property and I've had it set to 'true' but I'm
wondering what happens if I don't.
Is the puppet package manager 'smart' enough to get the latest versions of
packages that it's monitoring ('en
08 PM, Paul Archer wrote:
> > I see that puppet 3.3.2 has the problem as well. Worse, the
> > documentation for 'puppet node' doesn't match the actual command.
> >
> >
> > On Friday, December 13, 2013 11:13:26 AM UTC-6, Jon McKenzie wro
Answer here:
http://stackoverflow.com/questions/14607385/puppet-does-not-start-a-service-varnish-when-puppet-apply-is-run
On Friday, December 13, 2013 11:07:01 AM UTC-8, Jon Yeargers wrote:
>
> Just out of curiosity I created my own 'dmidecode' package with a trivial
ithout
> this dependency
> b) fetch all deb packages you require and install them in one go using
> dpkg -i --force-depends or similar.
>
> Option (a) is simple if you're versed in the creation of Debian
> packages, and pretty difficult if you're not.
>
Re-upping this topic rather than creating a new one.
I'm using Puppet 3.3.1 and am still having this problem.
For example, if I run:
puppet node find $(puppet config print certname) --render-as yaml
The resulting YAML is missing ENC-set parameters (among other things).
On the other hand, if I
So am I SOL on this? Is ARM considered an 'unsupported architecture' until
I can create a 'dmidecode' for this platform?
On Wednesday, December 11, 2013 10:55:11 AM UTC-8, Jon Yeargers wrote:
>
> I can wget and install facter but the issues continue:
>
> root@
11, 2013 9:50:07 AM UTC-8, Jeff Bachtel wrote:
>
> You can fetch it directly (wget, curl, whatever) from
>
>
> http://apt.puppetlabs.com/pool/squeeze/main/f/facter/facter_1.6.18-1puppetlabs1_all.deb
>
> Jeff
>
> On 12/11/2013 12:39 PM, Jon Yeargers wrote:
>
> root@plug
cking depends. The puppet install should succeed after that.
>
> I think facter's dmidecode dependency should be a Suggests vice a Depends,
> and it might be worth filing a bugrep to get it changed.
>
> Jeff
>
>
> On 12/11/2013 10:31 AM, Jon Yeargers wrote:
>
> I
epends : dmidecode but it is not installable
If I do 'apt-cache search dmidecode' it isn't available.
On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote:
>
> 'apt-get update' ran fine this time.
>
> 'apt-get install puppet'
On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza
> >
> wrote:
> > On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers
> > >
> wrote:
> >> I updated the repository file using the official puppet-recommended
> version.
> >> The corrected line is:
>
>
> Have you tried the instructions here:
>
> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu
>
>
> Because what apt is making of your configuration is plain wrong.
>
> On 12/10/2013 05:50 PM, Jon Yeargers wrote:
> > I
getcwd"
In my case, the solution was to identify DOS-encoded files on the master
and convert them to unix.
Jon
On Wednesday, June 19, 2013 12:28:28 PM UTC-4, Rachel Andrew wrote:
>
> Hi
>
> fully expecting to have done something silly here but am struggling to
> debug why
achine and then
rebuild the package file myself in a private repository.
On Tuesday, December 10, 2013 8:22:36 AM UTC-8, Jon Yeargers wrote:
>
> I've tried using 'gem' to install the latest build but it brings down lots
> of (seemingly) unnecessary bits with it. (examples,
eadache.
>
> Jeff
>
>
> On Thu, Dec 5, 2013 at 7:29 PM, Jon Yeargers
> > wrote:
>
>> After I got puppetdb working I was looking about at the various bits of
>> data available. Looking at the 'nodes' option I was suprised to see this:
>>
I've tried using 'gem' to install the latest build but it brings down lots
of (seemingly) unnecessary bits with it. (examples, docs, etc)
On Thursday, December 5, 2013 9:16:15 AM UTC-8, Jon Yeargers wrote:
>
> I'm looking to deploy several hundred ARM based machines
On further inspections the YAML files are still being created but not the
puppet db entries.
On Thursday, December 5, 2013 4:29:44 PM UTC-8, Jon Yeargers wrote:
>
> After I got puppetdb working I was looking about at the various bits of
> data available. Looking at the 'nodes
After I got puppetdb working I was looking about at the various bits of
data available. Looking at the 'nodes' option I was suprised to see this:
"report_timestamp" : null
for every node. They all have this for their puppet.conf:
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/va
(This is actually two questions):
Running 'puppet agent --test' on a 1Ghz ARM based (Debian 6) fanless PC.
It's pretty common to see the 'catalog run' take 120-300 seconds. Is this
typical?
Second (and possibly related): when I do a 'puppet agent --test (--noop)' I
get this set of messages:
d the results of running
> puppetdb-ssl-setup ... the more information the better in these kinds
> of cases.
>
> Also - is PuppetDB listening to port 8080?
>
> On Thu, Dec 5, 2013 at 9:15 PM, Jon Yeargers >
> wrote:
> > I used 'puppetdb-ssl-setup' (afte
cally, so try
> this first. For ssl-host I usually recommend something like ::1 or
> 0.0.0.0 to listen on all ports for simplicity, but you can make this
> explicit if you like.
>
> ken.
>
>
>
> On Thu, Dec 5, 2013 at 7:48 PM, Jon Yeargers >
> wrote:
> &g
I did `yum update` on my puppet server about a week ago. Up to that point I
had puppet and puppetdb running on the same machine. Since the update
puppetdb doesn't appear to be listening on port 8081 anymore.
When I run `puppet agent --test` on a client I get this error:
err: Could not retri
I'm looking to deploy several hundred ARM based machines in the near
future. At this point the puppet agent version available via apt (Debian 6)
is 2.6.
I tried adding the apt.puppetlabs.com repository but it won't install on my
systems as the CPU type isn't supported.
What are my options t
of the forge modules being usable easily out of the box, but it
solved the issue we had in categorising data within modules. Thought i
would mention our use case.
Jon
On Friday, 11 October 2013 19:09:23 UTC+1, Eric Sorenson wrote:
>
>
> Thanks to everyone who kicked the tires on the ex
to populate those parameters. AFAIK,
there's no interoperability between Foreman's ENC and Hiera (without
writing my own).
Jon
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and st
uot;foo::bar"]
}
On Friday, November 15, 2013 5:27:11 PM UTC-5, jcbollinger wrote:
>
>
>
> On Friday, November 15, 2013 10:08:54 AM UTC-6, Jon McKenzie wrote:
>>
>> Has anyone run into this issue before?
>> http://projects.puppetlabs.com/issues/5046#note-17
>>
Has anyone run into this issue before?
http://projects.puppetlabs.com/issues/5046#note-17
Is there something obvious that I'm missing?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails fro
Ashley,
Thanks for reporting the solution. I was just struggling with the same odd
behavior. My setup automatically inserts "puppet managed" comments at the
top of all templates, but this breaks init scripts (at least in Debian).
Jon
=====
Jon Jaroker
http://jaroker.com
Ah that's working perfectly now, thanks so much for your time.
Yep, I will update my Puppet scripts to install the deb packages going
forward.
Jon
On Thursday, July 11, 2013 11:01:33 AM UTC+1, R.I. Pienaar wrote:
>
>
>
> - Original Message -----
> > From: "
from /usr/bin/mco:20
On Thursday, July 11, 2013 10:43:43 AM UTC+1, R.I. Pienaar wrote:
>
>
>
> - Original Message -
> > From: "Jon Ward" >
> > To: puppet...@googlegroups.com
> > Sent: Thursday, July 11, 2013 10:37:00 AM
> > Subject
ator, aggregate and agent dirs
on both nodes, and the application dir on the client node.
Thanks,
Jon
On Wednesday, July 10, 2013 10:40:23 PM UTC+1, R.I. Pienaar wrote:
>
>
>
> ----- Original Message -
> > From: "Jon Ward" >
> > To: puppet...@googlegrou
*
>
So it seems that it thinks all the nodes are disabled. However other
actions such as "enable" and "disable" work correctly, and "runonce"
correctly determines which nodes are enabled.
I've had a dig around the code but got completely lost so any poi
Has there been any advancement with this bug?
On Friday, May 31, 2013 2:53:30 PM UTC-4, Trevor Vaughan wrote:
>
> This sounds like the other side of the coin to a bug that I filed:
> https://projects.puppetlabs.com/issues/19414
>
> Not being able to add AD/LDAP users to a local group is a fail.
>
On Fri, Jun 7, 2013 at 4:45 PM, Kenneth Edgar wrote:
>Protected multilib versions: libselinux-2.0.94-5.3.el6.i686 !=
> libselinux-2.0.94-5.3.el6_4.1.x86_64
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
Basically this
I am using the MSSQL server module from puppet as a baseline for the
installation of SQL Server 2012, and am running into issues durring the
install. It gets a lot of the way done, and issues this error:
Error: \\puppet\installs\SQLServer2012SP1\setup.exe
/CONFIGURATIONFILE=C:\sql201
2.config.ini
Now when you run puppet you should see the Hiera lookups happening as the
catalog is compiled, this might help you pinpoint the problem..
On Friday, May 10, 2013 3:46:28 PM UTC+1, Jonathan Gazeley wrote:
>
> Hi Jon,
>
> Thanks for your tip. I had made a typo in my yaml which debug
>
> If you use many parameterized classes, then Puppet 3's automatic class
> parameter binding will tend to aggravate that problem, especially if you
> typically allow class parameters to take default values or DSL-specified
> values (so that hiera has lots of complete misses on the parameter n
Hi,
Have you tried doing the Hiera lookup on the command line to double check
it can be read?
$ hiera -d -c /path/to/hiera.yaml jrs_config_server1 fqdn=hostname
>
Cheers,
Jon
On Friday, May 10, 2013 12:18:22 PM UTC+1, Jonathan Gazeley wrote:
>
> Hi,
>
> I'm having a pro
On Tue, Mar 19, 2013 at 6:03 PM, Steffen Vulpius
wrote:
> I have a file foo.sh which is basically a library of various bash functions.
> Is there a way to execute these functions from puppet
Correct me if I'm wrong, but you have a file foo.sh, that defines a
bash function called bar, and you wan
Using 2.6.17, I have something like this:
class yumrepos {
yumrepo { ['a',
'b']:
descr=>"yum repo $name",
baseurl=>"http://someurl/$name";;
}
}
Instead of using the names 'a' and 'b', like I'd expect (so a baseurl
of http://someurl/a), it creates .repo fil
Ah I missed that, thanks Craig.
On Thursday, February 21, 2013 12:43:12 PM UTC, Jon Ward wrote:
>
> Hi,
>
> I've been trying to debug my slow Puppet runs since using hiera-gpg (
> https://groups.google.com/d/topic/puppet-users/CRu_RolrX_8/discussion)
> and found
without it doing a hiera lookup?
This seems to have quite a major impact on my catalog compile time once I
add the gpg backend.
Cheers,
Jon
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop
s for debugging this problem, thanks in advance.
Jon
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to th
Brown wrote:
> > > It's probably easier in the long run to work out what that script does
> > > and replicate those settings in your samba puppet class.
>
> > > On 4 October 2012 19:34, Jon Skarpeteig wrote:
>
> > > > I'm trying to automate deploym
he long run to work out what that script does
> and replicate those settings in your samba puppet class.
>
> On 4 October 2012 19:34, Jon Skarpeteig wrote:
>
>
>
>
>
>
>
> > I'm trying to automate deployment of centrify-samba, which has a
> > adbindproxy
I'm trying to automate deployment of centrify-samba, which has a
adbindproxy.pl setup script attached. This script expects user input
(where 9 out of 10 options can be defaulted). Is there any way for
Puppet to preconfigure the inputs for this scripts, and mimic user
behavior by supplying this info
On Mon, Oct 1, 2012 at 12:33 PM, Douglas Garstang
wrote:
> I'm trying to find email addresses of some of the speakers from Puppet
> Conf last week. They aren't on the web site... maybe due to spamming
> concerns. Short of Googling, how can I get these?
I was a speaker, and you now have my email
Could you try changing your if statement to:
if $server_role =~ /app/
If that returns the result you want, it could be that you have an unwanted
newline character at the end of your fact value. (If that's the case a
little chomp in your fact code will sort you out.)
On Tuesday, September 25, 2
Thanks Bill - looks like concat provides a potential solution, will give
that a go.
Jon
On Tuesday, September 25, 2012 1:50:39 PM UTC+1, Bill Fraser wrote:
>
> Hi Jon,
>
> I have seen something similar done with Puppet Labs' haproxy module:
>
> https://github.com/puppet
not allowed here
A bit of googling (e.g.
http://stackoverflow.com/questions/4165116/can-include-directive-be-used-within-upstream-block-of-nginx)
seemed to suggest it's not possible.
On Tuesday, September 25, 2012 12:47:37 PM UTC+1, Greg Sutcliffe wrote:
>
> On 25 September 2012 12
e moment, just
wondering if anyone else out there has had any success doing something like
this?
Thanks,
Jon
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/
it.
Adding
File
{
mode => 644,
}
to the class makes the problem go away but this really
isn't a solution.
Any ideas what might be causing this?
Cordially,
Jon Forrest
--
You received this message because you are subscribed to the Google Groups "Puppet
Users"
I'm writing a module in which nodes export a concat::fragment, collect all
other nodes' analogous resource, and populate a config file (in this case,
the krb5.conf for MIT Kerberos).
It seems that nodes are not able to collect their own resource, but they
can collect every other resource, with
Hi Dan,
Thanks for the input. If I were to implement this in the provider, what
would be the proper way to do that? Is there a validation/conversion hook I
can override?
On Sunday, September 9, 2012 1:55:17 PM UTC-4, Dan Bode wrote:
>
>
>
> On Sun, Sep 9, 2012 at 10:46 AM,
I restarted my puppetmaster and this seemed to resolve the issue. Very
strange message, though. I suppose if I've defined a new type, but haven't
restarted puppetmaster it throws a message like this? I will need to test
that though
On Sunday, September 9, 2012 4:16:53 PM UTC-4, Jo
1 - 100 of 185 matches
Mail list logo
