I guess you're left with doing exec. Something like this should work:
exec { 'ruby193_scl_install_blah':
command = scl enable ruby193 'gem install --bindir /usr/bin --no-rdoc
--no-ri blah',
path= ['/bin','/usr/bin'],
unless = scl enable ruby193 'gem list'| grep -qs
On Wed, Jul 22, 2015 at 3:01 AM, Federico Agnelli fagne...@gmail.com
wrote:
Hi Peter,
attached you can find the output of dmidecode and another file with the
output of the cat command.
It looks like, for whatever reason, those values were set by the
manufacturer to 0xFF 0xFF 0xFF ...
Puppet-Community [1] would be a prime example to take over the maintainership.
[1] https://github.com/puppet-community/ https://github.com/puppet-community/
Tom
On 13 Jul 2015, at 15:45, Erik Dalén erik.gustav.da...@gmail.com wrote:
Yeah, I'm not really using puppet server (yet at least) or
When I get a vague failure, such as expect File[/whatever] to be in the
catalog and don't know why it's not, I put a pry in the `it` block before
the test failure and re-run. It will drop you into a pry prompt and you can
inspect the catalog manually by running `catalogue` and look for anything
Thanks to you Peter!
Bye,
Fede
Il giorno mercoledì 22 luglio 2015 17:26:55 UTC+2, Peter Huene ha scritto:
On Wed, Jul 22, 2015 at 3:01 AM, Federico Agnelli fagn...@gmail.com
javascript: wrote:
Hi Peter,
attached you can find the output of dmidecode and another file with the
output of
I am attempting to use the following module
--
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 view this discussion on
Given we've discovered a bug in 3.7.5 and have recalled it for an incorrect
version of Ruby[1], it's possible this issue was limited to just Puppet
3.7.5. Registry could be one thing that would likely have a large effect
given the amount of changes we put in to make registry work again on Ruby
Hi Peter,
attached you can find the output of dmidecode and another file with the
output of the cat command.
Thanks,
Federico
Il giorno lunedì 20 luglio 2015 22:24:18 UTC+2, Peter Huene ha scritto:
On Monday, July 20, 2015 at 1:23:20 PM UTC-7, Peter Huene wrote:
On Monday, July 20, 2015
The puppet_agent module 0.2.0 is available.
The puppet_agent module is intended to ease the transition of agents from
Puppet 3.8 to Puppet 4 (using the puppet-agent package). It works with both
master and master-less setups, but expects your existing Puppet
installation to be installed via
On Wednesday, July 22, 2015 at 4:06:51 PM UTC-5, Kevin Corcoran wrote:
We added a new feature in Puppet Server 2.1.0 which allows it to be used
with Puppet 3 agents (as well as Puppet 4 agents, of course).
On Tue, Jul 21, 2015 at 9:33 AM, Felix Frank
felix.fr...@alumni.tu-berlin.de wrote:
On 07/21/2015 04:14 PM, jcbollinger wrote:
2)
I read in the changelog that the older clients should work with the
backward compatibility, but is it worth even trying? Or should I just push
out the updated
On 07/22/2015 11:06 PM, Kevin Corcoran wrote:
Hi,
We added a new feature in Puppet Server 2.1.0 which allows it to be
used with Puppet 3 agents (as well as Puppet 4 agents, of course).
https://docs.puppetlabs.com/puppetserver/latest/release_notes.html#whats-new-in-puppet-server-21
- Kevin
Hi Felix,
I tried to reproduce your problem on a fresh Debian 7 VM, but couldn't.
Have you been running the agent on this machine? If so, I suspect you're
hitting this issue: https://tickets.puppetlabs.com/browse/SERVER-528
Cheers,
- Kevin
--
You received this message because you are
I’m happy to announce the next All-in-One Puppet Agent release! This
release includes new versions of Facter and Puppet, and is now downloadable
through the Puppet Collection 1 repository.
-
Facter 3.0.2 fixes several regressions in Facter 3.0.0 and implements
new features to support
So, I'm going through the dance of upgrading to puppet 4.2 from 3.8 on
CentOS 6, and I've run into a few things that brought up some questions.
During the install, I ran into a number of collisions and incompatibilities
between pc1 and the existing packages, but pertinent to this issue, I had
Hello Rene,
Can you help me in setting up High availability for my puppet master, can
you share any doc that will help me
--
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,
16 matches
Mail list logo
