Jira (PUP-3427) Service type: new provider type for Pacemaker
Title: Message Title
Bogdan Dobrelya commented on an issue
Re: Service type: new provider type for Pacemaker
Charlie, I think you are right, we should use another approach for pacemaker provider and put it into some module instead of core functions. E.g. we could use some '::ha_linux { 'foo_service': provider => 'pacemaker' }
' definition in catalog in order to override given foo_service service by pacemaker control plane. Or use some 'include foo_service::pacemaker' class in order to as well extend its standard behavior by pacemaker specific one...
Add Comment
Puppet / PUP-3427
Service type: new provider type for Pacemaker
Puppet service type should be enhanced with Pacemaker provider type in order to allow Linux HA-stack operators to benefit from all features provided by OCF control plane for Pacemaker resources supported by Puppet transparently.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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...@g
Jira (PDB-950) PuppetDB returns 500 error as HTML when query contains invalid regex
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-950 PuppetDB returns 500 error as HTML when query contains invalid regex Change By: Kenneth Barber Sprint: PuppetDB 2014-11-05 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3447) self.instances is undocumented
Title: Message Title Igor Galić created an issue Puppet / PUP-3447 self.instances is undocumented Issue Type: Bug Assignee: Kylo Ginsberg Components: DOCS, Types and Providers Created: 13/Oct/14 6:18 AM Priority: Normal Reporter: Igor Galić https://docs.puppetlabs.com/references/latest/developer/Puppet/Provider.html contains no explanation of what self.instances is and how to use it. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3447) instances is undocumented
Title: Message Title
Igor Galić updated an issue
Puppet / PUP-3447
instances is undocumented
Change By:
Igor Galić
Summary:
self. instances is undocumented
https://docs.puppetlabs.com/references/latest/developer/Puppet/Provider.html contains no doesn't appear to have an explanation of what {{ self. instances}} is and how to use it.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3447) instances is undocumented
Title: Message Title
Igor Galić updated an issue
Puppet / PUP-3447
instances is undocumented
Change By:
Igor Galić
https://docs.puppetlabs.com/references/latest/developer/Puppet/Provider.html doesn't appear to have an explanation of what {{instances}} is and how to use it. update: it appears it's documented, but not rendered: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider.rb#L363-L392, thanks [~richard]
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3345) Puppet Master Memory Leak
Title: Message Title Henrik Lindberg commented on an issue Re: Puppet Master Memory Leak Kylo Ginsberg pointed out in email that: "There was discussion in PUP-2576 about whether to remove the warning or not, but that didn't reach a resolution. If the warning (or rather the facility to support the warning) is expensive, I'm inclined to remove it." The logic in question is only there to provide deprecation warnings, and the only current such deprecation is for purge of cron in "resources". There is no good mechanism to deprecate things in types atm. hence the somewhat odd construct with a class level method on a type that is checked by the Resource baseclass with a "respond_to?". Since the warning will not be issued in 4.0 I am inclined to remove the entire construct for 3.7. When we do need deprecation / validation of types it seems better to perform this as part of visiting / checking the catalog. Add Comment Puppet / PUP-3345 Puppet Master Memory Leak Starting with 3.7, the Puppet master process will allocate more and more memory until it is killed by the OOM process. This occurs in about 24 hours in our environment. The behaviour occurs in both Rack and WEBRick configurations. In the Rack configuration the four Rack processes will grow until killed. In WEBRick configuration the one puppet maste... This message was sent by Atlassian
Jira (PUP-3447) instances & mk_resource_methods is "undocumented" (not rendered)
Title: Message Title
Igor Galić updated an issue
Puppet / PUP-3447
instances & mk_resource_methods is "undocumented" (not rendered)
Change By:
Igor Galić
Summary:
instances & mk_resource_methods is " undocumented " (not rendered)
https://docs.puppetlabs.com/references/latest/developer/Puppet/Provider.html doesn't appear to have an explanation of what {{instances}} is and how to use it.update: it appears it's documented, but not rendered: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider.rb#L363-L392, thanks [~richard] update2: the same seems also to be true for {{mk_resource_methods}}: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider.rb#L419-L431
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Lee Lowder created an issue PuppetDB / PDB-953 Observed PuppetDB database connection leak Issue Type: Bug Affects Versions: 1.6.3 Assignee: Unassigned Created: 13/Oct/14 7:43 AM Labels: support Priority: Normal Reporter: Lee Lowder (This was reported by a customer) Yesterday I cutover from an old to a new PuppetDB infrastructure based on PuppetDB 1.6.3.1 in PE 3.3.1 (pe-puppetdb-1.6.3.1-1.el6.noarch). Not long after we cutover I experienced an issue which hadn't previously appeared in the old environment. The number of connections to the PostgreSQL backend (pe-postgresql-9.2.7-9.pe.el6.x86_64) continued to climb until we hit the maximum number of allowed connections in Postgres and PuppetDB (and the Console) were no longer able to make new connections and the environment ground to a halt. I did not see this behavior in any of my pre-cutover testing in the new environment so it may be only something occurs under sustained load, though it is possible it may have been there but gone unobserved. I have run a number of tests and I believe I have isolated the configuration setting responsible for the behavior. My tests point to "conn-lifetime" in PuppetDB's database.ini file as the culprit. The scenario I originally started with is that I had PuppetDB's database.ini file set with the following:
Jira (PUP-3448) Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
Title: Message Title Niranjan Hettiwatte created an issue Puppet / PUP-3448 Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Issue Type: Task Affects Versions: PUP 3.7.1 Assignee: Andy Parker Components: Modules Created: 13/Oct/14 8:07 AM Environment: Red Hat Enterprise Linux Server release 6.5 (Santiago) Kernel: 2.6.32-431.el6.x86_64 x86_64 Priority: Normal Reporter: Niranjan Hettiwatte We have installed puppet master v 3.7.1and client v 3.7.1. [root@pptmstr ~]# puppet config print modulepath Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1119:in `issue_deprecation_warning') /etc/puppet/modules:/usr/share/puppet/modules [root@pptmstr ~]# [root@pptmstr ~]# tree -L 2 -d /etc/puppet/modules /etc/puppet/modules
Jira (PUP-3448) Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
Title: Message Title Niranjan Hettiwatte updated an issue Puppet / PUP-3448 Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Change By: Niranjan Hettiwatte Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-620) (PR 2429) Add install_options to gem provider
Title: Message Title Jason Ashby commented on an issue Re: (PR 2429) Add install_options to gem provider Hi Charlie Sharpsteen, I'm still seeing the quoting issue on puppet 3.7.1. $ sudo puppet agent -t Notice: Ignoring --listen on onetime run Info: Retrieving pluginfacts Notice: /File[/var/lib/puppet/facts.d]/mode: mode changed '0755' to '2775' Info: Retrieving plugin Info: Loading facts Info: Loading facts Info: Caching catalog for foo.example.com Info: Applying configuration version '1413212488' Error: Execution of '/usr/bin/gem install --no-rdoc --no-ri sys-proctable "--http-proxy http://webproxy.example.com:8080"' returned 2: ERROR: Could not find a valid gem '"--http-proxy http://webproxy.example.com:8080"' (>= 0) in any repository
Jira (PDB-954) create acceptance tests for PDB fallback
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-954 create acceptance tests for PDB fallback Issue Type: New Feature Assignee: Unassigned Created: 13/Oct/14 8:46 AM Priority: Normal Reporter: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3448) Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
Title: Message Title Andy Parker assigned an issue to Charlie Sharpsteen Puppet / PUP-3448 Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Change By: Andy Parker Assignee: Andy Parker Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-954) create acceptance tests for PDB fallback
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-954 create acceptance tests for PDB fallback Change By: Wyatt Alt Sprint: PuppetDB 2014-10-22 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-954) create acceptance tests for PDB fallback
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-954 create acceptance tests for PDB fallback Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Rob Reynolds commented on an issue Re: ENC returned environment ignored when using directory environments Britt Gresham could just prefer my PR then... Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3302) Puppet resource broken when directory environments enabled
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3302 Puppet resource broken when directory environments enabled Change By: Britt Gresham Assignee: Britt Gresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2638) Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing
Title: Message Title Chun Du updated an issue Puppet / PUP-2638 Missing dependent directory from Puppet Agent install on Windows causing issues with resource graphing Change By: Chun Du QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3003) Windows MSI contains unneeded files
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-3003 Windows MSI contains unneeded files Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename Change By: Adrien Thebo Affects Version/s: PUP 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title Adrien Thebo commented on an issue Re: tool should generate code using the actual module name as the directory instead of username-modulename Merged into master in 953449b4; this should be released in Puppet 4.0. Add Comment Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename This is what currently happens [root@puppet modules]# puppet-module generate ghoneycutt-apache = Generating module at /etc/puppetlabs/puppet/modules/ghoneycutt-apache - ghoneycutt-apache ghoneycutt-apache/M... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://group
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename Change By: Adrien Thebo Reporter: redmine.exporter garrett honeycutt Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename Change By: Adrien Thebo Component/s: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3446) CertificateError when running tests with OpenSSL >= 1.0.1i
Title: Message Title Eric Sorenson commented on an issue Re: CertificateError when running tests with OpenSSL >= 1.0.1i Thanks for the bug report and patch! Pinging Adrien Thebo and/or Josh Cooper for review – we will be able to check this out at an upcoming PR Triage hangout. Add Comment Puppet / PUP-3446 CertificateError when running tests with OpenSSL >= 1.0.1i The :minimal_certificate stub in Puppet::Network::HTTP::RackREST does everything necessary to produce a valid test certificate except sign it. An unsigned certificate has empty signing algorithm fields, which is invalid ASN.1, although OpenSSL versions prior to 1.0.1i would accept this ASN.1 anyway. When these tests are run on OpenSSL 1.0.1i or newer, ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename Change By: Adrien Thebo Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-927) Is checklist current
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-927 Is checklist current Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-938) Update the downloads page
Title: Message Title Wyatt Alt assigned an issue to Unassigned PuppetDB / PDB-938 Update the downloads page Change By: Wyatt Alt Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-942) Update dujour for 2.2.1
Title: Message Title Wyatt Alt assigned an issue to Melissa Stone PuppetDB / PDB-942 Update dujour for 2.2.1 Change By: Wyatt Alt Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3244 ENC returned environment ignored when using directory environments Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3449) Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-3449 Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'. Issue Type: Bug Affects Versions: PUP 3.7.1 Assignee: Joshua Partlow Components: Server Created: 13/Oct/14 10:36 AM Fix Versions: PUP 3.7.2 Priority: Normal Reporter: Joshua Partlow There is a top scope variable named 'trusted' which is reserved by the compiler for the trusted data that the server gathers from the request's certificate. A node's facts are also made available as top scope variables during puppet execution, and if the node has a 'trusted' fact, either created by the user, or retrieved from a node terminus like PuppetDB which stores the trusted data collected by the master for that node as 'trusted', then an "Attempt to assign to a reserved variable name" error is raised by the compiler: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/parser/scope.rb#L629
Jira (FACT-684) EC2 facts unavailable
Title: Message Title Klaus Ethgen commented on an issue Re: EC2 facts unavailable I see the same problem and I was able to track it down. I run facter on boxes on openstack. Openstack uses kvm instead of xen. But in facter/ec2.rb confines only for xen. But this is not the only problem. facter/ec2/rest.rb defines the timeout to 0.2 seconds what is definitively to little time for openstack to respond. Changing this two thinks (removing the confine test and increasing the timeout) solves the problem. Add Comment Facter / FACT-684 EC2 facts unavailable Looks like [FACT-185|https://tickets.puppetlabs.com/browse/FACT-185] may have regressed in 2.2.0. I'm unable to retrieve ec2_* facts for an EC2 instance in VPC. Works fine in 2.1.0. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-3449) Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3449 Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'. Change By: Joshua Partlow Sprint: Platform 2014-10-15 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3003) Windows MSI contains unneeded files
Title: Message Title
William Hopper commented on an issue
Re: Windows MSI contains unneeded files
Note: the builds used for these tests were taken from http://builds.puppetlabs.lan/puppet/a235ab202b3ea9aba8bfe86caba883e3fbd2b9ba/artifacts/windows/ .
Functional review:
Verified in the following cases that the MSI installs and that `sc query puppet` reports that the STATE is RUNNING after installing the Puppet MSI:
Win 2008R2 x64 with x64 Puppet MSI
Win 2008R2 x64 with x86 Puppet MSI
Win 2008R2 x86 with x86 Puppet MSI
Also verified that in each of these cases, "INSTALLDIR\Puppet{facter,hiera,puppet}", none of the `spec`, `acceptance` or `ext` directories are present, except for hiera/ext which correctly contains hiera.yaml.
Thumbs up!
Add Comment
Puppet / PUP-3003
Windows MSI contains unneeded files
The windows MSI contains in the puppet directory: * acceptance * autotest * ext * man * spec * tasks * yardoc ... It doesn't seem like any of these should be in there.
Jira (PUP-3003) Windows MSI contains unneeded files
Title: Message Title William Hopper updated an issue Puppet / PUP-3003 Windows MSI contains unneeded files Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilati
Title: Message Title
Joshua Partlow commented on an issue
Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation.
Kenneth Barber So, over the weekend I setup a 3.4 master and an agent and had beaker loop the agent/agent_disable_lockfile.rb test against it, at runinterval 5m and 30m. The only failure I was able to reproduce was a contention for the agent lockfile, because the master also has a daemonized puppet agent, which would occasionally collide with the agent running via beaker. I could not reproduce whatever race for the node's facts is happening in the full acceptance run (and it is continuing to happen; one or two tests per pe acceptance run).
I've opened PUP-3449 to address stripping 'trusted' from the node's parameters so we avoid this issue when setting up the top scope.
As for the more perplexing question of how the 'trusted' fact is getting back into the node, I will see if I can create a second jenkins job tied to a test branch and add a setup step that will patch the master's indirection with some extra instrumentation around find/save so we can try and see where the facts are coming from when one of these tests fails in a full pe run.
In the meantime, I'll close this ticket 'won't fix'.
Add Comment
PuppetDB / PDB-949
Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation.
We are seeing some failures in the PE Puppet Acceptance Tests job where the nodes facts contain a 'trusted' parameter which is reserved and ends up failing when the compiler pulls the facts into scope. {noformat} s60whm7u1kz3zfm.delivery.puppetlabs.net (redhat6-64-1) 09:08:56$ env PATH="/opt/puppet/bin:${PATH}" RUBYLI
Jira (PUP-3444) .gitignore being ignored on puppet module build
Title: Message Title
Brandon High commented on an issue
Re: .gitignore being ignored on puppet module build
So, this is a silly solution that you shouldn't have to do, but try using `doc/**`. I should probably make a bug for that.
Add Comment
Puppet / PUP-3444
.gitignore being ignored on puppet module build
I have a .gitignore like so: {code} pkg/* sensu.komodoproject spec/fixtures Gemfile.lock .vagrant/* .yardoc doc {code} There is a symlink inside doc. When I run puppet module build I get: {code} Warning: Symlinks in modules are unsupported. Please investigate symlink doc/.git/config -> .git/config. Warning: Symlinks in modules are un...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3450) The module tool should embed and use the root CAs it cares about
Title: Message Title Josh Cooper created an issue Puppet / PUP-3450 The module tool should embed and use the root CAs it cares about Issue Type: Bug Assignee: Unassigned Components: PMT Created: 13/Oct/14 11:23 AM Labels: windows Priority: Normal Reporter: Josh Cooper Currently the module tool will use the default set of CA certs when making an SSL connection to the forge. However, this is very fragile, because it requires that: #. openssl `set_default_paths` is implemented for that platform (it's not for windows) #. the cacerts bundle is present and updated (it's not for windows and some versions of solaris) #. the forge SSL cert is issued by a well known CA (it may not be, especially when using an internal/private forge) This has lead to a number of issues like: OPS-3320 PUP-2365 OPS-4555 ENTERPRISE-190 PE-4699 We need to modify the module tool so that it initialize the SSL context with a set of trusted CAs. The most secure thing is to specify them in code. Specifying an external file is a possibility, but you have to be careful of file system permissions.
Jira (PUP-3450) The module tool should embed and use the root CAs it cares about
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3450 The module tool should embed and use the root CAs it cares about Change By: Josh Cooper Currently the module tool will use the default set of CA certs when making an SSL connection to the forge. However, this is very fragile, because it requires that:# . openssl `set_default_paths` is implemented for that platform (it's not for windows)# . the cacerts bundle is present and updated (it's not for windows and some versions of solaris)# . the forge SSL cert is issued by a well known CA (it may not be, especially when using an internal/private forge)This has lead to a number of issues like:OPS-3320PUP-2365OPS-4555ENTERPRISE-190PE-4699We need to modify the module tool so that it initialize the SSL context with a set of trusted CAs. The most secure thing is to specify them in code. Specifying an external file is a possibility, but you have to be careful of file system permissions. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-948) Java 8 Support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-948 Java 8 Support Change By: Kenneth Barber This looks like we need: * Packaging dependencies on more JDK 8 systems. * Potential to find JDK 8 in our JDK discovery functions in scripts and such * DONE - Unit testing in Jenkins for JDK 8 * Acceptance testing for JDK 8 (so finding a few distros that ships 8 for example) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-948) Java 8 Support
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-948 Java 8 Support Change By: Kenneth Barber This looks like we need:* Packaging dependencies on more JDK 8 systems.* Potential to find JDK 8 in our JDK discovery functions in scripts and such* DONE - Unit testing in Jenkins for Oracle JDK 8* Unit testing switch for OpenJDK 8* Acceptance testing for JDK 8 (so finding a few distros that ships 8 for example) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3121) Puppet module generate - dependency problem
Title: Message Title Fero kittler commented on an issue Re: Puppet module generate - dependency problem Rob Nelson: I've checked out your code and it seems, that it is fixed. Thanks! Add Comment Puppet / PUP-3121 Puppet module generate - dependency problem Puppet will generate module, which reports dependency problem when listed. Generate module: puppet module generate bla-bla Build module: puppet module build bla-bla Install module (It will correctly install stdlib dependency): puppet module install /root/bla-bla/pkg/bla-bla-0.1.0.tar.gz List modules (It will report missing dependency): [ro... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3444) .gitignore being ignored on puppet module build
Title: Message Title
James Turnbull commented on an issue
Re: .gitignore being ignored on puppet module build
That work-around works for me.
Add Comment
Puppet / PUP-3444
.gitignore being ignored on puppet module build
I have a .gitignore like so: {code} pkg/* sensu.komodoproject spec/fixtures Gemfile.lock .vagrant/* .yardoc doc {code} There is a symlink inside doc. When I run puppet module build I get: {code} Warning: Symlinks in modules are unsupported. Please investigate symlink doc/.git/config -> .git/config. Warning: Symlinks in modules are un...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3124) tool should generate code using the actual module name as the directory instead of username-modulename
Title: Message Title garrett honeycutt commented on an issue Re: tool should generate code using the actual module name as the directory instead of username-modulename Thank you! Add Comment Puppet / PUP-3124 tool should generate code using the actual module name as the directory instead of username-modulename This is what currently happens [root@puppet modules]# puppet-module generate ghoneycutt-apache = Generating module at /etc/puppetlabs/puppet/modules/ghoneycutt-apache - ghoneycutt-apache ghoneycutt-apache/M... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-955) PDB PE 3.4.x Affecting Bugs
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-955 PDB PE 3.4.x Affecting Bugs Issue Type: Epic Assignee: Unassigned Created: 13/Oct/14 11:28 AM Priority: Normal Reporter: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-953 Observed PuppetDB database connection leak Change By: Kenneth Barber Sprint: PuppetDB 2014-11-05 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Andy Parker assigned an issue to Rob Reynolds Puppet / PUP-3244 ENC returned environment ignored when using directory environments Change By: Andy Parker Assignee: Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Andy Parker commented on an issue Re: ENC returned environment ignored when using directory environments My "small extra changes" on top broke the ability of an agent to use an environment that only exists on the master. The acceptance tests caught this. I've opened PR 3187 to fix the problem. Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/grou
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Rob Reynolds commented on an issue Re: ENC returned environment ignored when using directory environments Merge 3187 into stable at e84edcb. Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3441) tagmail report processor should use ExecutionStub
Title: Message Title
Kevin Corcoran updated an issue
Puppet / PUP-3441
tagmail report processor should use ExecutionStub
Change By:
Kevin Corcoran
It's currently calling {{safe_posix_fork}}, which does not work on JRuby. Instead, it should go through the {{ExecutionStub}} ({{Puppet::Util::Execution . execute}})
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3441) tagmail report processor should use ExecutionStub
Title: Message Title
Kevin Corcoran updated an issue
Puppet / PUP-3441
tagmail report processor should use ExecutionStub
Change By:
Kevin Corcoran
It's currently calling {{safe_posix_fork}}, which does not work on JRuby. Instead, it should go through the {{ ExecutionStub }} ( - {{Puppet::Util::Execution.execute}} )
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3451) Puppet generates metrics that extend past 6 decimal places under some circumstances
Title: Message Title Zachary Stern created an issue Puppet / PUP-3451 Puppet generates metrics that extend past 6 decimal places under some circumstances Issue Type: Bug Affects Versions: PUP 3.4.3 Assignee: Unassigned Created: 13/Oct/14 12:24 PM Environment: RHEL 6.5 + PE 3.2.1 Master AIX 7.1 + PE 3.2.1 Agent Priority: Normal Reporter: Zachary Stern Puppet generally produces metrics that only extend to 6 decimal places inside of a report. You can verify this by turning on stored reports, performing a few puppet runs, and examining the reports. Note that all "metrics" extend to a precision of 6 decimal places. However, occasionally, this is not the case. We've seen two cases where runs produce reports with data like the following. values:
Jira (PUP-3451) Puppet generates metrics that extend past 6 decimal places under some circumstances
Title: Message Title Zachary Stern updated an issue Puppet / PUP-3451 Puppet generates metrics that extend past 6 decimal places under some circumstances Change By: Zachary Stern Labels: customer support Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3451) Puppet generates metrics that extend past 6 decimal places under some circumstances
Title: Message Title
Zachary Stern updated an issue
Puppet / PUP-3451
Puppet generates metrics that extend past 6 decimal places under some circumstances
Change By:
Zachary Stern
Puppet generally produces metrics that only extend to 6 decimal places inside of a report. You can verify this by turning on stored reports, performing a few puppet runs, and examining the reports.Note that all "metrics" extend to a precision of 6 decimal places.However, occasionally, this is not the case. We've seen two cases where runs produce reports with data like the following.{code} values: - - schedule - Schedule - 0.002184- - package - Package - 8.6160649- - schedo - Schedo - 0.238365- - mount - Mount - 0.006872- - "no" - "No" - 2.92048498- - file_line - "File line" - 0.016742- - file - File - 11.4921386- - vmo - Vmo - 0.606267- - usersec - Usersec - 1.211225- - exec - Exec - 4.037464{code}Note that some of the metrics extend past 6 decimal places.Normally, I can perform puppet runs all day , and never see decimal places go beyond 6.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 gr
Jira (PUP-3452) Replace deprecating type check in Puppet::Resource with more robust method of emitting deprecation warnings
Title: Message Title William Hopper created an issue Puppet / PUP-3452 Replace deprecating type check in Puppet::Resource with more robust method of emitting deprecation warnings Issue Type: Bug Affects Versions: PUP 3.7.1 Assignee: Unassigned Created: 13/Oct/14 12:30 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: William Hopper It was recently discovered that the check for deprecated resource types and type parameters in Puppet::Resource is contributing to a Puppet memory leak. The check creates a cache of non-deprecated types, and for types not in the cache calls the `deprecate_params` method to emit a warning if warranted. The code in question resides in lib/puppet/resource.rb, lines 190 and 245 - 251 It should be noted that this mechanism was put into place to create deprecation warnings for the cron purge parameter and was merged at commit 7d7b7017. That warning was removed as part of the Puppet 4 code removal effort at 7ce59ba3. As this is causing memory issues, we should remove it and implement a more robust way of deprecating resource types or type parameters. On the puppet-dev mailing
Jira (PUP-3452) Replace deprecated type check in Puppet::Resource with more robust method of emitting deprecation warnings
Title: Message Title William Hopper updated an issue Puppet / PUP-3452 Replace deprecated type check in Puppet::Resource with more robust method of emitting deprecation warnings Change By: William Hopper Summary: Replace deprecating deprecated type check in Puppet::Resource with more robust method of emitting deprecation warnings Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Here's a breakdown from 10/13: http://jenkins-enterprise.delivery.puppetlabs.net/job/PE%20Puppet%20Acceptance%20Tests/46/testReport/ label=beaker,layout=64mcd-32a-64a,platform=redhat6 tests/ssl.autosign_command.rb => NC-263 tests/ssl.certificate_extensions.rb => NC-263 label=beaker,layout=64mcd-32a-64a,platform=debian7 tests/agent.fallback_to_cached_catalog.rb => 400 Bad file descriptor label=beaker,layout=64mcd-32a-64a,platform=ubuntu1204 tests/environment.use_enc_environment_for_files.rb => PUP-3449/ PDB-949 label=beaker,layout=64mcd-32a-64a,platform=sles11 tests/node.check_woy_cache_works.rb => fail to curl pe-puppetserver in 120 attempts label=beaker,layout=64mcd-32a-64a,platform=debian6 tests/ssl.autosign_command.rb => NC-263 tests/ssl.certificate_extensions.rb => NC-263 tests/modules/upgrade.introducing_new_dependencies.rb => transient timeout reaching https://forgeapi.puppetlabs.com? label=beaker,layout=64mcd-32a-64a,platform=centos5 tests/ssl.autosign_command.rb => NC-263 tests/ssl.certificate_extensions.rb => NC-263 NC-263 is closed, but presumably not yet pulled into a ci-ready PE 3.4 build. Add Comment
Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Eric Thompson commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. re: label=beaker,layout=64mcd-32a-64a,platform=sles11 tests/node.check_woy_cache_works.rb when running on vcloud on sles11 i've seen it not be able to fetch node data during the agent run (but restarts the server fine) then today i ran on platform under sles11 and the test ran fine and passed. ran against pe_ver 3.4.0-rc1-1249-ged96f3f on sles11 now and it passes. yolrev9tw5bwzoa (sles11-64-1) 13:02:42$ curl -m 1 https://localhost:8140 Trying command 120 times. .. yolrev9tw5bwzoa (sles11-64-1) 13:03:05$ curl -m 1 https://localhost:8140 ostensibly successful. tests/node/check_woy_cache_works.rb passed in 77.80 seconds took maybe 20 tries to contact the server after restart, but works. seems flaky... Add Comment
Jira (PUP-3452) Remove check for deprecated types in Puppet::Resource
Title: Message Title William Hopper updated an issue Puppet / PUP-3452 Remove check for deprecated types in Puppet::Resource Change By: William Hopper Summary: Replace deprecated type Remove check for deprecated types in Puppet::Resource with more robust method of emitting deprecation warnings Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3345) Puppet Master Memory Leak
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3345 Puppet Master Memory Leak Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-956) PR (1117): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-956 PR (1117): Update release notes for PDB 2.2.1 release. - wkalt Issue Type: Task Assignee: Unassigned Created: 13/Oct/14 1:30 PM Labels: github Priority: Normal Reporter: gepetto-bot Update release notes for PDB 2.2.1 release. Author: Wyatt Alt <> Company: Github ID: wkalt Pull Request 1117 Discussion Pull Request 1117 File Diff Pull Request Description (webhooks-id: 890c68e6dc2a83e421d71f2cfe69737e)
Jira (PDB-956) PR (1117): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1117): Update release notes for PDB 2.2.1 release. - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/91/ Add Comment PuppetDB / PDB-956 PR (1117): Update release notes for PDB 2.2.1 release. - wkalt h2. Update release notes for PDB 2.2.1 release. * Author: Wyatt Alt <> * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1117 Discussion|https://github.com/puppetlabs/puppetdb/pull/1117] * [Pull Request 1117 File Diff|https://github.com/puppetlabs/puppetdb/pull/1117/files] h2. Pull Request Description (webhooks-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 th
Jira (PDB-956) PR (1117): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1117): Update release notes for PDB 2.2.1 release. - wkalt wkalt commented: @pljenkinsro retest this please Add Comment PuppetDB / PDB-956 PR (1117): Update release notes for PDB 2.2.1 release. - wkalt h2. Update release notes for PDB 2.2.1 release. * Author: Wyatt Alt <> * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1117 Discussion|https://github.com/puppetlabs/puppetdb/pull/1117] * [Pull Request 1117 File Diff|https://github.com/puppetlabs/puppetdb/pull/1117/files] h2. Pull Request Description (webhooks-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Rob Reynolds commented on an issue Re: ENC returned environment ignored when using directory environments Merged 3187 into stable at a327be7 Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3244) ENC returned environment ignored when using directory environments
Title: Message Title Rob Reynolds commented on an issue Re: ENC returned environment ignored when using directory environments Merged 3182 and 3187 into master at 321b208 Add Comment Puppet / PUP-3244 ENC returned environment ignored when using directory environments Where a puppet agent is configured to use the default environment (production) and one relies on an ENC to assign the environment correctly (puppet 3.x where the ENC should win), when using directory environments to match an environment that doesn't exist, the default configured environment wins and the node is given a catalog from 'production' rather tha... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3452) Replace check for deprecated types in Puppet::Resource with more robust method method of emitting deprecation warnings
Title: Message Title William Hopper updated an issue Puppet / PUP-3452 Replace check for deprecated types in Puppet::Resource with more robust method method of emitting deprecation warnings Change By: William Hopper Summary: Remove Replace check for deprecated types in Puppet::Resource with more robust method method of emitting deprecation warnings Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-956) PR (1117): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1117): Update release notes for PDB 2.2.1 release. - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/92/ Add Comment PuppetDB / PDB-956 PR (1117): Update release notes for PDB 2.2.1 release. - wkalt h2. Update release notes for PDB 2.2.1 release. * Author: Wyatt Alt <> * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1117 Discussion|https://github.com/puppetlabs/puppetdb/pull/1117] * [Pull Request 1117 File Diff|https://github.com/puppetlabs/puppetdb/pull/1117/files] h2. Pull Request Description (webhooks-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 th
Jira (PDB-956) PR (1117): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1117): Update release notes for PDB 2.2.1 release. - wkalt wkalt commented: @pljenkinsro retest this please Add Comment PuppetDB / PDB-956 PR (1117): Update release notes for PDB 2.2.1 release. - wkalt h2. Update release notes for PDB 2.2.1 release. * Author: Wyatt Alt <> * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1117 Discussion|https://github.com/puppetlabs/puppetdb/pull/1117] * [Pull Request 1117 File Diff|https://github.com/puppetlabs/puppetdb/pull/1117/files] h2. Pull Request Description (webhooks-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-956) PR (1117): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1117): Update release notes for PDB 2.2.1 release. - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/90/ Add Comment PuppetDB / PDB-956 PR (1117): Update release notes for PDB 2.2.1 release. - wkalt h2. Update release notes for PDB 2.2.1 release. * Author: Wyatt Alt <> * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1117 Discussion|https://github.com/puppetlabs/puppetdb/pull/1117] * [Pull Request 1117 File Diff|https://github.com/puppetlabs/puppetdb/pull/1117/files] h2. Pull Request Description (webhooks-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 th
Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Branan Purvine-Riley commented on an issue Re: Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. It doesn't look like NC-263 has made it into PE yet. I'll try to get that shepherded through so we can get some cleaner results tonight. Add Comment Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. A big part of this is preparation for 4.0.x to adjust acceptance setup to use directory environments. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-114) No man pages for hiera
Title: Message Title Lauren Rother updated an issue Hiera / HI-114 No man pages for hiera Change By: Lauren Rother Assignee: Lauren Rother Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-287) stringify_facts needs to be in agent, not master conf file
Title: Message Title Lauren Rother updated an issue Hiera / HI-287 stringify_facts needs to be in agent, not master conf file Change By: Lauren Rother Assignee: Lauren Rother Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-705) Structured facts are not documented
Title: Message Title Lauren Rother updated an issue Facter / FACT-705 Structured facts are not documented Change By: Lauren Rother Assignee: Lauren Rother Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3277) Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default.
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-3277 Adjust puppet acceptance for puppetserver/classifier installations where environmentpath is set by default. Thanks to Branan Purvine-Riley pointing out the SERVER-38, ticket, I went back into the logs from last night's run, and found an example of the 'trusted' failure, which I'v attached. It looks like SERVER-38, cropping up when the master is handling the node/catalog requests from an agent run. In the pup-3449-agent-syslog.log at 04:15:41 there's the "Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'..." In the pup-3449-puppetserver.log at 04:15:40 the master replaces the facts for the node in puppetdb. And then there is an IO error reading the cached yaml facts, which gets logged, but proceeds. Basically the find_in_cache call of the indirection#find fails, so we fall through to querying the puppetdb terminus, and then cache that result (which now has 'trusted' in it). And either the facts we've just received, or subsequent requests hitting the now tainted YAML cache choke the top scope during the catalog evaluation. The next catalog request resets everything with a fresh set of facts. Change By: Joshua Partlow Attachment: pup-3449-puppetserver.log Attachment: pup-3449-agent-syslog.log Add Comment This m
Jira (PDB-956) PR (1117): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1117): Update release notes for PDB 2.2.1 release. - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/93/ Add Comment PuppetDB / PDB-956 PR (1117): Update release notes for PDB 2.2.1 release. - wkalt h2. Update release notes for PDB 2.2.1 release. * Author: Wyatt Alt <> * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1117 Discussion|https://github.com/puppetlabs/puppetdb/pull/1117] * [Pull Request 1117 File Diff|https://github.com/puppetlabs/puppetdb/pull/1117/files] h2. Pull Request Description (webhooks-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 th
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilati
Title: Message Title
Joshua Partlow commented on an issue
Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation.
We have useful logs of the failure from a PE 3.4 run finally. It looks to be SERVER-38 preventing a read of the YAML cache, falling back to puppetdb and then you get a node with 'trusted' in it's parameters and the scope throws an error. More details in PUP-3277 if anyone is curious.
Add Comment
PuppetDB / PDB-949
Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation.
We are seeing some failures in the PE Puppet Acceptance Tests job where the nodes facts contain a 'trusted' parameter which is reserved and ends up failing when the compiler pulls the facts into scope. {noformat} s60whm7u1kz3zfm.delivery.puppetlabs.net (redhat6-64-1) 09:08:56$ env PATH="/opt/puppet/bin:${PATH}" RUBYLIB="${RUBYLIB}" puppet agent --te...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3357) Unexpected error with multiple SSH keys without comments
Title: Message Title
Felix Frank commented on an issue
Re: Unexpected error with multiple SSH keys without comments
Changed the naming algorithm to ignore the key data and just rely on path and a unique counter per file. Each unnamed key gets a unique name.
Gert van Dijk have you had a chance to reproduce any other failures? We're nearing the 3.7.2, which might be the last 3.7 release. If so, further fixes will not be released until Puppet 4.0. Last call
Add Comment
Puppet / PUP-3357
Unexpected error with multiple SSH keys without comments
Steps to reproduce: # Enter multple SSH authorized keys for a user without comments (just a key line by line, see example below). # Manage the user with Puppet with the {{purge_ssh_keys}} parameter set to true. # Have Puppet agent 3.7.0+ # Puppet agent run fails completely with an error. (full denial of service of the agent effectively) Expected ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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,
Jira (PUP-3357) Unexpected error with multiple SSH keys without comments
Title: Message Title
Gert van Dijk commented on an issue
Re: Unexpected error with multiple SSH keys without comments
Felix Frank Well, it appears my earlier quick tests showing a lot of red warnings in the console weren't actually so harmful. They didn't stop the run, so I consider them too minor. Thanks for the fixes and the heads up!
Add Comment
Puppet / PUP-3357
Unexpected error with multiple SSH keys without comments
Steps to reproduce: # Enter multple SSH authorized keys for a user without comments (just a key line by line, see example below). # Manage the user with Puppet with the {{purge_ssh_keys}} parameter set to true. # Have Puppet agent 3.7.0+ # Puppet agent run fails completely with an error. (full denial of service of the agent effectively) Expected ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.goog
Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider
Title: Message Title
Eric Thompson commented on an issue
Re: Spurious 'trigger changed' messages generated by scheduled task provider
verified in win2012r2-ruby64 at stable SHA a327be7 with
# use Josh's manifest as above
# change start_time
# run again:
Notice: Compiled catalog for bw72vphos85hyye.delivery.puppetlabs.net in environment production in 0.14 seconds
Notice: /Stage[main]/Main/Scheduled_task[spurious_task]/trigger: trigger changed '[{'enabled' => 'true', 'every' => '1', 'index' => '0', 'schedule' => 'daily', 'start_date' => '2014-10-13', 'start_time' => '15:00'}]' to '[{'every' => '1', 'schedule' => 'daily', 'start_time' => '16:20'}]'
Notice: Finished catalog run in 0.03 seconds
# run again:
$ cmd.exe /c puppet apply manifest.pp
Notice: Compiled catalog for bw72vphos85hyye.delivery.puppetlabs.net in environment production in 0.14 seconds
Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1165 Spurious 'trigger changed' messages generated by scheduled task provider Change By: Eric Thompson QA Contact: Narmadha Perumal Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3096) trusted_node_data option should go away (should be always-on)
Title: Message Title Andy Parker commented on an issue Re: trusted_node_data option should go away (should be always-on) There is another setting that goes along with this. The purpose is to ensure that $facts and $trusted are always available so that we can start phasing out facts as top-scope variables. Add Comment Puppet / PUP-3096 trusted_node_data option should go away (should be always-on) This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3366) type system does not handle Enum/String compare correctly
Title: Message Title
Andy Parker commented on an issue
Re: type system does not handle Enum/String compare correctly
The final decision on this was Enum == String and Enum[a] < Enum and Enum[a] < String.
Add Comment
Puppet / PUP-3366
type system does not handle Enum/String compare correctly
{code} Enum[blue] < String {code} should be true, but it isn't. {code} Enum < String {code} should be true but fails with a comparison of fixnum vs. integer in the type calculator. While any enum is in fact the same as any string, it should still be considered more specific (they are not equal as types at least).
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3448) Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-3448
Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
Change By:
Charlie Sharpsteen
We have installed puppet master v 3.7.1and client v 3.7.1. {noformat} [root@pptmstr ~]# puppet config print modulepathWarning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1119:in `issue_deprecation_warning')/etc/puppet/modules:/usr/share/puppet/modules[root@pptmstr ~]#[root@pptmstr ~]# tree -L 2 -d /etc/puppet/modules/etc/puppet/modules|_ base |_ manifests|_ RH_Production|_ manifests {noformat} Under /etc/puppet/modules/base/manifests I have the following: {noformat} cd /etc/puppet/modules/base/manifests[root@pptmstr manifests]# lsinit.pp[root@pptmstr manifests]# cat init.ppclass base { file { '/etc/passwd':owner => 'root',group => 'root',mode => '0644', } file { '/etc/shadow':owner => 'root',group => 'root',mode => '0440', }}include base {noformat} I have run the following: {noformat} [root@pptmstr manifests]# puppet apply /etc/puppet/modules/base/manifests/init.pppuppet apply /etc/puppet/modules/base/manifests/init.ppWarning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1119:in `issue_deprecation_warning')Notice: Compiled catalog for pptmstr.poc.capgemini.com in environment production in 0.08 secondsNotice: Finished catalog run in 0.07 seconds {noformat} When we assign the class to the node through foreman and run the following command it fails: {noformat} [root@Linux4 yum.repos.d]# puppet agent --testInfo: Retrieving pluginfactsInfo: Retrieving pluginError: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class base::linux for linux4.poc.capgemini.com on node linux4.poc.capgemini.comWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run {noformat} What are we doing wrong here?Regards,Niranjan
Add Comment
Jira (PUP-3366) type system does not handle Enum/String compare correctly
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3366 type system does not handle Enum/String compare correctly Change By: Eric Thompson QA Contact: Kurt Wall Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3357) Unexpected error with multiple SSH keys without comments
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3357 Unexpected error with multiple SSH keys without comments Change By: Kylo Ginsberg Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3448) Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
Niranjan Hettiwatte: The definition you've shown working under puppet apply is for class base, however the master is looking for base::linux. It looks like you need to either change the classification in foreman to apply class base or add a new manifest to your module containing a definition for base::linux.
/etc/puppet/modules/base/manifests/linux.pp
Does that help resolve your issue?
Add Comment
Puppet / PUP-3448
Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
We have installed puppet master v 3.7.1and client v 3.7.1. {noformat} [root@pptmstr ~]# puppet config print modulepath Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:1119:in `issue_deprecation_warning') /etc/puppet/modules:/us...
Jira (PUP-3448) Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3448 Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Niranjan Hettiwatte Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3449) Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'.
Title: Message Title Joshua Partlow commented on an issue Re: Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'. PR is attached, but I'm really not sure that it should be merged. :/ Add Comment Puppet / PUP-3449 Puppet::Node::Facts allows a fact named 'trusted' that collides with the reserved top scope puppet variable name 'trusted'. There is a top scope variable named 'trusted' which is reserved by the compiler for the trusted data that the server gathers from the request's certificate. A node's facts are also made available as top scope variables during puppet execution, and if the node has a 'trusted' fact, either created by the user, or retrieved from a node terminus like PuppetD... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/pup
Jira (PDB-956) PR (1117): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1117): Update release notes for PDB 2.2.1 release. - wkalt Pull request Update release notes for PDB 2.2.1 release. has been closed. Add Comment PuppetDB / PDB-956 PR (1117): Update release notes for PDB 2.2.1 release. - wkalt h2. Update release notes for PDB 2.2.1 release. * Author: Wyatt Alt <> * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1117 Discussion|https://github.com/puppetlabs/puppetdb/pull/1117] * [Pull Request 1117 File Diff|https://github.com/puppetlabs/puppetdb/pull/1117/files] h2. Pull Request Description (webhooks-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-957) PR (1119): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-957 PR (1119): Update release notes for PDB 2.2.1 release. - wkalt Issue Type: Task Assignee: Unassigned Created: 13/Oct/14 5:42 PM Labels: github Priority: Normal Reporter: gepetto-bot Update release notes for PDB 2.2.1 release. Author: Wyatt Alt <> Company: Github ID: wkalt Pull Request 1119 Discussion Pull Request 1119 File Diff Pull Request Description (webhooks-id: db546880fb0064049b8e28379035c0d5)
Jira (PDB-957) PR (1119): Update release notes for PDB 2.2.1 release. - wkalt
Title: Message Title gepetto-bot commented on an issue Re: PR (1119): Update release notes for PDB 2.2.1 release. - wkalt Pull request Update release notes for PDB 2.2.1 release. has been closed. Add Comment PuppetDB / PDB-957 PR (1119): Update release notes for PDB 2.2.1 release. - wkalt h2. Update release notes for PDB 2.2.1 release. * Author: Wyatt Alt <> * Company: * Github ID: [wkalt|https://github.com/wkalt] * [Pull Request 1119 Discussion|https://github.com/puppetlabs/puppetdb/pull/1119] * [Pull Request 1119 File Diff|https://github.com/puppetlabs/puppetdb/pull/1119/files] h2. Pull Request Description (webhooks-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-643) Solaris pkg package provider does not handle expiring certificates
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-643 Solaris pkg package provider does not handle expiring certificates Change By: Kylo Ginsberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-643) Solaris pkg package provider does not handle expiring certificates
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-643 Solaris pkg package provider does not handle expiring certificates Change By: Kylo Ginsberg Sprint: Platform 2014-10-15 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-900) Improve GC's for fact_values
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-900 Improve GC's for fact_values Change By: Wyatt Alt Fix Version/s: 2.2.x Fix Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-847) PuppetDB 2.x is not compatible with Puppet Enterprise
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-847 PuppetDB 2.x is not compatible with Puppet Enterprise Change By: Wyatt Alt Fix Version/s: 2.2.x Fix Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-868) Potential race condition causing API error in db_resilience/postgres_restart.rb
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-868 Potential race condition causing API error in db_resilience/postgres_restart.rb Change By: Wyatt Alt Fix Version/s: 2.2.x Fix Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-865) Puppet DB Migrations Do not Handle Bad Data
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-865 Puppet DB Migrations Do not Handle Bad Data Change By: Wyatt Alt Fix Version/s: 2.2.x Fix Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-707) The first request to PuppetDB after DB backend restart fails
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-707 The first request to PuppetDB after DB backend restart fails Change By: Wyatt Alt Fix Version/s: 2.2.x Fix Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-653) Certain metrics aren't getting updated
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-653 Certain metrics aren't getting updated Change By: Wyatt Alt Fix Version/s: 3.0.0 Fix Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-905) Null containing-class and containing-path for skip events
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-905 Null containing-class and containing-path for skip events Change By: Wyatt Alt Fix Version/s: 2.2.x Fix Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-904) Adding a fact with a large value makes the PG DB enter recovery mode / crash
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-904 Adding a fact with a large value makes the PG DB enter recovery mode / crash Change By: Wyatt Alt Fix Version/s: 2.2.x Fix Version/s: 2.2.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
