Sorry, its your agents that need to be upgraded not your master. Are
they all running 3.4.3 or greater?
On Sat, Apr 26, 2014 at 7:08 PM, JonY wrote:
>
>
> 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
>> puppe
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
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
