Cool.
> On Dec 27, 2013, at 3:34 PM, Matthaus Owens wrote:
>
> Stuart,
> The rpms will install puppet into the load path of the system ruby for
> your platform. If you've installed a different ruby, then that new
> ruby won't be able to load libraries from your system ruby load path.
> For cust
Stuart,
The rpms will install puppet into the load path of the system ruby for
your platform. If you've installed a different ruby, then that new
ruby won't be able to load libraries from your system ruby load path.
For custom ruby use, the 3 main options are install from source,
install from a gem
Normal - via PL repo yum install.
I haven't reinstalled Puppet master and Puppet client for each Ruby
upgrade/downgrade.
On Friday, December 27, 2013 3:03:04 PM UTC-8, Matthaus Litteken wrote:
> Stuart,
> How have you installed puppet? Have you installed it for each ruby
> you're trying out?
Stuart,
How have you installed puppet? Have you installed it for each ruby
you're trying out?
On Fri, Dec 27, 2013 at 2:59 PM, Stuart Cracraft wrote:
> Tried ruby 2.0.0 but same:
>
> # /etc/init.d/puppetmaster start
>
> Starting puppetmaster:
> /usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_r
Tried ruby 2.0.0 but same:
# /etc/init.d/puppetmaster start
Starting puppetmaster:
/usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in
`require': cannot load such file -- pupp\
et/util/command_line (LoadError)
from
/usr/local/lib/ruby/2.0.0/rubygems/core_ext/kernel_re
Stuart, by doing a simple Google search I show from the release notes that
Puppet 3.2 added Ruby 2.0 support, but I see no mention of the addition of
Ruby 2.1 support.
My guess is that it's not been added.
Jeffrey.
On Fri, Dec 27, 2013 at 3:42 PM, Stuart Cracraft wrote:
>
> Has anyone else seen
Has anyone else seen this? ruby is 2.1.0 and puppet is 3.3.2.
# /etc/init.d/puppetmaster start
Starting
puppetmaster:
/usr/local/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in
`require': cannot load such file -- puppet/util/command_line (LoadError)
from
/usr/local/lib/
Hi all,
sometimes when I run an mco puppet runonce it fails with the error:
[root@puppet-master clientbucket]# mco puppet runonce -I client01
* [ > ] 1 / 1
client01 Request Aborted
Puppet command
Here
http://ttboj.wordpress.com/2013/06/04/collecting-duplicate-resources-in-puppet/
is
explained how to do the "trick" to be allowed to define several times the
same exported resource.
The basic idea is:
- Create a custom defined type to be exported
- That defined type should be exported al
I can confirm this. Same issue here.
On Thursday, December 26, 2013 1:54:33 PM UTC-5, Fabrice Bacchella wrote:
>
> When I upgrade a node with puppet 3.4.0, puppet-package is broken :
>
> ~$ mco package puppet status -I $(facter hostname) -v
>
> | [ >
Dear All,
Please help me if puppet agent installation is possible on hp unix os or
not.
If it is possible please tell how to installed it
Thanks and Regrads
Ankit Mittal
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from th
On Dec 26 10:56, Johan De Wit wrote:
> I use this one to set parameters for a define in my rspec
>
> let(:facts) { { :hostname => 'sambaserver' } }
>
> context 'default setting' do
> let(:params) { { :share_path => '/testpath/share' } }
> ...
> end
>
Thanks a bunch Johan, that gav
12 matches
Mail list logo