Seems that i'll try it with some structured facts read from
/etc/facter/facts.d/.
--
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
On Thursday, July 16, 2015 at 3:05:49 PM UTC-4, Hunter Haugen wrote:
A minimal use case shows that if $::operatingsystemmajrelease is undef
(puppet's idea of nil) then this will happen, because you can't compare
undef with comparators. (I include --trace just to show it really is the
On Friday, July 17, 2015 at 4:13:18 AM UTC-4, Ken Barber wrote:
I can run 'puppet resource package' on a node to get a list of installed
packages and version numbers.
are those version numbers available through a PuppetDB(2.3) API query?
We don't currently store the version of
I can run 'puppet resource package' on a node to get a list of installed
packages and version numbers.
are those version numbers available through a PuppetDB(2.3) API query?
We don't currently store the version of pre-existing/unmanaged
resources. If you define a version explicitly,
By the way: ruby.exe is missing from *C:\puppet\sys\ruby\bin*
Is this intended?
On Friday, July 17, 2015 at 2:59:34 PM UTC+2, cko wrote:
Hi all,
updating Puppet from 3.7.5 to 3.8.1 fails on all my Windows Server 2008R2
nodes.
I'm using the following code (puppet.pp):
*package {
Hi all,
updating Puppet from 3.7.5 to 3.8.1 fails on all my Windows Server 2008R2
nodes.
I'm using the following code (puppet.pp):
*package { 'Puppet':*
* ensure = 3.8.1,*
* source =
puppet\\puppetsamba\\puppet_agent\\windows\\puppet-3.8.1.msi,*
* provider=
On Friday, July 17, 2015 at 2:31:11 AM UTC-5, bjoern pohl wrote:
Hi,
we're currently transforming some ugly perl-based management scripts
(which placed some config data on the client and then configured something
with it) to puppet.
While it is definitely the best idea point to keep all
My windows team mentioned the same issue of not being able to upgrade the
agent because of a ruby issue.. I haven't had much time yet to go jump in
and help them, but this sounds exactly like what they reported.
Bummer.. I think i'll move them to the PC1 agent and Puppet 4.2 since
they're
Hi,
we're currently transforming some ugly perl-based management scripts (which
placed some config data on the client and then configured something with
it) to puppet.
While it is definitely the best idea point to keep all that config data on
the master ( using hiera, puppetdb, etc..) i am
I can run 'puppet resource package' on a node to get a list of installed
packages and version numbers.
are those version numbers available through a PuppetDB(2.3) API query?
We don't currently store the version of pre-existing/unmanaged
resources. If you define a version explicitly, that gets
I am facing same issue with 3.7.5 to 3.8.1 upgrade.
On 17-Jul-2015 7:04 pm, Byron Miller byr...@gmail.com wrote:
My windows team mentioned the same issue of not being able to upgrade the
agent because of a ruby issue.. I haven't had much time yet to go jump in
and help them, but this sounds
It appears in PE 3.8.1 there is puppetlabs/aws but nothing to replace
node_vmware functionality to provision vmware vm's. I cannot find a
module, am I missing something ?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this
Omen,
It looks like you've installed the gem into the agent's gem path
instead of the server's. Puppetserver's docs[1] have details on how to
install a gem for puppetserver.
However, ruby-ldap is a compiled gem that won't work with jruby, so
jruby-ldap is the gem you'd want to use on the server.
Em sexta-feira, 17 de julho de 2015 00:17:28 UTC-3, Ken Barber escreveu:
Hello list.
I'm trying to use PuppetDB to link a webserver cluster to an EJB
cluster.
Each webserver host need to reference a comma separated list of IPs
provided
by each EJB host
Exporting and
Quoting Matthaus Owens matth...@puppetlabs.com on Fri, Jul 17 09:55:
It looks like you've installed the gem into the agent's gem path
instead of the server's. Puppetserver's docs[1] have details on how to
install a gem for puppetserver.
So obvious when you point it out. Following the fine
When collecting virtual resources, is there a way to override them to *remove*
specific attributes?
For example, I have a set of service definitions with requires, and I want to
collect them without those. (It's rather more complicated than that, but
illustrates what I want to do.) Is this
TL;DR - the 2015 IT Monitoring Survey is closing shortly:
https://www.surveymonkey.com/s/monitoringsurvey2015.
The survey takes about 5 minutes to fill out and the results will again
be presented on my blog, in some conference talks and made available
as Creative Commons licensed data. The
Hi list,
I'm currently trying to get Puppet 4 to work with nginx/passenger. I had
that working with Puppet 3.x pretty well, but the new packaging stumps me.
For one, the config.ru file is no longer being packaged, apparently.
It's missing from my systems regardless of whether puppet-agent or
On 07/18/2015 03:20 AM, Tim Dunphy wrote:
Hey Felix,
thanks, but those aren't the important ones I'm afraid. There
should be
a vhost to bind port 8140. If there is not, please check carefully
which
process is actually listening on that port. (If it's Ruby, I have bad
Hey Ramin and Michael,
thanks for your replies.
On 07/17/2015 11:53 PM, Ramin K wrote:
I wrote a how-to on using different Rubies for your Puppet master and
am using it to run a Ruby 2.1.6/Puppet 3.7.x master. I would attempt
something similar in your case.
On Fri, Jul 17, 2015 at 6:51 PM, Felix Frank
felix.fr...@alumni.tu-berlin.de wrote:
Hey Ramin and Michael,
thanks for your replies.
On 07/17/2015 11:53 PM, Ramin K wrote:
I wrote a how-to on using different Rubies for your Puppet master and am
using it to run a Ruby 2.1.6/Puppet 3.7.x
Both of these methods seems to work on puppet 4, and you could try on
puppet 3:
@notify { 'one': before = Notify['two'], }
@notify { 'two': }
Notify | title == 'one' | {
before = undef,
}
OR
@notify { 'one': before = Notify['two'], }
@notify { 'two': }
Notify | title == 'one' | {
before =
On Fri, Jul 17, 2015 at 4:38 PM, Rob Reynolds r...@puppetlabs.com wrote:
On Fri, Jul 17, 2015 at 8:34 AM, Byron Miller byr...@gmail.com wrote:
My windows team mentioned the same issue of not being able to upgrade the
agent because of a ruby issue.. I haven't had much time yet to go jump in
For the AIO, you can certainly get passenger working. (Although we'd love
to hear why PuppetServer isn't working or what you want).
Config files on a gist:
https://gist.github.com/stahnma/cf89dfa79b053f138eb1
This should get you most of the way there. You might have to sub out
passenger
It was recently discovered that the following open source Puppet 3.7.5
releases on Windows from March 26, 2015 were mistakenly shipped with Ruby
2.1.6:
puppet-3.7.5.msi
puppet-3.7.5-x64.msi
Given compatibility against Ruby 2.1 is not tested until Puppet 4 series
releases, we are removing the 2
On Fri, Jul 17, 2015 at 8:34 AM, Byron Miller byr...@gmail.com wrote:
My windows team mentioned the same issue of not being able to upgrade the
agent because of a ruby issue.. I haven't had much time yet to go jump in
and help them, but this sounds exactly like what they reported.
Bummer..
On 07/17/2015 10:08 PM, Felix Frank wrote:
Hi list,
I'm currently trying to get Puppet 4 to work with nginx/passenger. I had
that working with Puppet 3.x pretty well, but the new packaging stumps me.
For one, the config.ru file is no longer being packaged, apparently.
It's missing from my
The ruby executable locking was likely exasperated by the wrong version of
ruby in 3.7.5 - we've yanked the 3.7.5 release[1] based on what we've
discovered this afternoon.
[1]
https://groups.google.com/forum/#!msg/puppet-dev/VtqadVFJKLM/e28O_so11fMJ
Hi,
this whole approach is hardly ideal. Try and take a look at the
file_line type in the stdlib module. It will likely do exactly what you
need.
https://github.com/puppetlabs/puppetlabs-stdlib#file_line
As soon as you install the stdlib module, the type becomes available to
your manifests.
On 07/17/2015 10:37 PM, Tim Dunphy wrote:
Hi Felix,
Thanks for getting back to me! And yes, you are correct.
Puppet/Foreman is running through apache/passenger.
And here's the vhost configurations. There's two of them, one for ssl
and one for non ssl. Non ssl is first:
Hi Tim,
thanks,
On 7/17/15 2:25 PM, Felix Frank wrote:
On 07/17/2015 10:08 PM, Felix Frank wrote:
Hi list,
I'm currently trying to get Puppet 4 to work with nginx/passenger. I had
that working with Puppet 3.x pretty well, but the new packaging stumps me.
For one, the config.ru file is no longer being
Hi,
I'm not very familiar with the puppet/foreman stack, so this might be a
silly question, but how is the master set up? Is it running through
Apache/Passenger?
In that case, can we see the Apache vhost configuration?
Thanks,
Felix
On 07/15/2015 05:12 AM, Tim Dunphy wrote:
Hey all,
I'm
Hi Felix,
Thanks for getting back to me! And yes, you are correct. Puppet/Foreman is
running through apache/passenger.
And here's the vhost configurations. There's two of them, one for ssl and
one for non ssl. Non ssl is first:
#
Hey Felix,
thanks, but those aren't the important ones I'm afraid. There should be
a vhost to bind port 8140. If there is not, please check carefully which
process is actually listening on that port. (If it's Ruby, I have bad
news and good news :-)
Whoops! OK I get you now. Here's the vhost
34 matches
Mail list logo
