Jira (PUP-5134) Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-5134 Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet Change By: Josh Cooper Status: Ready for CI Test Assignee: Josh Cooper qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5134) Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet
Title: Message Title Josh Cooper commented on PUP-5134 Re: Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet John Duarte Not sure if you want to verify this fix for SPARC in puppet-agent#master? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2057) Align the sync config and terminus server_url config behavior
Title: Message Title Russell Mull assigned an issue to Unassigned PuppetDB / PDB-2057 Align the sync config and terminus server_url config behavior Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2071) Sticky failover in for terminus queries
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2071 Sticky failover in for terminus queries Change By: Russell Mull Scope Change Category: Adopted Scope Change Reason: Closely related to planned work Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Adam Winberg commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Using apache/passenger I have only had one puppet run where ~70 agent runs failed. It's still really slow at those times, but manage to keep it together more so than puppetserver (with my current configuration). The only parameters in the jetty config docs you provided that seem interesting to me is the idleTimeout and the stopTimeout. The former I believe is already set (idle-timeout-milliseconds), but the latter may be interesting, is this already available and what's its default value? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5134) Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5134 Get pre-suites working for Solaris 11 (SPARC, i386) for Puppet Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2057) Align the sync config and terminus server_url config behavior
Title: Message Title Russell Mull commented on PDB-2057 Re: Align the sync config and terminus server_url config behavior The terminus requires https, but allows you to omit the port. It forbids url paths though. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2057) Align the sync config and terminus server_url config behavior
Title: Message Title Russell Mull commented on PDB-2057 Re: Align the sync config and terminus server_url config behavior Another consideration: if the user writes "http", it will only work if they've explicitly configured their puppetdb to allow http from non-localhost. In that case, shouldn't we let them? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2071) Sticky failover in terminus queries
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2071 Sticky failover in terminus queries Change By: Russell Mull Summary: Sticky failover in for terminus queries Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2071) Sticky failover in for terminus queries
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-2071 Sticky failover in for terminus queries Change By: Russell Mull Sprint: PuppetDB 2015-11- 18 4 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2071) Sticky failover in terminus queries
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2071 Sticky failover in terminus queries Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2057) Align the sync config and terminus server_url config behavior
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2057 Align the sync config and terminus server_url config behavior Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5022) module README template should be updated in puppet module generate skeleton
Title: Message Title David Schmitt commented on PUP-5022 Re: module README template should be updated in puppet module generate skeleton Uploaded updated template in https://github.com/puppetlabs/puppet/pull/4373 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings John Bollinger The intent is to deprecate the hiera_xxx functions sometime in the 4.x series. As the functionality for "data in modules"/"lookup" is brand new in puppet 4.3.0 we want it to be use a bit before we start banging on the big drum and doing the deprecations. If all goes well, the idea is to do that in Puppet 4.4.0. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1254) Custom Structured Facts don't return values via dot syntax
Title: Message Title Michael Smith commented on FACT-1254 Re: Custom Structured Facts don't return values via dot syntax Failed CI due to a missing header: https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Master/view/Puppet%20Agent%20Daily/job/platform_aio-suite_pkg-build_master/65/. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1254) Custom Structured Facts don't return values via dot syntax
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1254 Custom Structured Facts don't return values via dot syntax Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1238) Facter should respect long-form hostnames to populate hostname, domain, and FQDN
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1238 Facter should respect long-form hostnames to populate hostname, domain, and FQDN Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2058) build from source instructions no longer valid for PDB 3+ on arch linux (if not in general)
Title: Message Title Kenneth Barber commented on PDB-2058 Re: build from source instructions no longer valid for PDB 3+ on arch linux (if not in general) Raised this for now to cover pushing to clojars for the future: https://github.com/puppetlabs/ezbake/pull/285/files Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2075) Speed up unit tests
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2075 Speed up unit tests Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title John Bollinger commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Is it ok if we leave the hiera_xxx functions as they are since they have the style that implies that the user knows the data configuration? Instead users should use the lookup function where the lookup options from data files becomes the default if not given as an argument to lookup. If the lookup() function honors the lookup options specified in the data, then I would be satisfied for hiera() to not do so. I agree that it does not make sense for the behavior of the hiera_xxx() functions to change in any case, but I do still recommend that those functions be deprecated. If lookup() behaves as suggested then the hiera() function should be deprecated, too. Overall, this could be less surprising than altering hiera() to sometimes perform hash-merge or array lookups. If deprecation is too strong to be palatable at this time, then at minimum start strongly promoting use of lookup() and the in-data lookup options as superior practice, which it is. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-475) Use syck YAML parser for Ruby 1.9.3 and 2.0.x
Title: Message Title Matthew Mosesohn created an issue Hiera / HI-475 Use syck YAML parser for Ruby 1.9.3 and 2.0.x Issue Type: Bug Affects Versions: HI 1.3.4 Assignee: Unassigned Created: 2015/10/23 5:59 AM Priority: Normal Reporter: Matthew Mosesohn Default YAML parser treats unquoted strings starting with 0 sometimes as a numeric value. Example input: password: 0Xmy_secret_pass mac: 08:00:27:32:56:08 1.93 parser output: $ hiera password 0Xmy_secret_pass $ hiera mac 6226750568 2.0.0 parser output: $ hiera password 12380245 $ hiera mac 1960347 Output is as expected with 'syck' yamler in 1.9.3 and 2.0.0: $ hiera password 0Xmy_secret_pass $ hiera mac 08:00:27:32:56:08 Ruby versions below 1.9.3 do not contain 'syck' yamler and 2.1 is not affected. Add Comment
Jira (PDB-2058) build from source instructions no longer valid for PDB 3+ on arch linux (if not in general)
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-2058 build from source instructions no longer valid for PDB 3+ on arch linux (if not in general) Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5317) Master should return 74 when puppet user doesn't exist
Title: Message Title Nicholas Fagerlund commented on PUP-5317 Re: Master should return 74 when puppet user doesn't exist This is meant to apply to webrick only, right? Or is this Puppet Server too? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Nick Moriarty commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' I've reproduced the same bug _sproradically_against puppet 3.7.5. In my case it's network_config/interfaces that can't load puppetx/filemapper. I added some debug logging to the relevant code. What I can see is that, sometimes, util/autoload.rb ends up missing out the environment modulepath's directories completely when trying to load providers. When it fails, the search path (including gems) only consists of the gempath. In working runs, it includes the lib directories in all modules under each element of modulepath. This seems like it might be a race condition somewhere. I note that $env_module_directories stores the mapping between the current environment and the load path. This is a global variable, but the comment on module_directories says "per-thread cache". I can't see any sort of protection on it; is it possible this is being corrupted somewhere? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2039) PuppetDB node-level securing of command submission
Title: Message Title Kenneth Barber commented on PDB-2039 Re: PuppetDB node-level securing of command submission Original PR is getting old, I'm going to close it: https://github.com/puppetlabs/puppetdb/pull/1679, but its still there for reference. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings All keys in a module are qualified with the module name. In fact, the module data provider is selected based on this key. A key that isn't prefixed with the module name will hence never reach a module data provider which means that the keys like lookupoptions or lookupoptions::* will never be found in a module. So in a module, the format must instead be: mysql::lookupoptions mysql::server::override_options: merge: deep Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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
Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Nick Moriarty commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' On further inspection, I can't see anything actually hooking the require 'puppetx/filemapper' in autoload.rb - this almost looks like the fact it's succeeding could be some strange side-effect of it being in the load path at some point, sometimes - but restarting the master does seem to reliably kill it. Does anyone know how the require / autoload bits actually work? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Adam Winberg commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection I'm also seeing the occasional WARN [o.e.j.s.HttpChannel] Could not send response error 500: java.lang.IllegalStateException: org.eclipse.jetty.util.SharedBlockingCallback$BlockerTimeoutException message in the puppetserver.log when agent runs are aborted. Then I found this jetty bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=444031 Don't know if thats relevant with the jetty version puppetserver is using, but it sounds like it may be a similar problem. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5311) aix_package_provider test fails on AIX
Title: Message Title William Hopper commented on PUP-5311 Re: aix_package_provider test fails on AIX John Duarte heh, yeah that makes sense. If for some reason the package provider is bugged, then this test could cause subsequent tests to fail if it can't uninstall the package correctly, so +1. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5189) Add node definition for Windows 10 (x86, x64) to Puppet
Title: Message Title Kenn Hussey commented on PUP-5189 Re: Add node definition for Windows 10 (x86, x64) to Puppet Steve Barlow ping. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4743) Correct checksum documentation for `puppet help module changes`
Title: Message Title Kenn Hussey commented on PUP-4743 Re: Correct checksum documentation for `puppet help module changes` Steve Barlow ping. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5382) Compiler raises a cryptic error when no node mappings are defined on an application declaration
Title: Message Title Hailee Kenney assigned an issue to qa Puppet / PUP-5382 Compiler raises a cryptic error when no node mappings are defined on an application declaration Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2078) Rethink migrate.clj
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-2078 Rethink migrate.clj Change By: Ryan Senior Assignee: Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5382) Compiler raises a cryptic error when no node mappings are defined on an application declaration
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-5382 Compiler raises a cryptic error when no node mappings are defined on an application declaration Change By: Hailee Kenney Assignee: qa Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1261) Differentiate open source and PE fact collection direcotries
Title: Message Title Christopher W Anderson created an issue Facter / FACT-1261 Differentiate open source and PE fact collection direcotries Issue Type: Bug Assignee: Unassigned Created: 2015/10/23 9:55 AM Priority: Normal Reporter: Christopher W Anderson Stale facts saved from a previous test PE install no longer being utilized are incorrectly being detected by facter on an open source puppet install. This was discovered on facter 1.7.5, upon looking in github, is present in the latest native release as well. 'puppetlabs' directories are named for Enterprise and should not these be included in open source releases: /opt/puppetlabs/facter/facts.d /etc/puppetlabs/facter/facts.d Ruby version: lib/facter/util/config.rb Native version: lib/src/facts/posix/collection.cc Add Comment
Jira (PUP-5381) Evaluating instance match with Optional[T] and NotUndef[T] fails when T is a string value
Title: Message Title Hailee Kenney commented on PUP-5381 Re: Evaluating instance match with Optional[T] and NotUndef[T] fails when T is a string value On SHA d29f5e3f373d14c22969f141e54034540c880e8c (before the fix): ❤ > be puppet apply -e "notice(5 =~ Optional[foo])" Error: Evaluation Error: Error while evaluating a '=~' _expression_, undefined method `instance?' for "foo":String at line 1:10 on node hailees-mbp-2.corp.puppetlabs.net And on SHA e3195ba1cd69f81fc054f1361e8578c1fe452fe7 (after the fix): ❤ > be puppet apply -e "notice(5 =~ Optional[foo])" Notice: Scope(Class[main]): false Notice: Compiled catalog for hailees-mbp-2.corp.puppetlabs.net in environment production in 0.03 seconds Notice: Applied catalog in 0.04 seconds
Jira (PUP-5060) Add support for --facts in 'puppet lookup' command
Title: Message Title Hailee Kenney assigned an issue to qa Puppet / PUP-5060 Add support for --facts in 'puppet lookup' command Change By: Hailee Kenney Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1258) Exceptions thrown while resolving facts should be caught when running inside Ruby
Title: Message Title Peter Huene assigned an issue to qa Facter / FACT-1258 Exceptions thrown while resolving facts should be caught when running inside Ruby Change By: Peter Huene Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1255) Facter reporting wrong NIC card IP's on RHEL 5
Title: Message Title Michael Smith commented on FACT-1255 Re: Facter reporting wrong NIC card IP's on RHEL 5 Haven't been able to reproduce this on a CentOS 5 or 7 machine with puppet-agent 1.2.2. I'm using VMs in VMWare Fusion, setup with a public and a private network. Output: [vagrant@localhost ~]$ /opt/puppetlabs/bin/facter ipaddress_eth0 172.16.103.130 [vagrant@localhost ~]$ /opt/puppetlabs/bin/facter ipaddress_eth1 10.0.18.52 [vagrant@localhost ~]$ /opt/puppetlabs/bin/facter ipaddress_eth2 172.16.160.132 [vagrant@localhost ~]$ sudo /sbin/ifconfig eth0 | grep 'inet ' inet addr:172.16.103.130 Bcast:172.16.103.255 Mask:255.255.255.0 [vagrant@localhost ~]$ sudo /sbin/ifconfig eth1 | grep 'inet '
Jira (FACT-1258) Exceptions thrown while resolving facts should be caught when running inside Ruby
Title: Message Title Peter Huene commented on FACT-1258 Re: Exceptions thrown while resolving facts should be caught when running inside Ruby Like, FACT-1257 , there is no good way to test this as it relies on an unhandled exception on Windows to reproduce. FACT-1257 was specific to a particular configuration of Windows that we could reproduce. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5381) Evaluating instance match with Optional[T] and NotUndef[T] fails when T is a string value
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-5381 Evaluating instance match with Optional[T] and NotUndef[T] fails when T is a string value Change By: Hailee Kenney Assignee: qa Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thomas Hallgren Hm (the need to use a module name in the lookupoptions key) - how do you see that working. I imagined we would simply do a lookup of "lookupoptions" with deep merge and get all of them. Does this mean we need to do a lookup per module? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5278) puppet lookup --explain produces unhelpful reference
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5278 puppet lookup --explain produces unhelpful reference Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Christopher Price commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Reading up on stopTimeout, it sounds like it just affects how long the server waits to forcefully kill threads during a shutdown. So, that sounds like a long shot, unfortunately. What version of the JDK are you using? And remind me what version of Puppet Server? There are some newer builds of Jetty out there; we're currently using 9.2.10, and they are up to 9.2.13 in the 9.2.x series, and 9.3.5 on the new 9.3.x series. I could pretty easily put a build together for you that included 9.3.5, but it looks like it has a minimum JDK version of 8. It also might be useful to get some JMX metrics out of your Jetty setup when it's under high load. At some point I could put a script together to try to collect those for you, but TBH it'll probably be a few weeks before we have bandwidth for that because we have a big release date coming up. Usually when we've seen those WritePending it's been because (from the perspective of the server) the client closed the connection. So if you're seeing that happen on multiple agents at the same time, I'd be suspicious of a load balancer or a router severing the connection; perhaps temporarily, and perhaps in a way that Apache is more patient about waiting for a recovery from. If you are interested in testing a build with a newer Jetty, let us know. Or if you are able to narrow down what other things might be going on in your environment so that we can set up a repro case over here. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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
Jira (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Adam Winberg commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection I'm using puppetserver 1.1.1, which has a dependency (i'm on RHEL) to java-1.7.0-openjdk (of which I am running latest patch), so thats the one I'm using. It's no problem for me to run java8 instead, though. I'm gonna do some more digging regarding networking and such. I'll get back to you about that updated jetty build. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5340) puppet apply doesn't honor --catalog_cache_terminus
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5340 puppet apply doesn't honor --catalog_cache_terminus Change By: Sean Griffin Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Henrik Lindberg, the way I see it, using the hiera_xxx functions is similar to explicitly specify the options with a parameter when using the lookup function. I.e. the user expresses a desire to override the default and should be able to do so. Therefore I'm in favor of keeping the hiera_xxx functions as they are. Another reason for this is that I view them as legacy functions that should be deprecated eventually. As such, it's better to just leave them as they are. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-2071) Sticky failover in terminus queries
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2071 Sticky failover in terminus queries Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5422) Agent pidfile never removed in Solaris
Title: Message Title William Hopper commented on PUP-5422 Re: Agent pidfile never removed in Solaris This is a result of Puppet::Daemon.stop never being called when trying to stop the service. In that method, the pidfile is supposed to be removed. We're never calling that method because of our signal handling issues, which are detailed in https://tickets.puppetlabs.com/browse/PUP-4516. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5262) Solaris (10) service provider returns before service refresh is complete
Title: Message Title William Hopper commented on PUP-5262 Re: Solaris (10) service provider returns before service refresh is complete A solution to this might revolve around waiting for the service to truly be dead in the smf script, such as is detailed in PUP-5405. However, currently the pidfile is not being removed correctly in Solaris, blocking that fix (see PUP-5422). Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5089) classes should be allowable as application components
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5089 classes should be allowable as application components Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5427) incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5427 incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env. Change By: Geoff Nichols Fix Version/s: PUP 4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5427) incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5427 incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env. Change By: Geoff Nichols Affects Version/s: PUP 4.2.2 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5427) incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env.
Title: Message Title Geoff Nichols moved an issue Puppet / PUP-5427 incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env. Change By: Geoff Nichols Affects Version/s: puppet-agent 1.2.4 Workflow: Release Engineering Scrum Team Workflow Key: PA PUP - 6 5427 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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
Jira (PUP-5294) Capability resource params without default values fail during env catalog compilation
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5294 Capability resource params without default values fail during env catalog compilation Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5089) classes should be allowable as application components
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-5089 classes should be allowable as application components Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title Eric Thompson commented on PUP-5426 Re: config set ignores --section and can insert duplicate settings if they are in [main] possible history: https://github.com/puppetlabs/puppet/pull/2138 https://github.com/puppetlabs/puppet/pull/2158 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5382) Compiler raises a cryptic error when no node mappings are defined on an application declaration
Title: Message Title
Hailee Kenney commented on PUP-5382
Re: Compiler raises a cryptic error when no node mappings are defined on an application declaration
When running with this manifest:
❤ > cat foo.pp
application app {
}
site {
app { anapp:
}
}
On SHA fd3732b3328134f145e68ddfda2a5273abe9dd12 (before the fix was merged):
❤ > be puppet apply --app_management foo.pp
Jira (PUP-5271) Windows user resource should not manage password unless specified
Title: Message Title
Ryan Gard commented on PUP-5271
Re: Windows user resource should not manage password unless specified
Functional Review
Verified as fixed in build b628b07eb521caacc920f8b87749974d269a58bc. Ethan Brown Rob Reynolds Can you take a look at this FR to make sure I covered the right scenarios?
Environment
Agent OS: Windows 2012 R2 x64
Test Case 1
Install the Puppet Agent (x64) onto the Windows SUT.
Set the "Password must meet complexity requirements" policy to "Enabled" in the Local Group Policy Editor on the Windows SUT. (Computer Configuration->Windows Settings->Security Settings->Account Policies->Password Policy)
Set the "Minimum password length" policy to "0" in the Local Group Policy Editor on the Windows SUT. (Computer Configuration->Windows Settings->Security Settings->Account Policies->Password Policy)
Create a user without providing a password:
puppet apply -e "user {'bob': ensure=>present }"
Expect
The user should be created successfully without error.
Console Output
C:\test>puppet apply -e "user {'bob': ensure=>present }"
Notice: Compiled catalog for w2012r2.vm in environment production in 0.25 second
Jira (PUP-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title Eric Thompson created an issue Puppet / PUP-5426 config set ignores --section and can insert duplicate settings if they are in [main] Issue Type: Bug Assignee: Kylo Ginsberg Components: Client Created: 2015/10/23 2:27 PM Priority: Normal Reporter: Eric Thompson [root@qcpd7c0tnvnp4kd ~]# cat /etc/puppetlabs/puppet/puppet.conf # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available:
Jira (PUP-5262) Solaris (10) service provider returns before service refresh is complete
Title: Message Title William Hopper assigned an issue to Unassigned Puppet / PUP-5262 Solaris (10) service provider returns before service refresh is complete Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5275) "produces" statements seem not to work from a puppet agent run
Title: Message Title
Nick Lewis commented on PUP-5275
Re: "produces" statements seem not to work from a puppet agent run
Thomas Hallgren I think the example I gave was a little _too_simple, as we're still seeing this problem in more complex cases. I think because the component in my example was in init.pp, it ends up being loaded early enough for this fix to take effect. If we swap the location of application and component, the problem is still present (which makes sense, since consumes mappings are evaluated during the site evaluation, before most mappings have been):
$modules/foo/manifests/init.pp
application foo() {
foo::component { $name:
export => Sql[$name],
}
}
$modules/foo/manifests/component.pp
define foo::component() { }
Foo::Component produces Sql { }
site.pp
Jira (PUP-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5000 acceptance: test agent_specified environment, ENC, and related facts Change By: Eric Thompson Sprint: Client 2015-11- 11 25 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1253) acceptance: ensure jar file is packaged on all applicable platforms
Title: Message Title Eric Thompson updated an issue Facter / FACT-1253 acceptance: ensure jar file is packaged on all applicable platforms Change By: Eric Thompson Sprint: Client 2015-11- 11 25 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-5422) Agent pidfile never removed in Solaris
Title: Message Title William Hopper created an issue Puppet / PUP-5422 Agent pidfile never removed in Solaris Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Created: 2015/10/23 11:10 AM Environment: Solaris Priority: Normal Reporter: William Hopper In Solaris, starting the puppet service with puppet resource service puppet ensure=running creates /var/run/puppetlabs/agent.pid with the PID of the daemonized process. However, stopping the service correctly kills the service but leaves the pidfile in place with the old PID. -bash-3.2# puppet resource service puppet ensure=running Notice: /Service[puppet]/ensure: ensure changed 'stopped' to 'running'
Jira (PUP-5422) Agent pidfile never removed in Solaris
Title: Message Title
William Hopper updated an issue
Puppet / PUP-5422
Agent pidfile never removed in Solaris
Change By:
William Hopper
In Solaris, starting the puppet service with {{puppet resource service puppet ensure=running}} creates {{/var/run/puppetlabs/agent.pid}} with the PID of the daemonized process. However, stopping the service correctly kills the service but leaves the pidfile in place with the old PID.{noformat}-bash-3.2# puppet resource service puppet ensure=runningNotice: /Service[puppet]/ensure: ensure changed 'stopped' to 'running'service { 'puppet': ensure => 'running',}-bash-3.2# puppet resource service puppetservice { 'puppet': ensure => 'running', enable => 'true',}-bash-3.2# cat /var/run/puppetlabs/agent.pid1343-bash-3.2# ps -elf | grep 1343 0 S root 1343 1 0 40 20? 9011? 11:07:40 ? 0:00 /opt/puppetlabs/puppet/bin/ruby /op# Stopping the service-bash-3.2# puppet resource service puppet ensure=stoppedNotice: /Service[puppet]/ensure: ensure changed 'running' to 'stopped'service { 'puppet': ensure => 'stopped',}-bash-3.2# puppet resource service puppetservice { 'puppet': ensure => 'stopped', enable => 'false',}-bash-3.2# cat /var/run/puppetlabs/agent.pid1343-bash-3.2# ps -elf | grep puppet-bash-3.2# svcs -a puppetsvcs: -a ignored when used with arguments.STATE STIMEFMRIdisabled 11:08:31 svc:/network/puppet:default{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet
Jira (PUP-5422) Agent pidfile never removed in Solaris
Title: Message Title
William Hopper updated an issue
Puppet / PUP-5422
Agent pidfile never removed in Solaris
Change By:
William Hopper
In Solaris, starting the puppet service with {{puppet resource service puppet ensure=running}} creates {{/var/run/puppetlabs/agent.pid}} with the PID of the daemonized process. However, stopping the service correctly kills the service but leaves the pidfile in place with the old PID.{noformat}-bash-3.2# puppet resource service puppet ensure=runningNotice: /Service[puppet]/ensure: ensure changed 'stopped' to 'running'service { 'puppet': ensure => 'running',}-bash-3.2# puppet resource service puppetservice { 'puppet': ensure => 'running', enable => 'true',}-bash-3.2# cat /var/run/puppetlabs/agent.pid1343-bash-3.2# ps -elf | grep 1343 0 S root 1343 1 0 40 20? 9011? 11:07:40 ? 0:00 /opt/puppetlabs/puppet/bin/ruby /op# Stopping the service-bash-3.2# puppet resource service puppet ensure=stoppedNotice: /Service[puppet]/ensure: ensure changed 'running' to 'stopped'service { 'puppet': ensure => 'stopped',}-bash-3.2# puppet resource service puppetservice { 'puppet': ensure => 'stopped', enable => 'false',}-bash-3.2# cat /var/run/puppetlabs/agent.pid1343-bash-3.2# ps -elf | grep puppet-bash-3.2# svcs puppet svcs: -a ignored when used with arguments. STATE STIMEFMRIdisabled 11:08:31 svc:/network/puppet:default{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet
Jira (PUP-5311) aix_package_provider test fails on AIX
Title: Message Title John Duarte commented on PUP-5311 Re: aix_package_provider test fails on AIX https://github.com/puppetlabs/puppet/pull/4374 William Hopper ^^ Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-1257) Facter crashes when attempting to return an empty array
Title: Message Title Erik Hansen updated an issue Facter / FACT-1257 Facter crashes when attempting to return an empty array Change By: Erik Hansen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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.
