Jira (PDB-3565) PuppetDB module needs updated for Puppet 5 platform (requires PostgreSQL 9.6)
Title: Message Title
Doug Rosser created an issue
PuppetDB / PDB-3565
PuppetDB module needs updated for Puppet 5 platform (requires PostgreSQL 9.6)
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/06/16 2:25 PM
Priority:
Normal
Reporter:
Doug Rosser
Out of the box, a user attempting to use the PuppetDB module from the forge (https://forge.puppet.com/puppetlabs/puppetdb) will hit an error applying the catalog stating, "PostgreSQL 9.6 is required".
Workaround is to add the Postgres yum repository at https://yum.postgresql.org/repopackages.php (so Postgres96 can be found) and add the following to their manifest/module:
class { 'puppetdb':
postgres_version => '9.6'
}
Jira (PUP-4192) puppet master help grabs port 8140 and doesn't let go until you kill it
Title: Message Title Doug Rosser commented on PUP-4192 Re: puppet master help grabs port 8140 and doesn't let go until you kill it Confirmed this still occurs with whatever puppet server ships with 2017.1.X Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4182) add a flag to get JSON output from puppet resource
Title: Message Title Doug Rosser updated an issue Puppet / PUP-4182 add a flag to get JSON output from puppet resource Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6648) Puppet 4.6.x breaks catalog.apply in unit tests
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6648 Puppet 4.6.x breaks catalog.apply in unit tests Change By: Doug Rosser Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6648) Puppet 4.6.x breaks catalog.apply in unit tests
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6648 Puppet 4.6.x breaks catalog.apply in unit tests Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6624) File resource with source=http:// not updating on url change
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6624 File resource with source=http:// not updating on url change Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6614) Puppet 4.6.0 Error transactionstore is corrupt
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6614 Puppet 4.6.0 Error transactionstore is corrupt Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6610) macro expansion in hostname
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6610 macro expansion in hostname Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Doug Rosser commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Stephano Zanzin Were you able to reproduce the issue running the agents as daemons? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Doug Rosser assigned an issue to Stephano Zanzin Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Change By: Doug Rosser Assignee: Doug Rosser Stephano Zanzin Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Doug Rosser assigned an issue to Doug Rosser Puppet / PUP-6609 After a Debian puppet package upgrade, parameter error persists on dashboard Change By: Doug Rosser Assignee: Doug Rosser Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6587) `puppet module search --render-as json` returns non-JSON first line on stdout
Title: Message Title Doug Rosser commented on PUP-6587 Re: `puppet module search --render-as json` returns non-JSON first line on stdout See PUP-7408 for another example of logging corrupting json output (look for "puppet master --compile ") Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6583) `puppet module generate` does not honor `--modulepath` on the command line
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6583 `puppet module generate` does not honor `--modulepath` on the command line Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6583) `puppet module generate` does not honor `--modulepath` on the command line
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6583 `puppet module generate` does not honor `--modulepath` on the command line Change By: Doug Rosser Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6569) Improve error messaging for Windows user management
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6569 Improve error messaging for Windows user management Change By: Doug Rosser Labels: triaged type_user windows Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6562 Limit transaction.failed_dependencies? verbosity Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6562 Limit transaction.failed_dependencies? verbosity Change By: Doug Rosser Sub-team: Performance Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Doug Rosser assigned an issue to Doug Rosser Puppet / PUP-6562 Limit transaction.failed_dependencies? verbosity Change By: Doug Rosser Assignee: Doug Rosser Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6528) cron type ignores noop option
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6528 cron type ignores noop option Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6528) cron type ignores noop option
Title: Message Title Doug Rosser commented on PUP-6528 Re: cron type ignores noop option Attempted to repro puppet-agent-1.9.3-1.el7.x86_64. Applying the test code did not result in an entry to root's crontab. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6517) undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6517 undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source Change By: Doug Rosser Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6517) undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source
Title: Message Title Doug Rosser assigned an issue to Unassigned Puppet / PUP-6517 undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source Change By: Doug Rosser Assignee: Kylo Ginsberg Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6517) undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source
Title: Message Title Doug Rosser commented on PUP-6517 Re: undefined method `backtrace' for Puppet::Error:Class with package with unresolvable source Verified this still gives an ugly backtrace, but it's not the same exact error as in the description. (puppet-agent-1.9.3-1.el7.x86_64 ) Debug: Facter: resolving Xen facts. Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Error: Evaluation Error: Error while evaluating a Resource Statement, Unknown resource type: 'ckage' at /root/package-test.pp:1:1 on node fldr-agent-01.us-west-2.compute.internal /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_resource_support.rb:31:in `create_resources' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/evaluator/runtime3_support.rb:321:in `create_resources' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:842:in `block in eval_ResourceExpression' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/evaluator/evaluator_impl.rb:839:in `map'
Jira (PUP-6516) support the same service name in resources with multiple providers
Title: Message Title Doug Rosser updated an issue Puppet / PUP-6516 support the same service name in resources with multiple providers Change By: Doug Rosser Labels: manage-service triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1940) Reveal client IP address to autosign script.
Title: Message Title Doug Rosser commented on PUP-1940 Re: Reveal client IP address to autosign script. Host IP addresses are more difficult to to "spoof" but should not be considered secure. Auto-signing will always be a security compromise. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7408) Declaring a resource on a huge list causes an error
Title: Message Title Doug Rosser commented on PUP-7408 Re: Declaring a resource on a huge list causes an error Cleaned up the json file. I get the same error as from a regular puppet run. [root@glsn-agent-01 ~]# puppet apply --debug --catalog glsn-agent-01.take2.json Debug: Runtime environment: puppet_version=4.10.0, ruby_version=2.1.9, run_mode=user, default_encoding=UTF-8 Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Failed to load library 'msgpack' for feature 'msgpack' Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing Debug: catalog supports formats: pson yaml dot binary Debug: Facter: searching for custom fact "osfamily". Debug: Facter: searching for osfamily.rb in /opt/puppetlabs/puppet/cache/lib/facter.
Jira (PUP-7408) Declaring a resource on a huge list causes an error
Title: Message Title Doug Rosser commented on PUP-7408 Re: Declaring a resource on a huge list causes an error The file is 150MB, so I've put a copy at http://int-resources.ops.puppetlabs.net/drosser/glsn-agent-01.us-west-2.compute.internal.json Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7408) Declaring a resource on a huge list causes an error
Title: Message Title Doug Rosser commented on PUP-7408 Re: Declaring a resource on a huge list causes an error Henrik Lindberg Results below, but it looks like the catalog compiled successfully on the master, although the agent was unable to apply it. [root@glsn-mom ~]# puppet master --compile glsn-agent-01.us-west-2.compute.internal > glsn-agent-01.us-west-2.compute.internal.json Warning: Unknown variable: '::pe_server_version'. at /etc/puppetlabs/code/environments/production/manifests/site.pp:13:4 Warning: /etc/puppetlabs/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 (in /etc/puppetlabs/puppet/hiera.yaml) Warning: This method is deprecated, please use the stdlib validate_legacy function, with Stdlib::Compat::Bool. There is further documentation for validate_legacy function in the README. (at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:19:in `deprecation') Warning: This method is deprecated, please use match expressions with Stdlib::Compat::String instead. They are described at https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match-expressions. (at /etc/puppetlabs/code/environments/production/modules/stdlib/lib/puppet/functions/deprecation.rb:19:in `deprecation')
Jira (PUP-7408) Declaring a resource on a huge list causes an error
Title: Message Title Doug Rosser commented on PUP-7408 Re: Declaring a resource on a huge list causes an error And unfortunately, the workaround above does NOT work. I hit the same error, it just takes longer to hit it. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7408) Declaring a resource on a huge list causes an error
Title: Message Title
Doug Rosser updated an issue
Puppet / PUP-7408
Declaring a resource on a huge list causes an error
Change By:
Doug Rosser
Following code:https://github.com/puppetlabs/clamps/blob/ iterate_test master /manifests/agent.pp#L37Works fine with about 3000 items in the list, but hits the following error at 4000:{noformat}[root@glsn-agent-01 ~]# puppet agent -t --traceInfo: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: Could not run: stack level too deep/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:434{noformat}Workaround in Puppet 4 is to use an iterator, like{noformat} $nonroot_usernames.each |$name| { ::clamps::users { $name:servername => $master,ca_server => $ca,metrics_server => $metrics_server,metrics_port => $metrics_port,daemonize => $daemonize,splay => $splay,splaylimit => $splaylimit, } }{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7408) Declaring a resource on a huge list causes an error
Title: Message Title Doug Rosser created an issue Puppet / PUP-7408 Declaring a resource on a huge list causes an error Issue Type: Bug Assignee: Unassigned Created: 2017/03/29 3:39 PM Priority: Normal Reporter: Doug Rosser Following code: https://github.com/puppetlabs/clamps/blob/iterate_test/manifests/agent.pp#L37 Works fine with about 3000 items in the list, but hits the following error at 4000: [root@glsn-agent-01 ~]# puppet agent -t --trace Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin
Jira (PDB-3241) Tests failing with "Maximum of 5000 keypairs reached"
Title: Message Title Doug Rosser commented on PDB-3241 Re: Tests failing with "Maximum of 5000 keypairs reached" I am going through the ESO-Puppetlabs AWS console and deleting every keypair with "2015" in the name. This should clear up some space. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3241) Tests failing with "Maximum of 5000 keypairs reached"
Title: Message Title Doug Rosser commented on PDB-3241 Re: Tests failing with "Maximum of 5000 keypairs reached" Looks like Beaker (wrapping the ruby AWS::SDK) is creating a new keypair with every run. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3231) A query in Everett is using too much cpu
Title: Message Title Doug Rosser created an issue PuppetDB / PDB-3231 A query in Everett is using too much cpu Issue Type: Bug Affects Versions: PDB 4.2.5 Assignee: Unassigned Created: 2016/12/14 9:54 AM Priority: Normal Reporter: Doug Rosser See PERF-135 for details but the query introduced with https://github.com/puppetlabs/puppetdb/commit/71cd8857bab89b40b1204e39bde621622c4ff004/src/puppetlabs/puppetdb/scf/storage.clj#diff-0 is taking up considerably more CPU than prior releases. Comparing the latest Davis Z release with the pre-release version of Everett I am testing, PostgreSQL in Everett is taking around 4-5 times more CPU. Upon Wyatt Alt's advice, I installed pg_stat_statements and found the query. Add Comment
Jira (PDB-2985) Fix excessive CPU usage by clj-i18n
Title: Message Title Doug Rosser commented on PDB-2985 Re: Fix excessive CPU usage by clj-i18n Any word of how to repro? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2947) Review "events" fix for Davis
Title: Message Title Doug Rosser created an issue PuppetDB / PDB-2947 Review "events" fix for Davis Issue Type: Task Assignee: Doug Rosser Created: 2016/08/09 2:07 PM Priority: Normal Reporter: Doug Rosser https://tickets.puppetlabs.com/browse/PE-16383 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title
Doug Rosser commented on PUP-3829
Re: pip package provider is broken on EL (where osfamily is RedHat)
Hrmmm. I could rely on the workaround for now, but even that doesn't seem to work...
[root@rc-metrics ~]# ls -l /usr/bin/python-pip
lrwxrwxrwx. 1 root root 12 Apr 6 20:46 /usr/bin/python-pip - /usr/bin/pip
[root@rc-metrics ~]# puppet apply -e 'package {s3cmd: ensure = installed, provider=pip}'
Notice: Compiled catalog for rc-metrics.us-west-2.compute.internal in environment production in 0.28 seconds
Error: Could not set 'present' on ensure: Could not locate the pip command. in 1
Error: Could not set 'present' on ensure: Could not locate the pip command. in 1
Wrapped exception:
Could not locate the pip command.
Error: /Stage[main]/Main/Package[s3cmd]/ensure: change from absent to present failed: Could not set 'present' on ensure: Could not locate the pip command. in 1
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Doug Rosser commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) Sorry I didn't make it clear. Pip is definitely installed. [root@rc-metrics ~]# which pip /usr/bin/pip [root@rc-metrics ~]# pip --version pip 1.5.6 from /usr/lib/python2.7/site-packages (python 2.7) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title
Doug Rosser commented on PUP-3829
Re: pip package provider is broken on EL (where osfamily is RedHat)
From looking at the code of the provider at /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/provider/package/pip.rb, we're looking for pip-python and not python-pip
[root@rc-metrics opt]# ln -s /usr/bin/pip /usr/bin/pip-python
[root@rc-metrics opt]# pip-python --version
pip 1.5.6 from /usr/lib/python2.7/site-packages (python 2.7)
[root@rc-metrics opt]# puppet apply -e 'package {s3cmd: ensure = installed, provider=pip}'
Notice: Compiled catalog for rc-metrics.us-west-2.compute.internal in environment production in 0.26 seconds
Notice: /Stage[main]/Main/Package[s3cmd]/ensure: created
Notice: Finished catalog run in 2.15 seconds
Add
