Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Andrey Galkin commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters I've extended the test to shutdown PuppetServer & Puppet DB on primary master and PostgreSQL replica on secondary. The result is the same. I can provide scripts for complete setup of vagrant environment from scratch with a few clicks and around 10 minutes for processing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3386) Puppet Module Gem Dependency Metadata and Installation
Title: Message Title Sam McLeod commented on PUP-3386 Re: Puppet Module Gem Dependency Metadata and Installation Howdy, Just wondering if there's any update on this issue? We've just run up against it when needing to install a gem into puppet's environment as part of a provider. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Henrik Lindberg commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Wild guess: Facts posted on one master, read from the other? Posting facts goes to cache and PDB, PDB write is lazy? Read from master 2 does not have values in cache, hits PDB, and PDB write not yet complete? Reads old written value. henrik Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1431) Pre/Post-run commands don't work under Windows
Title: Message Title
Reid Vandewiele commented on PUP-1431
Re: Pre/Post-run commands don't work under Windows
A postrun_command with no spaces and no arguments seems to work.
PS C:\windows\system32> & puppet --version
3.8.7 (Puppet Enterprise 3.8.7)
PS C:\windows\system32> & puppet apply --postrun_command C:\true.bat -e 'notify { "foo": }'
Notice: Compiled catalog for windows-test in environment production in 0.14 seconds
Notice: foo
Notice: /Stage[main]/Main/Notify[foo]/message: defined 'message' as 'foo'
Notice: Finished catalog run in 0.03 seconds
Add Comment
Jira (FACT-1569) Add Ubuntu 16.10 to Ubuntu facts acceptance test
Title: Message Title Kenn Hussey commented on FACT-1569 Re: Add Ubuntu 16.10 to Ubuntu facts acceptance test Maggie Dreyer is this done now? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1569) Add Ubuntu 16.10 to Ubuntu facts acceptance test
Title: Message Title Maggie Dreyer commented on FACT-1569 Re: Add Ubuntu 16.10 to Ubuntu facts acceptance test Yes. I was waiting for it to see an actual pipeline run before resolving it though, just so there's a record of it working. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3276) Factset producer doesn't get updated
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3276 Factset producer doesn't get updated Change By: Russell Mull Fix Version/s: PDB 4.4.x Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3275) Generative command commutativity tests
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3275 Generative command commutativity tests Change By: Russell Mull Fix Version/s: PDB 4.4.x Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3277) Latest report is incorrectly determined with end_time
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3277 Latest report is incorrectly determined with end_time Change By: Russell Mull Fix Version/s: PDB 4.4.x Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7161) CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb
Title: Message Title Eric Delaney assigned an issue to qa Puppet / PUP-7161 CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb Change By: Eric Delaney Status: In Progress Ready for Test Assignee: Eric Delaney qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7159) CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures
Title: Message Title Eric Delaney assigned an issue to qa Puppet / PUP-7159 CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures Change By: Eric Delaney Status: In Progress Ready for Test Assignee: Eric Delaney qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7161) CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7161 CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb Fixed Solaris 11 OS image to not have zfs entries configured which conflicted with the acceptance tests Change By: Eric Delaney QA Risk Assessment Reason: The Solaris 11 OS base image was incorrect which caused the test failures QA Risk Assessment: Needs Assessment No Action QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Jeremy Barlow commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters I don't have any immediate ideas as to what might be causing this. It may be that the value of the 'fact_cache_issue' fact is somehow erroneously getting cached into the environment on the master instead of being processed from the agent's catalog request. If that were happening, it could be that a different value is being cached per JRuby instance on the server, causing the content which is applied to flop back and forth per agent run. I don't have any theories as to why switching from one master to another between agent runs may be causing the problem, though. It might be interesting to see if puppet.conf file on each of the masters - the primary and secondary - has any differences. What is the environment_timeout setting set to for the environment in question on each of the masters? Are both the primary and secondary masters running the same Puppet Server and puppet-agent versions? Henrik Lindberg or Thomas Hallgren - can you think of what might cause this problem? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7159) CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7159 CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures Change By: Eric Delaney Acceptance Criteria: acceptance test should pass when run on base solaris 11 OS image QA Risk Assessment Reason: The Solaris 11 OS base image was incorrect which caused the test failures QA Risk Assessment: Needs Assessment No Action Remaining Estimate: 1 minute Original Estimate: 1 minute QA Contact: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7161) CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7161 CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb Change By: Eric Delaney Sprint: AP Accepted 2017-02-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7159) CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7159 CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures Change By: Eric Delaney Sprint: AP Accepted 2017-02-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3294) Update i18n dev-resources
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3294 Update i18n dev-resources Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3294) Update i18n dev-resources
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3294 Update i18n dev-resources Issue Type: Bug Assignee: Unassigned Created: 2017/02/09 11:57 AM Labels: maintenance Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the
Jira (PUP-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza commented on PUP-7021 Re: Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module pulling into sprint given preceding support escalation is now up for pr and undergoing testing Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7021) Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-7021 Prevent incompatible encodings reaching Puppet::Parameter#format from ruby Etc module Change By: Moses Mendoza Sprint: AP 2017-01-25, AP 2017-02-08, AP 2017- 03 02 - 08 22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7181) Add function support to defined()
Title: Message Title Sean Millichamp commented on PUP-7181 Re: Add function support to defined() A "find_function" approach would be great too. Good point about function signatures. For my purpose I was assuming that the signatures would not be an issue. The motivation is that we have some early manifest bootstrapping logic which can (and does) vary per customer. Traditionally we have baked that all into one massive case statement in a single class that is the first thing we load. This had the downside of being difficult to maintain, test, manage, and certainly not nimble enough for others (less familiar with the code) to contribute new logic for new customers in a timely manner. I am currently reworking this logic to instead allow a Puppet language function to be written outside of the core module and then have which function gets called (via `call`) using a configurable setting (typically via a lookup in Hiera). This would permit the team to craft and deploy a custom function for a new customer in a rush situation outside of the change control process our core (versioned) code is required to follow. My thinking here was to check for the existence of the requested function and, if not found, either soft-fail (allow the catalog run to complete, raise an error via Notify, but skip most of the processing) or hard fail with an error that would provide additional help/site-specific direction to the user. Definitely in the "nice to have" category rather than required for this use case. Also, in my situation the most likely spot where these functions would appear won't be in versioned modules (either via git tag or a metadata.json-supplied version) so in this case I actually couldn't check for either. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6716 Error when purging local users on Windows Change By: Ethan Brown Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6722) Type/Provider Improvements - User Management Phase 1
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6722 Type/Provider Improvements - User Management Phase 1 Change By: Ethan Brown Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6812) Force --disable flag comment
Title: Message Title Geoff Nichols assigned an issue to Geoff Nichols Puppet / PUP-6812 Force --disable flag comment Change By: Geoff Nichols Assignee: Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7162) CI acceptance: failure Huawei tests/pluingsync/7316_apps_should_be_available_via_pluginsync.rb
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7162 CI acceptance: failure Huawei tests/pluingsync/7316_apps_should_be_available_via_pluginsync.rb Change By: Geoff Nichols Sprint: AP Accepted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7159) CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7159 CI acceptance: solaris 11 tests/resource/zfs/basic_tests.rb tests/resource/zfs/should_be_idempotent.rb failures Change By: Geoff Nichols Sprint: AP Accepted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7161) CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7161 CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb Change By: Geoff Nichols Sprint: AP Accepted Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7161) CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb
Title: Message Title Geoff Nichols assigned an issue to Eric Delaney Puppet / PUP-7161 CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb Change By: Geoff Nichols Assignee: Stan Duffy Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7161) CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb
Title: Message Title Geoff Nichols assigned an issue to Stan Duffy Puppet / PUP-7161 CI acceptance: solaris 11 failure tests/resource/zone.ticket_4840_should_create_zone_with_zpool.rb Change By: Geoff Nichols Assignee: Stan Duffy Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7162) CI acceptance: failure Huawei tests/pluingsync/7316_apps_should_be_available_via_pluginsync.rb
Title: Message Title Geoff Nichols assigned an issue to Stan Duffy Puppet / PUP-7162 CI acceptance: failure Huawei tests/pluingsync/7316_apps_should_be_available_via_pluginsync.rb Change By: Geoff Nichols Assignee: Stan Duffy Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6048) error running puppet with non existing and non default environment
Title: Message Title Branan Riley assigned an issue to Unassigned Puppet / PUP-6048 error running puppet with non existing and non default environment Change By: Branan Riley Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6048) error running puppet with non existing and non default environment
Title: Message Title Branan Riley assigned an issue to Branan Riley Puppet / PUP-6048 error running puppet with non existing and non default environment Change By: Branan Riley Assignee: Kylo Ginsberg Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5652) Windows Package provider does not work with Installshield with MSI files
Title: Message Title Corey Osman commented on PUP-5652 Re: Windows Package provider does not work with Installshield with MSI files Rob Reynolds It is not about having internal sources. It is about having to recreate all the choco packages that have hard coded external dependencies. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6635) An exec resource specifying a user will not inherit that user's limits from /etc/security/limits.conf
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6635 An exec resource specifying a user will not inherit that user's limits from /etc/security/limits.conf Change By: Geoff Nichols Labels: needs_epic Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7196) Intermittent test failure on Windows for Puppet::ModuleTool::Applications::Builder
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7196 Intermittent test failure on Windows for Puppet::ModuleTool::Applications::Builder Change By: Geoff Nichols Sprint: AP Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7184) Puppet::FileSystem should implement `readlines`
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7184 Puppet::FileSystem should implement `readlines` Change By: Geoff Nichols Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-145) Update module-related docs for Strings
Title: Message Title Jean Bond updated an issue Puppet Strings / PDOC-145 Update module-related docs for Strings Change By: Jean Bond * Rewrite Documenting Modules page: https://docs.puppet.com/puppet/latest/reference/modules_documentation.html* Revise module README template: https://docs.puppet.com/puppet/latest/reference/READMEtemplate.txt* BGTM: https://docs.puppet.com/guides/module_guides/bgtm.html (doesn't talk about docs, but should mention and reference strings as part of code)* - Style Guide: Replace documentation section and add in "how to doc your code with Strings, from README at least) - Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters thanks for filing Andrey Galkin Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters ping Jeremy Barlow Patrick Carlisle for review/awareness Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1544) Facter leaves behind cached facts if you enable fact TTLs in facter.conf and then remove those TTLs
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-1544 Facter leaves behind cached facts if you enable fact TTLs in facter.conf and then remove those TTLs Change By: Maggie Dreyer Sprint: AP 2017-02-08, AP 2017- 03 02 - 08 22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1569) Add Ubuntu 16.10 to Ubuntu facts acceptance test
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1569 Add Ubuntu 16.10 to Ubuntu facts acceptance test Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1569) Add Ubuntu 16.10 to Ubuntu facts acceptance test
Title: Message Title Maggie Dreyer created an issue Facter / FACT-1569 Add Ubuntu 16.10 to Ubuntu facts acceptance test Issue Type: Task Assignee: Unassigned Created: 2017/02/09 9:18 AM Priority: Normal Reporter: Maggie Dreyer The Ubuntu facts acceptance test (acceptance/tests/facts/ubuntu.rb) has a case statement with hardcoded data for each Ubuntu version. 16.10 needs to be added to this list in order for it to pass on the new platform. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7189) Add a fact value to log entries for subsequent classification
Title: Message Title Michael Smith updated an issue Puppet / PUP-7189 Add a fact value to log entries for subsequent classification Change By: Michael Smith Sprint: Puppet Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Michael Smith updated an issue Puppet / PUP-7198 Puppet Server uses facts from the previous run (n-1) after agent switches masters Change By: Michael Smith Sprint: Puppet Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5609) Puppet apply doesn't protect shared files with a lock
Title: Message Title Michael Smith updated an issue Puppet / PUP-5609 Puppet apply doesn't protect shared files with a lock Change By: Michael Smith Sprint: Puppet Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7199) Update to puppet-agent 1.9.0-1jessie breaks puppet master
Title: Message Title Morgan Rhodes moved an issue Puppet / PUP-7199 Update to puppet-agent 1.9.0-1jessie breaks puppet master Change By: Morgan Rhodes Key: CPR PUP - 406 7199 Project: Community Package Repository Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7189) Add a fact value to log entries for subsequent classification
Title: Message Title Steve Traylen commented on PUP-7189 Re: Add a fact value to log entries for subsequent classification > I'm not quite sure what you're getting at. Are you trying to associate the error with catalog compilation for a specific node? What would that fact be associated with? The fact would be associated with the node which produced the compilation error. Currently the fqdn is logged and this is of course very important and useful But one more fact would allow logs to be grouped by that fact very easily. So if my computer centre is cut up into partitions of nodetype=webserver , nodetype=databases, nodetypes=appplication. Then being to have that fact on the log line as well as the fqdn would make classification by nodetype so much easier. Clearly the particular factname should be a configuration. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Scott Nolin commented on PUP-1298 Re: manage_membership for unix groups provider I'm surprised this isn't i the default groups provider. Using the gpasswd based module does work - https://forge.puppet.com/onyxpoint/gpasswd Scott Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7111) a None data type in Puppet?
Title: Message Title Francois Lafont commented on PUP-7111 Re: a None data type in Puppet? Yes, big problem changing the behavior in resource creation passing undef to argument. We simply will not do that. Yes, I understand. Also, do not think a different kind of "no-value" value makes this anything but worse. Yes, after thinkings, I completely agree with you. I can imagine changing the syntax to allow a way to state that an undef does not mean default. I was unable to convince others of the merits of that though. [snip example with ==> and =>] Ah, personally this option could satisfy me and you have my support. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5808) puppet via sudo from nfs home is not working
Title: Message Title Thomas Mueller commented on PUP-5808 Re: puppet via sudo from nfs home is not working I've also seen this failure. we allow every user to trigger a puppet run with sudo. if I'm in the nfs-mounted homedir - where root has no access - I also see puppet runs failing. workaround is to switch cwd to something root-accessible. like cd /; sudo puppet agent -t Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7111) a None data type in Puppet?
Title: Message Title
Henrik Lindberg commented on PUP-7111
Re: a None data type in Puppet?
Yes, big problem changing the behavior in resource creation passing undef to argument. We simply will not do that. Also, do not think a different kind of "no-value" value makes this anything but worse. I can imagine changing the syntax to allow a way to state that an undef does not mean default. I was unable to convince others of the merits of that though.
Example:
class { 'mymod':
foo ==> undef, # force undef
bar => undef, # same as value not given
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7111) a None data type in Puppet?
Title: Message Title
Francois Lafont commented on PUP-7111
Re: a None data type in Puppet?
Hi.
Thanks Henrik Lindberg for your answer and sorry for my late answer.
Indeed the default value can be relevant but, imho, only to set a real default value of a class. Personally the meaning of my None value is not the same as the default value. The meaning of my None value is really "I provide no value for this parameter". In fact the meaning of my None value is clearly undef but the problem of undef value for me is that it's impossible to pass this value in a resource-like declaration.
Of course, I know well the (very nice) data binding mechanism etc. (with hiera or the function data provider) and I use it daily. But I use too classes via resource-like declarations, especially in my high-level classes which I call my "roles".
In fact, the real solution to my problem could be the undef value and in my "roles" classes I would like to put this:
class { 'mymod':
foo => undef,
}
even if the undef value is not the default value.
In clear, I completely agree with you when you say "I think that passing an explicit undef in a resource _expression_ should not pick the default value if it is acceptable to assign undef to the parameter" and this is in fact exactly my problem here and my idea of a None value is in fact a workaround as regards this problem (so, as all workarounds, this is so not necessarily a good idea).
But of course, I guess that changing this behavior (foo => undef doesn't mean anaymore "take the defaut value" but "set foo to undef") is big decision, because it breaks the backward compatibility.
Add Comment
Jira (PUP-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title
Andrey Galkin updated an issue
Puppet / PUP-7198
Puppet Server uses facts from the previous run (n-1) after agent switches masters
Change By:
Andrey Galkin
I couldn't believe that, but I could finally reliably reproduce the problem in minimal sample. I've observed that episodically and believe this is a long standing issue - the reason I do not put Critical to this.Ruby fact plugin:{code:ruby}Facter.add('fact_cache_issue') dosetcode dobeginFile.read('/etc/fact_cache_issue')rescueendendend{code}Puppet code:{code:puppet}class factcacheissue {$value = $::facts['fact_cache_issue'] ? {undef => generate('/usr/bin/openssl', 'rand', '-hex', '8'),default => $::facts['fact_cache_issue']}file { '/etc/fact_cache_issue':content => $value,}}node cacheissue.example.com {include factcacheissuefile {'/etc/puppetlabs/puppet/puppet.conf':mode=> '0644',content => '[main]client = falsecertname = cacheissue.example.comserver = puppetback.example.comca_server = puppet.example.comenvironment = productionsrv_domain = example.comuse_srv_records = false',}}{code}1. Setup puppet-agent 1.9.0 package2. Run against CA server puppet.example.com3. During the first initialization, openssl generator is called and puppet server is changed to secondary master (puppetback.example.com)4. Second run goes to secondary master. Master stores facts PuppetDB, but Master does not see new facts during catalog compilations => calls openssl generator again .5. Each next run uses fact set from run #n-1 - *that's very weird*, and produces resource value switch to previous run.6. If puppet server is not switched then everything is correct.Command line output:{noformat}Setting up puppet-agent (1.9.0-1jessie) ...Configuration file '/etc/puppetlabs/puppet/puppet.conf' ==> File on system created by you or by a script. ==> File also in package provided by package maintainer. ==> Using current old file as you requested.Created symlink from /etc/systemd/system/multi-user.target.wants/puppet.service to /lib/systemd/system/puppet.service.Created symlink from /etc/systemd/system/multi-user.target.wants/mcollective.service to /lib/systemd/system/mcollective.service.Created symlink from /etc/systemd/system/multi-user.target.wants/pxp-agent.service to /lib/systemd/system/pxp-agent.service.Removed symlink /etc/systemd/system/multi-user.target.wants/pxp-agent.service.+ PUPPET=/opt/puppetlabs/bin/puppet+ /opt/puppetlabs/bin/puppet resource service puppet ensure=false enable=false provider=systemdNotice: /Service[puppet]/enable: enable changed 'true' to 'false'service { 'puppet': ensure => 'stopped', enable => 'false',}+ systemctl mask puppetCreated symlink from /etc/systemd/system/puppet.service to /dev/null.+ host maint.example.com+ /opt/puppetlabs/bin/puppet agent --test --traceInfo: Creating a new SSL key for cacheissue.example.comInfo: Caching certificate for caInfo: csr_attributes file loading from /etc/puppetlabs/puppet/csr_attributes.yamlInfo: Creating a new SSL certificate request for cacheissue.example.comInfo: Certificate Request fingerprint (SHA256): DA:8A:E9:2C:01:A4:2B:B4:DA:28:66:89:8D:91:9B:4F:76:DF:62:4F:EA:A5:28:68:03:0B:20:92:03:01:70:01Info: Caching
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title Thomas Honey commented on PUP-7197 Re: make type aliases from modules available on the agent +1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title David Schmitt created an issue Puppet / PUP-7197 make type aliases from modules available on the agent Issue Type: Story Assignee: Unassigned Created: 2017/02/09 1:32 AM Priority: Normal Reporter: David Schmitt As a provider author, I want to have access to type aliases in code running on the agent So that I can avoid duplication and drift in my code Currently DSL data type aliases are only available with direct access to the installed module. For both the netconf, and new Resource API efforts, it is necessary to transport these definitions to agents (presumably via pluginsync) so that their infrastructure code can rely on the definitions. CC Rick Sherman Thomas Honey Henrik Lindberg Thomas Hallgren Add Comment
Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title R.I.Pienaar commented on HI-257 Re: Dynamic hierarchy based on fact/variable Henrik Lindberg this is the feature discussed at contributor summit, I suspect with the new code base we're in a better position to reconsider the feasibility of including this? Good history on the PR https://github.com/puppetlabs/hiera/pull/193 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
