Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title Josh Cooper commented on PUP-1131 Re: Puppet raises error when trying to set owner to non-existant user Puppet no longer requires that the puppet user exist, so this particular issue has been resolved, and I'm re-closing this. There is a second issue where puppet will raise an exception if there isn't a suitable user provider, filed as PUP-1162. You can see the problem on line 382: https://github.com/puppetlabs/puppet/blob/3.7.5/lib/puppet/type/user.rb#L382 due to provider being nil. We've seen this problem on centos when running as non-root, because useradd isn't world-executable. I imagine something similar is going on with Solaris. Chris Denneen please follow PUP-1162 for updates. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured
Title: Message Title Branan Riley commented on PUP-6475 Re: Agent should use first entry of server_list in cases where failover has not occured John DuarteSince this is being rolled out as part of the initial HA implementation, I think it falls under whatever notes/documentation we have for that, with no need for anything special here Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured
Title: Message Title Branan Riley updated an issue Puppet / PUP-6475 Agent should use first entry of server_list in cases where failover has not occured Change By: Branan Riley Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6350) Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk
Title: Message Title Kenneth Barber commented on PUP-6350 Re: Include last_transaction_uuid if exists, in a report to aid in timelining for PDB and its ilk Since our plans have been diverted from this, I'm closing it for now. If we need it again, we'll re-open or make a new ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6491) "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Title: Message Title
Ruth Linehan updated an issue
Puppet / PUP-6491
"No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Change By:
Ruth Linehan
Puppet Server master bumped to e759f3ccea8e4ca89edccb7921c6b628e9314eb1 of puppet and now getting failures in {{acceptance/tests/face/parser_validate.rb}} with:{code} qqe0bf13xxw93w9.delivery.puppetlabs.net (redhat6-64-1) 14:29:25$ puppet parser validate /tmp/parser_validate.hlQ6J6/parser_validate_broken.ppError: Could not parse for environment production: This Name has no effect. A value was produced and then forgotten (one or more preceding expressions may have the wrong form) at /tmp/parser_validate.hlQ6J6/parser_validate_broken.pp:1:1qqe0bf13xxw93w9.delivery.puppetlabs.net (redhat6-64-1) executed in 1.09 seconds Exited: 1* (large) manifest with exported resources Errno::ENOENT: No such file or directory - fixtures/manifest_large_exported_classes_node.pp /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/ruby/puppet/acceptance/tests/face/parser_validate.rb:49 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/ruby/puppet/acceptance/tests/face/parser_validate.rb:49 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/vendor/bundler/ruby/1.9.1/gems/beaker-2.44.0/lib/beaker/dsl/structure.rb:43 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/ruby/puppet/acceptance/tests/face/parser_validate.rb:47 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/ruby/puppet/acceptance/tests/face/parser_validate.rb:9 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/ruby/puppet/acceptance/tests/face/parser_validate.rb:9 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/vendor/bundler/ruby/1.9.1/gems/beaker-2.44.0/lib/beaker/dsl/structure.rb:58 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/ruby/puppet/acceptance/tests/face/parser_validate.rb:1 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/vendor/bundler/ruby/1.9.1/gems/beaker-2.44.0/lib/beaker/test_case.rb:133 /var/lib/jenkins/workspace/platform_puppetserver_integration-system_no-conditional_full-master/LAYOUT/redhat6-64ma-64a/LDAP_TYPE/default/PLATFORM/default/label/beaker/vendor/bundler/ruby/1.
Jira (PUP-6491) "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Title: Message Title Ruth Linehan assigned an issue to Eric Thompson Puppet / PUP-6491 "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test Change By: Ruth Linehan Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6491) "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test
Title: Message Title Ruth Linehan created an issue Puppet / PUP-6491 "No such file or directory - fixtures/manifest_large_exported_classes_node" in parser_validate acceptance test Issue Type: CI Blocker Assignee: Unassigned Created: 2016/07/11 5:20 PM Priority: Normal Reporter: Ruth Linehan Puppet Server master bumped to e759f3ccea8e4ca89edccb7921c6b628e9314eb1 of puppet and now getting failures in acceptance/tests/face/parser_validate.rb with: qqe0bf13xxw93w9.delivery.puppetlabs.net (redhat6-64-1) 14:29:25$ puppet parser validate /tmp/parser_validate.hlQ6J6/parser_validate_broken.pp Error: Could not parse for environment production: This Name has no effect. A value was produced and then forgotten (one or more preceding expressions may have the wrong form) at /tmp/parser_validate.hlQ6J6/parser_validate_broken.pp:1:1
Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured
Title: Message Title John Duarte commented on PUP-6475 Re: Agent should use first entry of server_list in cases where failover has not occured Branan Riley, are release notes needed for this or is this covered by another ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured
Title: Message Title John Duarte updated an issue Puppet / PUP-6475 Agent should use first entry of server_list in cases where failover has not occured Change By: John Duarte QA Risk Assessment Reason: critical for consistent behavior when server_list is used Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured
Title: Message Title John Duarte updated an issue Puppet / PUP-6475 Agent should use first entry of server_list in cases where failover has not occured Change By: John Duarte QA Highest Test Level Reason: The evaluation of the server_list array is internal to the ruby implementation Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured
Title: Message Title John Duarte updated an issue Puppet / PUP-6475 Agent should use first entry of server_list in cases where failover has not occured Change By: John Duarte QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured
Title: Message Title John Duarte updated an issue Puppet / PUP-6475 Agent should use first entry of server_list in cases where failover has not occured Change By: John Duarte QA Highest Test Level: Unit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1448) facter json output converts all booleans to true
Title: Message Title John Duarte commented on FACT-1448 Re: facter json output converts all booleans to true Using released puppet-agent version 1.5.2 containing facter version 3.2.0, the updated acceptance test in PR 1373 fails as expected. Test Case tests/options/json.rb reported: # --- expected +++ actual @@ -6,6 +6,6 @@ \"bar\": \"value2\", \"baz\": \"value3\", \"true\": true, -\"false\": false +\"false\": true } }"
Jira (FACT-1448) facter json output converts all booleans to true
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1448 facter json output converts all booleans to true Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1448) facter json output converts all booleans to true
Title: Message Title John Duarte updated an issue Facter / FACT-1448 facter json output converts all booleans to true Change By: John Duarte QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1448) facter json output converts all booleans to true
Title: Message Title John Duarte updated an issue Facter / FACT-1448 facter json output converts all booleans to true Change By: John Duarte QA Risk Assessment Reason: Critical regression Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4660) Stop checking Puppet.features.external_facts?
Title: Message Title John Duarte updated an issue Puppet / PUP-4660 Stop checking Puppet.features.external_facts? Change By: John Duarte QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4660) Stop checking Puppet.features.external_facts?
Title: Message Title John Duarte updated an issue Puppet / PUP-4660 Stop checking Puppet.features.external_facts? Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4660) Stop checking Puppet.features.external_facts?
Title: Message Title John Duarte updated an issue Puppet / PUP-4660 Stop checking Puppet.features.external_facts? Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1462) Allow disabling subsections of structured facts
Title: Message Title Branan Riley created an issue Facter / FACT-1462 Allow disabling subsections of structured facts Issue Type: New Feature Assignee: Unassigned Created: 2016/07/11 3:59 PM Priority: Normal Reporter: Branan Riley Allow disabling sub-facts so that they are not submitted to the master. For the initial implementation, this is considered a way to avoid sending facts across the network or storing them in puppetdb - the only way to actually disable resolution will be to turn off top-level structured facts as in FACT-718 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Branan Riley assigned an issue to Unassigned Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Branan Riley Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Branan Riley updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Branan Riley Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1461) Reload facter.conf when puppet reloads its configuration
Title: Message Title Branan Riley created an issue Facter / FACT-1461 Reload facter.conf when puppet reloads its configuration Issue Type: New Feature Assignee: Unassigned Created: 2016/07/11 3:54 PM Priority: Normal Reporter: Branan Riley Puppet will need to call into a new API on the facter side to reload configuration when needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1459) Allow specifying the config file from command line
Title: Message Title Branan Riley updated an issue Facter / FACT-1459 Allow specifying the config file from command line Change By: Branan Riley Summary: Allow specifying the config file from command line or when library is loaded Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1460) Load facter.conf when facter. is used as a library
Title: Message Title Branan Riley created an issue Facter / FACT-1460 Load facter.conf when facter. is used as a library Issue Type: New Feature Assignee: Unassigned Created: 2016/07/11 3:50 PM Priority: Normal Reporter: Branan Riley Facter should load its config file (excluding the CLI section) when it is used as a library. If the library consumer specifies any configuration, that should take precedence (similar to how command line overrides facter.conf in standalone mode) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1459) Allow specifying the config file from command line or when library is loaded
Title: Message Title Branan Riley created an issue Facter / FACT-1459 Allow specifying the config file from command line or when library is loaded Issue Type: New Feature Assignee: Unassigned Created: 2016/07/11 3:48 PM Priority: Normal Reporter: Branan Riley The default location of the config file should be overrideable for testing and/or special environments Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1458) Allow setting existing facter config flags from the config file
Title: Message Title Branan Riley created an issue Facter / FACT-1458 Allow setting existing facter config flags from the config file Issue Type: New Feature Assignee: Unassigned Created: 2016/07/11 3:45 PM Priority: Normal Reporter: Branan Riley Main: [no]-custom-facts [no]-external-facts [no]-ruby Cli: debug trace verbose log-level Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1457) Spike HOCON access layer
Title: Message Title Branan Riley created an issue Facter / FACT-1457 Spike HOCON access layer Issue Type: Task Assignee: Unassigned Created: 2016/07/11 3:40 PM Priority: Normal Reporter: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1456) Spike HOCON integration into boost::program_options
Title: Message Title Branan Riley updated an issue Facter / FACT-1456 Spike HOCON integration into boost::program_options Change By: Branan Riley Sprint: Client 2016-07-27 facter.conf Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1456) Spike HOCON integration into boost::program_options
Title: Message Title Branan Riley created an issue Facter / FACT-1456 Spike HOCON integration into boost::program_options Issue Type: Task Assignee: Unassigned Created: 2016/07/11 3:33 PM Priority: Normal Reporter: Branan Riley It would be super cool to be ableto use boost:po as the standard way of dealing with C++ project configuration. We should investigate whether it's possible to hook our preferred config file format (hocon) into boost:po Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6457) Mount resources could handle invalid options better
Title: Message Title Kylo Ginsberg commented on PUP-6457 Re: Mount resources could handle invalid options better I haven't dug into this at all, but do we know if https://github.com/puppetlabs/puppetlabs-mount_providers has this problem? My understanding is that the module is generally recommended/better in several regards. If it handles this issue properly, perhaps we recommend that as the path going forward. And otoh, if not, we should probably put up a ticket to fix the same issue in the module. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6485) make it easier to require based on tag
Title: Message Title Henrik Lindberg commented on PUP-6485 Re: make it easier to require based on tag We would like a query that is just that and that produces references to resources that you then operate on (like in this case, add dependencies on them). The difficult issues are how to deal with late binding logic - now there is a precedence among them - it is far from perfect. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6489) Windows service resource doesn't understand trigger start services
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-6489
Windows service resource doesn't understand trigger start services
Change By:
Ethan Brown
Windows services can be configured as {{trigger start}}, which means while the service is started, it may not always be running at the time that Puppet looks at it. When using a manifest with {{enable => 'true', ensure => 'running'}}, this may mean Puppet is constantly turning the service back on, even though it probably shouldn't. Changing {{ensure}} to {{scheduled}} would likely be very difficult to manage right now... so uncertain yet what the best approach would be:The docs for Service trigger events are at https://msdn.microsoft.com/en-us/library/windows/desktop/dd405513(v=vs.85).aspx The code that deals with Windows service types is at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/windows.rb#L46-L54 The gem we're using does have the constants available associated with trigger starts:https://github.com/djberg96/win32-service/blob/ffi/lib/win32/windows/constants.rb#L88This was discovered while looking at the MODULES-2420 and the Windows {{wuaserv}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For
Jira (PUP-5427) incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env.
Title: Message Title Geoff Nichols commented on PUP-5427 Re: incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env. Mikhail T. - thanks! I have opened a new issue at PUP-6488 to track the issues you identified. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6489) Windows service resource doesn't understand trigger start services
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6489 Windows service resource doesn't understand trigger start services Change By: Ethan Brown Summary: Windows service resource doesn't understand trigger start service type services Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6489) Windows service resource doesn't understand trigger start service type
Title: Message Title Ethan Brown created an issue Puppet / PUP-6489 Windows service resource doesn't understand trigger start service type Issue Type: Bug Affects Versions: PUP 4.5.2 Assignee: Unassigned Components: Windows Created: 2016/07/11 2:20 PM Priority: Normal Reporter: Ethan Brown Windows services can be configured as trigger start, which means while the service is started, it may not always be running at the time that Puppet looks at it. When using a manifest with enable => 'true', ensure => 'running', this may mean Puppet is constantly turning the service back on, even though it probably shouldn't. Changing ensure to scheduled would likely be very difficult to manage right now... so uncertain yet what the best approach would be: The docs for Service trigger events are at https://msdn.microsoft.com/en-us/library/windows/desktop/dd405513(v=vs.85).aspx The gem we're using does have the constants available associated with trigger starts: https://github.com/djberg96/win32-service/blob/ffi/lib/win32/windows/constants.rb#L88 This was discovered while looking at the MODULES-2420 and the Windows wuaserv
Jira (PUP-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6115 The instructions for cleaning a Windows node's certificate are wrong Change By: Craig Gomes Acceptance Criteria: No more errors in instructions to user. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-6115 The instructions for cleaning a Windows node's certificate are wrong Change By: Glenn Sarti QA Status: Reviewed QA Contact: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH
Title: Message Title
Geoff Nichols created an issue
Puppet / PUP-6488
Gem provider should allow alternative gem command; should not rely on $PATH
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2016/07/11 2:17 PM
Priority:
Normal
Reporter:
Geoff Nichols
In PUP-5427, Mikhail T. commented:
The gem-provider should not rely on the $PATH for the default gem – it must explicitly invoke the gem-executable appropriate for the underlying OS. On Linux that's /usr/bin/gem, on FreeBSD that's typically /usr/local/bin/gem and so on.
The gem-provider must allow specifying an alternative gemcmd. People have been asking for this for years. Something like:
package {'foo':
ensure => 'latest',
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Craig Gomes Sprint: Windows 2016- 07 08 - 27 10 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Craig Gomes Sprint: Windows Triage 2016-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6382 Add "Automatic (delayed start)" as option for Service Resource on Windows Change By: Craig Gomes Sprint: Windows Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6330) puppet uninstall exe resource fails on windows due to missing quotes
Title: Message Title Craig Gomes commented on PUP-6330 Re: puppet uninstall exe resource fails on windows due to missing quotes Max, Do you anticipate upgrading? This version of Puppet is only receiving critical security fixes at this point in time. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6116) Add additional triggers like "ONLOGON" to scheduled_task resource on Windows
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6116 Add additional triggers like "ONLOGON" to scheduled_task resource on Windows Change By: Craig Gomes Sprint: Windows Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6076) Set additional settings for triggers and/or overall task with scheduled_task
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6076 Set additional settings for triggers and/or overall task with scheduled_task Change By: Craig Gomes Sprint: Windows Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6438) Parallel spec on Windows improvements, assoc lib/provider refactors
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6438 Parallel spec on Windows improvements, assoc lib/provider refactors Change By: Craig Gomes As per comments on https://github.com/puppetlabs/puppet/pull/5041* Refactor lib/provider files to expose $CHILD_STATUS. exitstatus exit status to the spec tests in a way that allows stubbing / mocking as with execution_spec or pacman_spec* Take a closer look at settings_spec changes. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6438) Parallel spec on Windows improvements, assoc lib/provider refactors
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6438 Parallel spec on Windows improvements, assoc lib/provider refactors Change By: Craig Gomes As per comments on https://github.com/puppetlabs/puppet/pull/5041* Refactor lib/provider files to expose $CHILD_STATUS.exitstatus to the spec tests in a way that allows stubbing / mocking as with execution_spec or pacman_spec* Decide between fixing mocking for launchd_spec OS X specific tests in Windows, and guarding.* Take a closer look at settings_spec changes. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Craig Gomes updated an issue Hiera / HI-519 Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 Change By: Craig Gomes Sprint: Windows 2016- 07 08 - 27 24 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1446) Improve the windows user check in facter/acceptance/test/facts/window.rb
Title: Message Title Craig Gomes updated an issue Facter / FACT-1446 Improve the windows user check in facter/acceptance/test/facts/window.rb Change By: Craig Gomes Sprint: Windows 2016- 07 08 - 27 24 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6457) Mount resources could handle invalid options better
Title: Message Title Hailee Kenney commented on PUP-6457 Re: Mount resources could handle invalid options better With a lot of help from Adrien Thebo, I've been making progress on this ticket. I've hit a little bit of a roadblock however. The beginnings of the solution we came up with can be found in this commit. The problem basically is that puppet is failing to detect when a mount has failed due to bad options and does not attempt to remount. This is because it is comparing only two sources and ensuring they match but neither source reflects what is actually mounted. When puppet attempts to mount a resource with invalid options, the mount will fail BUT the new options will be listed in /etc/fstab. On the next puppet run, puppet will compare the defined resource to /etc/fstab and find that the options match, thus it will not attempt to remount. So puppet will give the impression that the remount with the new options is no longer failing which is incorrect. However, the output of the mount command does reveal that the resource did not successfully remount with the new problematic options. The options listed for the mounted file system from the mount command are not the update options which match the manifest, but the old ones which do not match the user defined resource. Thus we decided that the way to solve this problem was to also check the options for the mounted file system as they are in the output of the mount command, and if they do not match we know that the resource is not in sync with what is on the system and that we should attempt another remount. This was all working until we realized the difference between /etc/fstab and the output of mount for default mount options. /etc/fstab will list the string "defaults" but mount will list the full list of default options. That means for this case, it's impossible to compare if the two are in sync unless we devise some kind of insane lookup table that tells us for each type of file system and operating system (and probably some more parameters honesty) what the list of default options should look like. This has left us stumped, and we're looking for some ideas. Either a new approach, or a solution to the problem just described. Or the go ahead to attempt to construct the insane archive of default options for every OS we support. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6037) File Permissions are set wrong in puppet
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6037 File Permissions are set wrong in puppet Change By: Eric Thompson QA Risk Assessment: High Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6037) File Permissions are set wrong in puppet
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6037 File Permissions are set wrong in puppet Change By: Eric Thompson QA Risk Assessment Reason: escaped, reported from outside feature Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6115) The instructions for cleaning a Windows node's certificate are wrong
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6115 The instructions for cleaning a Windows node's certificate are wrong Change By: Craig Gomes Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6423) The scheduled_task provider performs incorrect matching on file names
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6423 The scheduled_task provider performs incorrect matching on file names Change By: Craig Gomes Sprint: Windows 2016- 07 08 - 27 10 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5948) write tool to transform ruby resource type to pcore resource type
Title: Message Title Peter Huene commented on PUP-5948 Re: write tool to transform ruby resource type to pcore resource type I'm going to mark this as ready for merge so we can review what has already been committed to https://github.com/peterhuene/puppet-generate. It needs unit tests still, but I'm waiting on the OK from product regarding the expected user story and experience for this tool. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Craig Gomes Sprint: Windows 2016- 07 08 - 27 10 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6347) new function (String): programmatic representation escapes for Ruby language and not Puppet
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6347 new function (String): programmatic representation escapes for Ruby language and not Puppet Change By: Eric Thompson QA Highest Test Level: Unit Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6347) new function (String): programmatic representation escapes for Ruby language and not Puppet
Title: Message Title
Eric Thompson commented on PUP-6347
Re: new function (String): programmatic representation escapes for Ruby language and not Puppet
validated on ubuntu1404 at puppet-agent stable SHA: │d8d9047b9271a282b370079a078af17f170a8305
root@qne9q5hydtdyji1:~# puppet apply -e "notice String('foo#{bar}', '%p')
> "
Notice: Scope(Class[main]): 'foo#{bar}'
Notice: Compiled catalog for qne9q5hydtdyji1.delivery.puppetlabs.net in environment production in 0.04 seconds
Notice: Applied catalog in 0.10 seconds
root@qne9q5hydtdyji1:~# puppet apply -e "notice String('$foobar', '%p')
> "
Notice: Scope(Class[main]): ''
Notice: Compiled catalog for qne9q5hydtdyji1.delivery.puppetlabs.net in environment production in 0.04 seconds
Jira (PUP-6347) new function (String): programmatic representation escapes for Ruby language and not Puppet
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6347 new function (String): programmatic representation escapes for Ruby language and not Puppet Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6347) new function (String): programmatic representation escapes for Ruby language and not Puppet
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6347 new function (String): programmatic representation escapes for Ruby language and not Puppet Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6042) `puppet agent --test` does not override cached catalog behavior
Title: Message Title Adrien Thebo commented on PUP-6042 Re: `puppet agent --test` does not override cached catalog behavior I want to understand the use case of using cached catalogs with the orchestrator a bit and why one would use puppet agent -t on a node that's using cached catalogs by default - it seems like ignoring the cached catalog when doing a oneshot run may cause one node within an environment to have a catalog version that's not compatible with the rest of the nodes in that environment. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2734) Create upgrade/migration code for ActiveMQ
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2734 Create upgrade/migration code for ActiveMQ Change By: Andrew Roetker Assignee: Andrew Roetker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2855) PQL - Possibility to create fact arrays like from Puppetdbquery
Title: Message Title Wyatt Alt commented on PDB-2855 Re: PQL - Possibility to create fact arrays like from Puppetdbquery André Bauer the tickets to follow are PDB-2632 and PDB-2633. There will likely be a couple of follow-up tickets but those two cover the bulk of the work. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2864) (WIP) Sync with threadpool
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2864 (WIP) Sync with threadpool Issue Type: Bug Assignee: Unassigned Created: 2016/07/11 11:13 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6487) puppet-agent fails to build on/for ubuntu, huawei
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6487 puppet-agent fails to build on/for ubuntu, huawei Change By: Geoff Nichols Scope Change Category: Found Scope Change Reason: CI blocker Story Points: 1 Sprint: RE Platforms 2016-07-13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Erik Dasher updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Erik Dasher QA Risk Assessment Reason: Testing and Risk Assessment documented in HI-525. QA Status: Reviewed QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-523) Add support for using hocon for main hiera config file
Title: Message Title Erik Dasher updated an issue Hiera / HI-523 Add support for using hocon for main hiera config file Change By: Erik Dasher QA Risk Assessment Reason: Testing and Risk Assessment documented in HI-525. QA Status: Reviewed QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-524) determine strategy for something like eyaml for hocon
Title: Message Title Erik Dasher updated an issue Hiera / HI-524 determine strategy for something like eyaml for hocon Change By: Erik Dasher QA Risk Assessment Reason: Testing and Risk Assessment documented in HI-525. QA Status: Reviewed QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6476) Add Hocon support to Puppet
Title: Message Title Erik Dasher updated an issue Puppet / PUP-6476 Add Hocon support to Puppet Change By: Erik Dasher QA Risk Assessment Reason: Testing and Risk Assessment documented in HI-525. QA Status: Reviewed QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6487) puppet-agent fails to build on/for ubuntu, huawei
Title: Message Title Rick Sherman commented on PUP-6487 Re: puppet-agent fails to build on/for ubuntu, huawei I updated debmirror to ignore missing release packages as Ubuntu 10.04 is no longer mirrored upstream. The unintended consequence of that was the removal of the Packages/Sources archive and release.gpg files. I manually copied those over from the shermdog-mirror Ubuntu 10.04 repo (essentially online backup) and set those files immutable. Re-ran debmirror and did not experience any issues. Validated Ubuntu 10.04 VM's are able to install packages from osmirror. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-525) test coverage for hiera/lookup hocon support
Title: Message Title Erik Dasher updated an issue Hiera / HI-525 test coverage for hiera/lookup hocon support Change By: Erik Dasher QA Risk Assessment Reason: New Feature QA Risk Assessment: High QA Status: Reviewed QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6487) puppet-agent fails to build on/for ubuntu, huawei
Title: Message Title Rick Sherman commented on PUP-6487 Re: puppet-agent fails to build on/for ubuntu, huawei huawei release package was not updated and did not include updated release gpg key. It is now a symlink to the latest jessie package. pl-build-tools-release-huaweios.deb -> pl-build-tools-release-jessie.deb Validated with a local puppet-agent build. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2863) Limit the connect-pool size for the Migrations pool
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2863 Limit the connect-pool size for the Migrations pool Issue Type: Improvement Assignee: Unassigned Created: 2016/07/11 10:28 AM Priority: Normal Reporter: Andrew Roetker There' not really a reason to have a connection-pool size for the migrations pool greater than 1 as far as I can tell. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6487) puppet-agent fails to build on/for ubuntu, huawei
Title: Message Title Eric Thompson created an issue Puppet / PUP-6487 puppet-agent fails to build on/for ubuntu, huawei Issue Type: CI Blocker Assignee: Rick Sherman Created: 2016/07/11 10:18 AM Priority: Normal Reporter: Eric Thompson https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_pkg-van-ship_daily-master/269/ missing packages, it appears Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1454) When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults
Title: Message Title Rajasree Talla updated an issue Facter / FACT-1454 When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults Change By: Rajasree Talla Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1454) When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults
Title: Message Title Andrew Henroid commented on FACT-1454 Re: When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults I've reproduced this, and it appears to be related to garbage collection changes in Ruby 2.3.1. I can make this behavior disappear with a one line patch to Ruby, but more diagnosis ahead to get to the underlying cause. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6437) directoryservice user provider crashes if no ShadowHashData is found
Title: Message Title William Hopper updated an issue Puppet / PUP-6437 directoryservice user provider crashes if no ShadowHashData is found Change By: William Hopper Release Notes Summary: This change fixes an issue with the directoryservice user provider in OSX, where puppet would crash in certain circumstances while fetching bad ShadowHashData from the system. Puppet now handles this gracefully. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title J.D. Welch commented on HI-341 Re: Hiera should support native HOCON to match Puppet Server OK. Sounds reasonable. +1 to .hocon then, I guess. We'll set the precedent! Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Ethan Brown Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6415) static_compiler: symlinks in recursed directories don't work
Title: Message Title
William Hopper updated an issue
Puppet / PUP-6415
static_compiler: symlinks in recursed directories don't work
Change By:
William Hopper
Release Notes Summary:
This change fixes an issue in the (now deprecated) static compiler where symlinks in recursed directories did not end up with {{target}} attributes, causing Puppet to fail to manage them.Note that this only affects the static compiler, and *not* the newer static catalog functionality which was added as part of the direct puppet workflow.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1454) When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults
Title: Message Title Andrew Henroid assigned an issue to Andrew Henroid Facter / FACT-1454 When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults Change By: Andrew Henroid Assignee: Andrew Henroid Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4660) Stop checking Puppet.features.external_facts?
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-4660 Stop checking Puppet.features.external_facts? Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6440) Tag transaction events with sensitive data
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-6440 Tag transaction events with sensitive data Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6347) new function (String): programmatic representation escapes for Ruby language and not Puppet
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-6347 new function (String): programmatic representation escapes for Ruby language and not Puppet Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1448) facter json output converts all booleans to true
Title: Message Title Eric Thompson assigned an issue to qa Facter / FACT-1448 facter json output converts all booleans to true Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured
Title: Message Title Eric Thompson assigned an issue to qa Puppet / PUP-6475 Agent should use first entry of server_list in cases where failover has not occured Change By: Eric Thompson Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2858) stockpile: report detailed rm-r errors during tests
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-2858 stockpile: report detailed rm-r errors during tests Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1406) mountpoints size and used values can be corrupt on 32-bit linux or bsd
Title: Message Title John Duarte updated an issue Facter / FACT-1406 mountpoints size and used values can be corrupt on 32-bit linux or bsd Change By: John Duarte QA Risk Assessment: Low High Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1406) mountpoints size and used values can be corrupt on 32-bit linux or bsd
Title: Message Title John Duarte updated an issue Facter / FACT-1406 mountpoints size and used values can be corrupt on 32-bit linux or bsd Change By: John Duarte QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1406) mountpoints size and used values can be corrupt on 32-bit linux or bsd
Title: Message Title John Duarte updated an issue Facter / FACT-1406 mountpoints size and used values can be corrupt on 32-bit linux or bsd Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6037) File Permissions are set wrong in puppet
Title: Message Title John Mears commented on PUP-6037 Re: File Permissions are set wrong in puppet Eric Thompson I am not quite sure what, if any, resolution was found for Patrick's issue, however, mine turned out to be a gap in my own understanding of Puppet's handling of folder permissions as I stated on 2016/06/03. Hope this helps. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6037) File Permissions are set wrong in puppet
Title: Message Title John Mears updated an issue Puppet / PUP-6037 File Permissions are set wrong in puppet Change By: John Mears Comment: Found the problem here...essentially we are misunderstanding Puppet's native behavior. Whenever Puppet sees a write permission bit set on a folder it will add the execute bit automatically due to it being required for writing to work. This is therefor a non-issue. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2855) PQL - Possibility to create fact arrays like from Puppetdbquery
Title: Message Title André Bauer commented on PDB-2855 Re: PQL - Possibility to create fact arrays like from Puppetdbquery The inventory approach looks promissing Is there a bugreport i can follow to watch progress? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
