On Saturday, April 26, 2014 11:05:50 AM UTC-7, JonY wrote:
>
> I think I'm past that version already:
>
> # rpm -qa | grep puppet
> puppetdb-1.6.3-1.el6.noarch
> puppet-3.5.1-1.el6.noarch
> puppet-server-3.5.1-1.el6.noarch
> vim-puppet-2.7.20-1.el6.rf.noarch
> puppetlabs-release-6-10.noarch
> pup
I think I'm past that version already:
# rpm -qa | grep puppet
puppetdb-1.6.3-1.el6.noarch
puppet-3.5.1-1.el6.noarch
puppet-server-3.5.1-1.el6.noarch
vim-puppet-2.7.20-1.el6.rf.noarch
puppetlabs-release-6-10.noarch
puppetdb-terminus-1.6.3-1.el6.noarch
On Saturday, April 26, 2014 7:44:43 AM UTC-7
And... the following module has not been updated for Ubuntu 'Trusty' (i.e.)
14.04 as well...
/etc/puppet/modules/java/manifests/params.pp
On Tuesday, April 22, 2014 8:05:18 PM UTC-7, Schorschi Decker wrote:
>
> New to Puppet, but long term Linux user (CentOS, RHEL, Ubuntu, Debian - on
> Raspbe
Felix,
Actually looking at that page and other examples via Google is what
suggested the 'test' directory should exist. There seems to be a quite a
few examples of how to install razor that all point to the same step, that
does not appear to be correct.
David,
I don't see any example of how
On 04/25/14 16:14, jcbollinger wrote:
> On Thursday, April 24, 2014 7:35:10 PM UTC-5, Joachim Schrod wrote:
>
> I have a service where there is one server in my net and many
> clients (actually, all systems are clients): CUPS. In client
> setups, one file has to be changed (client.conf
On 04/25/14 14:34, Felix Frank wrote:
> That'll work, and not at all a bad design choice. But the parameterised
> cups wrapper class is ultimately unnecessary - you can just have all
> nodes include cups::client and make sure that the server(s) also include
> cups::server in a fashion that suits yo
Sorry, the URL for the Puppet bug is really here:
https://tickets.puppetlabs.com/browse/PUP-1524
On Sat, Apr 26, 2014 at 3:44 PM, Ken Barber wrote:
> It sounds like this Puppet bug: https://tickets.puppetlabs.com/browse/PDB-349
>
> You can usually solve this by upgrading to Puppet 3.4.3.
>
> ken.
It sounds like this Puppet bug: https://tickets.puppetlabs.com/browse/PDB-349
You can usually solve this by upgrading to Puppet 3.4.3.
ken.
On Sat, Apr 26, 2014 at 3:39 PM, JonY wrote:
> FWIW: I tried to remove all the db files and restart in hopes of removing
> the constraint issue. It immedia
FWIW: I tried to remove all the db files and restart in hopes of removing
the constraint issue. It immediately came back so I'm assuming that this is
a bug in the version of puppetdb I have installed (1.6.3.1)
On Saturday, April 26, 2014 6:03:22 AM UTC-7, JonY wrote:
>
> It seems that puppetdb h
Hi All,
I am thinking of implementing Razor for ESX provisioning with existing
Puppet Open Source version.
I am new to Razor, and would like to have opinion on this.
Have anyone used Razor with Puppet Open Source, how is the experience ? Are
there any other options to Razor ?
Exploring phase
It seems that puppetdb has run itself into a corner. It starts (albeit
briefly) and then stops soon afterwards with this error:
2014-04-25 20:38:30,242 ERROR [command-proc-65] [puppetdb.command]
[6c141db1-eeac-4c3f-be08-d03e5f445a19] [store report] Retrying after
attempt 13, due to: java.sql.SQ
11 matches
Mail list logo
