Jira (PUP-5340) puppet apply doesn't honor --catalog_cache_terminus
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5340 puppet apply doesn't honor --catalog_cache_terminus Change By: Kylo Ginsberg Story Points: 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 (PDB-841) Retire (or at least consider retiring) the storeconfigs export tool
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-841 Retire (or at least consider retiring) the storeconfigs export tool Change By: Kurt Wall QA Risk Assessment Reason: Design, test-related, and refactoring tickets not risked QA Status: Reviewed QA Risk Assessment: Low 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-1459) Support extract with no subexpression
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1459 Support extract with no subexpression Change By: Kurt Wall QA Status: Reviewed 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-1459) Support extract with no subexpression
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1459 Support extract with no subexpression Change By: Kurt Wall QA Risk Assessment Reason: New features not risked 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-1459) Support extract with no subexpression
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1459 Support extract with no subexpression Change By: Kurt Wall QA Risk Assessment: Low 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-1957) Remove Puppet 3 Support Hacks
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1957 Remove Puppet 3 Support Hacks Change By: Kurt Wall QA Risk Assessment Reason: Design, test-related, and refactoring tickets not risked QA Status: Reviewed QA Risk Assessment: Low 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-2033) Spike: Design resilient terminus delivery from puppet master
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2033 Spike: Design resilient terminus delivery from puppet master Change By: Kurt Wall QA Risk Assessment Reason: Design, test-related, and refactoring tickets not risked QA Status: Reviewed QA Risk Assessment: Low 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-1014) Retirement: Make hash field for not null always
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1014 Retirement: Make hash field for not null always Change By: Kurt Wall QA Risk Assessment Reason: Design, test-related, and refactoring tickets not risked QA Status: Reviewed QA Risk Assessment: Low 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-2007) munging catalog fails with :undef tags
Title: Message Title Daniel Dreier commented on PDB-2007 Re: munging catalog fails with :undef tags Kurt Wall The reason it's only impacting us now is that we're working on migrating from PE 3.3.0 / PuppetDB 1.5.2 to 2015.2.1 / PuppetDB 3.1.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 (PDB-2007) munging catalog fails with :undef tags
Title: Message Title Kurt Wall commented on PDB-2007 Re: munging catalog fails with :undef tags Daniel Dreier This sounds like an issue that has been present for some time. Is that accurate or is this a recent regression? Thanks! 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-5343) Triage Solaris 11 failures
Title: Message Title John Duarte created an issue Puppet / PUP-5343 Triage Solaris 11 failures Issue Type: Task Assignee: John Duarte Created: 2015/10/08 7:23 AM Environment: Solaris 11 SPARC Priority: Normal Reporter: John Duarte The following puppet acceptance tests fail on Solaris 11 SPARC using 1.2.5-78-gbb3022f at puppet-agent SHA bb3022fd4c4d7b4ab7d391514770f7c257132196. tests/resource/file/symbolic_modes.rb tests/resource/zone/set_ip.rb tests/resource/zone/set_path.rb
Jira (PDB-1995) Move logging test utils code into TK
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1995 Move logging test utils code into TK Change By: Kurt Wall QA Risk Assessment Reason: Design, test-related, and refactoring tickets not risked QA Status: Reviewed QA Risk Assessment: Low 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-1100) Retire support for classname with hyphens
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1100 Retire support for classname with hyphens Change By: Kurt Wall QA Risk Assessment Reason: Design, test-related, and refactoring tickets not risked QA Status: Reviewed QA Risk Assessment: Low 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-1956) Retire support for Ruby 1.8.7
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1956 Retire support for Ruby 1.8.7 Change By: Kurt Wall QA Risk Assessment Reason: Design, test-related, and refactoring tickets not risked QA Status: Reviewed QA Risk Assessment: Low 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-5344) Could not evaluate: invalid byte sequence in US-ASCII
Title: Message Title Chris Denneen created an issue Puppet / PUP-5344 Could not evaluate: invalid byte sequence in US-ASCII Issue Type: Bug Affects Versions: PUP 3.8.3 Assignee: Unassigned Created: 2015/10/08 7:43 AM Fix Versions: PUP 3.8.2 Labels: ubuntu puppet Priority: Normal Reporter: Chris Denneen Could not evaluate: invalid byte sequence in US-ASCII puppetserver-1.1.1 Agent: Ubuntu Trusty agent 3.8.3 has issue, downgrade to 3.8.2 and issue goes away.
Jira (PDB-2007) munging catalog fails with :undef tags
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2007 munging catalog fails with :undef tags Change By: Kurt Wall QA Risk Assessment Reason: A failed agent run doesn't lose data but is still disruptive; QA Highest Test Level: Unit QA Risk Probability Reason: Probability/likelihood unknown: how often is a tag :undef on resources? QA Risk Severity Reason: Disruptive but not catastrophic QA Status: Reviewed QA Contact: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5344) Could not evaluate: invalid byte sequence in US-ASCII
Title: Message Title Chris Denneen commented on PUP-5344 Re: Could not evaluate: invalid byte sequence in US-ASCII This was an issue few years back and suggested fix was to set default LANG into the puppetmaster rack instance. Now with puppetserver not sure if that's the solution anymore or why it was working with 3.8.2 and broke again with 3.8.3. 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-2007) munging catalog fails with :undef tags
Title: Message Title Kurt Wall commented on PDB-2007 Re: munging catalog fails with :undef tags Daniel Dreier Thanks. Trying to assess the risk of whatever fix might emerge. 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-2007) munging catalog fails with :undef tags
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2007 munging catalog fails with :undef tags Change By: Kurt Wall QA Risk Severity: Medium 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-2007) munging catalog fails with :undef tags
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-2007 munging catalog fails with :undef tags Change By: Kurt Wall QA Risk Assessment: Medium 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-5345) SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Title: Message Title Joshua Partlow created an issue Puppet / PUP-5345 SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404 Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/10/08 10:47 AM Priority: Normal Reporter: Joshua Partlow This is probably very similar to PUP-5016 but with a different set of defaults. On Ubuntu platforms defaulting to upstart, a sysv init script ends up using the init rather than the debian provider, and therefore will not show the enable parameter when using `puppet resource service`. (Unless the 'enable' parameter is specifically set, see below) For example, on Ubuntu1404, with puppet-agent 1.2.2 installed: root@pe-201520-agent:/home/vagrant# puppet resource service puppet
Jira (PDB-2034) schema error on replace facts insert-facts-pv-pairs!
Title: Message Title
Wyatt Alt commented on PDB-2034
Re: schema error on replace facts insert-facts-pv-pairs!
Martin Loy
Thanks for tracking that down – I was not thinking that the problem would turn out to be with a specific fact, but that seems to be the case. PuppetDB seems to fail to process facts with names that begin with an escaped quote, which yours does. I can reproduce the error with this custom fact:
Facter.add("\"foo") do setcode do "hello world" end end
I'm about to start looking into what's causing the problem (and I'll update the ticket with that info), but I think your issues will go away if that fact is fixed.
Wyatt
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-2034) schema error on replace facts insert-facts-pv-pairs!
Title: Message Title Martin Loy commented on PDB-2034 Re: schema error on replace facts insert-facts-pv-pairs! Wyatt Alt i've solve my issue by removing the fact from the catalog and already report the bug to the fine folks of puppet-community https://github.com/puppet-community/puppet-rundeck/issues/132 Hope my troubles end up helping you make a better puppetdb! Regards M 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-5274) Puppet cert generate leaves ca_key as 644 on first run
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5274 Puppet cert generate leaves ca_key as 644 on first run Change By: Sean Griffin 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 (PUP-5292) regsubst doesn't work on empty arrays in puppet 4.x
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5292 regsubst doesn't work on empty arrays in puppet 4.x Change By: Sean Griffin 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 (PUP-5290) Puppet::Error raised by an indirector save method is silent
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5290 Puppet::Error raised by an indirector save method is silent Change By: Sean Griffin 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 (PUP-5001) Remove ubuntu 14.10 acceptance node definitions from source repos
Title: Message Title William Hopper commented on PUP-5001 Re: Remove ubuntu 14.10 acceptance node definitions from source repos Merged into master and stable. 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-5345) SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Title: Message Title Joshua Partlow commented on PUP-5345 Re: SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404 Hooray! Thanks Will. 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-2041) (maint) Simplify code in command.clj
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2041 (maint) Simplify code in command.clj Issue Type: Bug Assignee: Unassigned Created: 2015/10/08 3:39 PM Priority: Normal Reporter: gepetto-bot This PR cleans up the code in `command.clj`. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
Jira (PUP-5346) puppet_mcollective_service_management acceptance test fails on AIX
Title: Message Title John Duarte created an issue Puppet / PUP-5346 puppet_mcollective_service_management acceptance test fails on AIX Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Created: 2015/10/08 1:50 PM Environment: AIX 5.3 Priority: Normal Reporter: John Duarte The puppet acceptance test tests/resource/service/puppet_mcollective_service_management.rb fails with the following Test Case tests/resource/service/puppet_mcollective_service_management.rb reported: # h 4 running:
Jira (HI-464) Add node definition for Windows 10 (x86, x64) to Hiera
Title: Message Title John Duarte commented on HI-464 Re: Add node definition for Windows 10 (x86, x64) to Hiera See PR-464 for 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 (PUP-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Ryan Gard QA Risk Assessment Reason: This is a mostly a corner case, but it give me the opportunity to build a test VM with a Windows directory that is not "C:\Windows" which will be useful in the future. 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-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Ryan Gard QA Risk Assessment Reason: This is a corner case, but it give gives me the opportunity to build a test VM with a Windows directory that is not "C:\Windows" which will be useful in the future. 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-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Ryan Gard QA Risk Assessment Reason: This is a mostly a corner case, but it give me the opportunity to build a test VM with a Windows directory that is not "C:\Windows" which will be useful in the future. 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-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Ryan Gard Priority: Normal Blocker 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-5326) Tag the release and create packages
Title: Message Title Rob Braden commented on PUP-5326 Re: Tag the release and create packages http://builds.puppetlabs.lan/puppet-agent/1.2.6/ 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-5345) SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Title: Message Title
William Hopper commented on PUP-5345
Re: SysV init script managed by 'init' provider instead of 'debian' provider on Ubuntu1004,1204,1404
Joshua Partlow the good news is that the changes that went into puppet#master for PUP-5016 (specifically https://github.com/puppetlabs/puppet/commit/9071052aee9f9289897b6e2069ca1b78ebf07016) look to resolve this issue.
I was able to reproduce your exact issue on puppet agent 1.2.5, and then patched it with the new code. By default, we see:
root@jhgx2dg9wmcux3n:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service# puppet resource service puppet --param provider
service { 'puppet':
ensure => 'running',
enable => 'true',
provider => 'debian',
}
When enabling and disabling, we still use the upstart provider:
root@jhgx2dg9wmcux3n:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service# puppet resource service puppet enable=false --param provider
Jira (PDB-2041) (maint) Simplify code in command.clj
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2041 (maint) Simplify code in command.clj Change By: Andrew Roetker Scope Change Reason: had time, blocked a hack-day PR from Puppet conf Story Points: 1 Sprint: PuppetDB 2015-10-21 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 John Duarte commented on PUP-5189 Re: Add node definition for Windows 10 (x86, x64) to Puppet See PR-4330 for 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 (PUP-5347) Allow {{puppet agent}} to run even when disabled if {{--noop}} is given
Title: Message Title
Johnson Earls created an issue
Puppet / PUP-5347
Allow {{puppet agent}} to run even when disabled if {{--noop}} is given
Issue Type:
New Feature
Assignee:
Kylo Ginsberg
Components:
Client
Created:
2015/10/08 5:01 PM
Priority:
Normal
Reporter:
Johnson Earls
Currently, if the puppet agent is disabled (via puppet agent disable), the puppet agent will refuse to run.
Would it be possible to allow the puppet agent to run in --noop mode even when disabled?
This would be helpful when testing "quick fixes" for modules before pushing those modules into source code control.
Add Comment
Jira (PUP-5347) Allow puppet agent to run even when disabled if --noop is given
Title: Message Title
Johnson Earls updated an issue
Puppet / PUP-5347
Allow puppet agent to run even when disabled if --noop is given
Change By:
Johnson Earls
Summary:
Allow {{ puppet agent }} to run even when disabled if {{ --noop }} is given
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-2033) Spike: Design resilient terminus delivery from puppet master
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2033 Spike: Design resilient terminus delivery from puppet master 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 (FACT-1225) Get pre-suites working for Windows 10 (x86, x64) for Facter
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1225 Get pre-suites working for Windows 10 (x86, x64) for Facter Change By: John Duarte Assignee: 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 (HI-465) Get pre-suites working for Windows 10 (x86, x64) for Hiera
Title: Message Title John Duarte assigned an issue to John Duarte Hiera / HI-465 Get pre-suites working for Windows 10 (x86, x64) for Hiera Change By: John Duarte Assignee: 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-5190) Get pre-suites working for Windows 10 (x86, x64) for Puppet
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5190 Get pre-suites working for Windows 10 (x86, x64) for Puppet Change By: John Duarte Assignee: 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title
Tom Limoncelli commented on PUP-3483
Re: Systemd provider doesn't scan for changed units
It is now 3 months later and it looks like the recommended solution has an unintentional negative side-effect.
Many modules need this kind of functionality. They all do what you've recommended: Create a `Exec['systemd-tmpfiles-create']` which can be notify'ed any time a unit file is installed or modified. However, now many different modules use the same name and collide. If they use different names, systemd is told to "daemon-reload" multiple times, instead of having all the notify's collapsed into one Exec{}.
There are probably many solutions but one would be: Puppet Labs should bless a single module that defines the Exec[], so that all other modules can notify it. A module such as https://github.com/camptocamp/puppet-systemd would be a candidate, though I think the name should be different.
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-2040) Tool for generating demo data
Title: Message Title Carl Caum created an issue PuppetDB / PDB-2040 Tool for generating demo data Issue Type: New Feature Assignee: Unassigned Created: 2015/10/08 12:52 PM Priority: Normal Reporter: Carl Caum I need to be able to give Puppet Enterprise demos with realistic data that mimics a medium to large size infrastructure. Currently, the benchmark tool built into the PuppetDB source repository successfully generates data, but it has issues. The main PE console dashboard shows different data than Event Inspector Fact mutation is done in a way that's nonsensicle from a user perspective. For example, kernel, ipaddress, and other fact values will be replaced with a GUID string, rather than values that make sense for that particular fact The breadth of catalogs is limited to a basic Apache and PG installs. It would be nice to have catalogs, events, and facts for more types of roles and devices.
Jira (PDB-2003) facts GC can exceed jdbc max message size if too many paths are deleted
Title: Message Title Susan McNerney updated an issue PuppetDB / PDB-2003 facts GC can exceed jdbc max message size if too many paths are deleted Change By: Susan McNerney Scope Change Category: Adopted Scope Change Reason: community issue 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-1224) Add node definition for Windows 10 (x86, x64) to Facter
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1224 Add node definition for Windows 10 (x86, x64) to Facter Change By: John Duarte Assignee: 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 (HI-464) Add node definition for Windows 10 (x86, x64) to Hiera
Title: Message Title John Duarte assigned an issue to John Duarte Hiera / HI-464 Add node definition for Windows 10 (x86, x64) to Hiera Change By: John Duarte Assignee: 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-5189) Add node definition for Windows 10 (x86, x64) to Puppet
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-5189 Add node definition for Windows 10 (x86, x64) to Puppet Change By: John Duarte Assignee: 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-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Ryan Gard QA Status: Reviewed 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-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Ryan Gard QA Risk Assessment: Medium 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-4814) Path of scheduled tasks folder is not necessarily C:\Windows\Tasks
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4814 Path of scheduled tasks folder is not necessarily C:\Windows\Tasks Change By: Ryan Gard QA Contact: Eric Thompson Ryan Gard 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.
