[Puppet Users] Re: Puppetdb installed with puppetlabs/puppetdb migration 65 failing

Postgres versions released last Thursday June 20th contain a regression in the behavior of the ALTER TABLE statement that is causing this issue by preventing PuppetDB from initializing its database schema. A concise summary of the issue can be

[Puppet Users] Re: Trouble after Agent upgrade -- Error: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

A quick update on this one: With Patrick's help, we were able to re-produce the issue in AWS. The root cause appears to be that the Puppet::Provider class includes the Puppet::Util module, which also happens to have a Puppet::Util::Package sub-module. So, depending on the load order of

[Puppet Users] Re: Trouble after Agent upgrade -- Error: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

Could you post the content of package_provider.rb? Since that is in cache/lib/facter, it is a custom fact and the specifics of its implementation could shed some light on what is happening. -Charlie On Thursday, June 20, 2019 at 1:53:34 PM UTC-7, Patrick Whitney wrote: > > Hello Everyone, > >

[Puppet Users] Re: Install puppet 4.0 on centos 7?

On Wednesday, October 14, 2015 at 6:18:33 PM UTC-5, anton kropp wrote: > > I feel like I'm missing something super obvious here but I'm trying to > install puppet 4.0 on centos 7 and the only packages i can see are 3.8.3. > When I check the repo https://yum.puppetlabs.com/el/7/products/x86_64/

[Puppet Users] Re: Puppet Agent broken on OS X (Yosemite w/ Ruby 2.2.0)?

On Tuesday, March 24, 2015 at 11:42:57 AM UTC-7, Joaquin Menchaca wrote: $ ruby --version ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin14] $ puppet --version /Users/vagrant/.rvm/gems/ruby-2.2.0/gems/puppet-3.7.4/lib/puppet/defaults.rb:465: warning: duplicated key at line 466

[Puppet Users] Re: Puppet fails to run if ruby1.8 is not installed.

On Friday, April 4, 2014 12:40:44 PM UTC-7, Tom Poulton wrote: I was running into this problem as well so I ran: *sudo cp -r /usr/lib/ruby/site_ruby/1.8/* /usr/local/share/ruby/site_ruby/2.0/* /usr/local/share/ruby/site_ruby/2.0/ is part of the $LOAD_PATH so I figured why not stick the

[Puppet Users] Re: vagrant and reusing certs after destroy box

On Thursday, February 27, 2014 12:17:51 PM UTC-8, Johan De Wit wrote: Hi, The situation ; Whenever I bring up a vagrant box, I do a puppet run against my puppet master to configure some common things I need. And I want to avoid the remove/new request and sign cycle after a vagrant

[Puppet Users] Re: Hiera isn't merging hashes

On Wednesday, February 26, 2014 2:19:23 PM UTC-8, paul@complex.com wrote: I have been doing some experimenting with Puppet + Hiera with some of my hashes, but when it is going through my hierarchy it is returning whatever hash it hits first and skipping the others. For my node

[Puppet Users] Re: Puppet 3.4.0 name as an array in package

{['pkg1', 'pkg2']: ensure = present, } This won’t achieve the exact same effect, i.e. there will be multiple calls to yum, but it is pretty close for most use cases. Hope this helps! -- Charlie Sharpsteen Open Source Support Engineer Puppet Labs -- You received this message because you

[Puppet Users] Re: Projects.puppetlabs.com undergoing maintenance at 9PM PST

Let us know if you have any questions about the migration or if the ticket exporter on the old Redmine site does not appear to be working properly! -- Charlie Sharpsteen Open Source Support Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups

[Puppet Users] Re: Puppet Labs issue tracker migration 16 Dec 2013

the updates mailed out on a set schedule. More information can be found here: https://confluence.atlassian.com/display/JIRA061/Receiving+Search+Results+via+Email Updates for all platform projects are also being sent by JIRA to the puppet-bugs mailing list. -- Charlie Sharpsteen Open Source

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

significant activity for quite a while and so automatic issue migration will not be set up. For cases like this, we can discuss the status of the ticket on IRC in #puppet-dev. Let us know if you have any more questions! -- Charlie Sharpsteen Open Source Support Engineer Puppet Labs -- You received

Re: [Puppet Users] get a *structured* version of the puppet agent output

or the dashboard. Approach 3 works as well and offers a lot of control, but you will need to write a bit of code that extracts data from the catalog and report files before you can focus on the analysis. -- Charlie Sharpsteen Open Source Support Engineer Puppet Labs -- You received this message

[Puppet Users] Re: err: Could not send report: Error 400 on SERVER: (unknown): found character that cannot start any token while scanning for the next token

to send can usually be found in /var/lib/puppet/state/last_run_report.yaml --- this is the file that the line and column numbers relate to. Hope this is helpful! -- Charlie Sharpsteen Open Source Support Engineer Puppet Labs -- You received this message because you are subscribed to the Google

Re: [Puppet Users] get a *structured* version of the puppet agent output

-agent.puppetdebug.vlan} ] The power of PuppetDB in this situation is that your reporting script can now focus on analyzing the data instead of finding and then filtering it. Hope this helps! -- Charlie Sharpsteen Open Source Support Engineer Puppet Labs -- You received this message because you are subscribed

Re: [Puppet Users] Puppet Labs issue tracker migration 16 Dec 2013

. Or do I need to hold my horses? Thanks John Hi John, Updated documentation will be rolled out alongside public access to JIRA on the 16th. Account creation will be opened on that day as well. Let us know if you have any other questions about the migration! -- Charlie Sharpsteen Open Source