Jira (PUP-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Chuck Schweizer commented on PUP-8470 Re: Unable to modify local user group membership with forcelocal Is there a reason you don’t want to use usermod for this? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus commented on PUP-8489
Re: inifile no longer manages existing lines in puppet post 5.4.0
These are the modules where it seems to work with: {{accounts apache archive chocolatey concat dotnet epel gitlab graphite_powershell hiera iis inifile java_ks logstash memcached ntp pe_metric_curl_cron_jobs powershell reboot registry sensu stdlib vcsrepo windows_env windowsfeature wsus_client acl apt aws chocolatey_server docker elasticsearch firewall grafana haproxy hocon influxdb java jenkins logstashforwarder nginx openldap postgresql puppetserver_gem redis rsyslog staging tomcat windows_autoupdate windows_eventlog windows_firewall yum}}
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title Past Haus commented on PUP-8489 Re: inifile no longer manages existing lines in puppet post 5.4.0 A bisect showed this commit as the culprit: https://github.com/puppetlabs/puppet/commit/c98bb6787fa2ec04842a92924dd4eb8e41bddd78 Also I can't explain why having multiple modules in codedir made the problem go away but having only the one module in codedir doesn't work. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8489
inifile no longer manages existing lines in puppet post 5.4.0
Change By:
Past Haus
.comm *Puppet Version: f77e9e00efcf9bd8dac66c6622f35cbe16c8eb7a (5.5.0)* *Puppet Server Version: (5.2.0)* *OS Name/Version: Rhel 7*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Even when using a codedir with only the inifile module installed, it should work.In this example, {{/tmp/configure_inifile.aPkO3n}} is a tmpdir with just the inifile module installed.An inifile resource such as the following should modify the existing java_args line: {code}[root@b3wa4ws5mg41efr ~]# puppet apply --codedir /tmp/configure_inifile.aPkO3n -e 'ini_setting { "JAVA_ARGS": ensure => present, path => "/etc/sysconfig/puppetserver", section => "", setting => "JAVA_ARGS", key_val_separator => "=", value => "\"-Xmx2g -Xms2g -XX:+PrintTenuringDistribution -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/var/log/puppetlabs/puppetserver/gc.log\"",}'{code}In this case the value of JAVA_ARGS in the file is {{JAVA_ARGS="-Xms2g -Xmx2g -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"}}*Actual Behavior:*It does not. inifile seems to be able to remove lines and add lines that don't already exist, but modifying existing lines does not work. Unfortunately even with --trace, --verbose and --debug there isn't anything useful coming out of the module. Note: this seems to only be the case when inifile is installed in its own codedir and {{puppet apply --codedir $codedir}} is used. When inifile is present in {{/etc/puppetlabs/code/environments/production/modules/inifile}} with other modules the resource behaves as expected.
Add Comment
Jira (PUP-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus commented on PUP-8489
Re: inifile no longer manages existing lines in puppet post 5.4.0
Minimal reproducer:
Make a tmpdir ($tmpdir)
Install inifile module to $tmpdir puppet module install puppetlabs-inifile --codedir $tmpdir
Make a file with SETTING="foo" in it (call it temp-file)
Make the following puppet manifest (call it test-resource.pp):
ini_setting { "JAVA_ARGS":
ensure=> present,
path => "/path/to/temp-file",
section => "",
setting=> "SETTING",
key_val_separator => "=",
value=> "BAR",
}
Run the following puppet code puppet apply --codedir $tmpdir test-resource.pp
Watch nothing happen when it should (then try it with 5.4.0 and watch it work)
Jira (BOLT-338) Local transport for bolt
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-338 Local transport for bolt Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8489
inifile no longer manages existing lines in puppet post 5.4.0
Change By:
Past Haus
*Puppet Version: f77e9e00efcf9bd8dac66c6622f35cbe16c8eb7a (5.5.0)* *Puppet Server Version: (5.2.0)* *OS Name/Version: Rhel 7*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Even when using a codedir with only the inifile module installed, it should work.In this example, {{/tmp/configure_inifile.aPkO3n}} is a tmpdir with just the inifile module installed.An inifile resource such as the following should modify the existing java_args line: {code}[root@b3wa4ws5mg41efr ~]# puppet apply --codedir /tmp/configure_inifile.aPkO3n -e 'ini_setting \ { "JAVA_ARGS": ensure => present, path => "/etc/sysconfig/puppetserver", section => "", setting => "JAVA_ARGS", key_val_separator => "=", value => "\"-Xmx2g -Xms2g -XX:+PrintTenuringDistribution -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/var/log/puppetlabs/puppetserver/gc.log\"",}'{code}In this case the value of JAVA_ARGS in the file is {{JAVA_ARGS="-Xms2g -Xmx2g -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"}}*Actual Behavior:*It does not. inifile seems to be able to remove lines and add lines that don't already exist, but modifying existing lines does not work. Unfortunately even with --trace, --verbose and --debug there isn't anything useful coming out of the module. Note: this seems to only be the case when inifile is installed in its own codedir and {{puppet apply --codedir $codedir}} is used. When inifile is present in {{/etc/puppetlabs/code/environments/production/modules/inifile}} with other modules the resource behaves as expected.
Add Comment
Jira (PUP-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8489
inifile no longer manages existing lines in puppet post 5.4.0
Change By:
Past Haus
*Puppet Version: f77e9e00efcf9bd8dac66c6622f35cbe16c8eb7a (5.5.0)* *Puppet Server Version: (5.2.0)* *OS Name/Version: Rhel 7*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:*Even when using a codedir with only the inifile module installed, it should work.In this example, {{/tmp/configure_inifile.aPkO3n}} is a tmpdir with just the inifile module installed.An inifile resource such as the following should modify the existing java_args line: {code}[root@b3wa4ws5mg41efr ~]# puppet apply --codedir /tmp/configure_inifile.aPkO3n -e 'ini_setting \{ "JAVA_ARGS": ensure => present, path => "/etc/sysconfig/puppetserver", section => "", setting => "JAVA_ARGS", key_val_separator => "=", value => "\"-Xmx2g -Xms2g -XX:+PrintTenuringDistribution -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:/var/log/puppetlabs/puppetserver/gc.log\"",}'{code}In this case the value of JAVA_ARGS in the file is {{JAVA_ARGS="-Xms2g -Xmx2g -Djruby.logger.class=com.puppetlabs.jruby_utils.jruby.Slf4jLogger"}}*Actual Behavior:*It does not. inifile seems to be able to remove lines and add lines that don't already exist, but modifying existing lines does not work. Unfortunately even with --trace, --verbose and --debug there isn't anything useful coming out of the module. Note: this seems to only be the case when inifile is installed in its own codedir and {{puppet apply --codedir $codedir}} is used. When inifile is present in {{/etc/puppetlabs/code/environments/production/modules/inifile}} with other modules the resource behaves as expected.
Add Comment
Jira (PUP-8489) inifile no longer manages existing lines in puppet post 5.4.0
Title: Message Title
Past Haus created an issue
Puppet / PUP-8489
inifile no longer manages existing lines in puppet post 5.4.0
Issue Type:
Bug
Affects Versions:
PUP 5.5.0
Assignee:
Unassigned
Created:
2018/02/23 3:15 PM
Priority:
Normal
Reporter:
Past Haus
Puppet Version: f77e9e00efcf9bd8dac66c6622f35cbe16c8eb7a (5.5.0) Puppet Server Version: (5.2.0) OS Name/Version: Rhel 7 Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Even when using a codedir with only the inifile module installed, it should work. In this example, /tmp/configure_inifile.aPkO3n is a tmpdir with just the inifile module installed. An inifile resource such as the following should modify the existing java_args line:
[root@b3wa4ws5mg41efr ~]# puppet apply --codedir /tmp/configure_inifile.aPkO3n -e 'ini_setting \{ "JAVA_ARGS":
ensure => present,
path => "/etc/sysconfig/puppetserver",
section => "",
Jira (BOLT-338) Local transport for bolt
Title: Message Title Alex Dreyer commented on BOLT-338 Re: Local transport for bolt I don't think it's important for either of our key use cases so lets not. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-338) Local transport for bolt
Title: Message Title Michael Smith commented on BOLT-338 Re: Local transport for bolt Do we want to support sudo? I think not initially, but may want it as a next step. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith commented on BOLT-345 Re: Bolt should provide a better summary of failures Do we care about adding this to JSON output? It can be computed by filtering the specific results, but so can node_count. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-337 Nodes in inventory groups should accept "host:port" syntax Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-346) Orchestrator batching only handles task environment
Title: Message Title Kate Lopresti commented on BOLT-346 Re: Orchestrator batching only handles task environment Added ticket to the release notes: Improvements to orchestrator configuration file settings You can now specify orchestrator config in inventory files and set up different targets to use different orchestrators. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-346) Orchestrator batching only handles task environment
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-346 Orchestrator batching only handles task environment Change By: Kate Lopresti Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8230) Puppet Platform Release Process Improvements
Title: Message Title Molly Waggett assigned an issue to Molly Waggett Puppet / PUP-8230 Puppet Platform Release Process Improvements Change By: Molly Waggett Assignee: Molly Waggett Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Trey Dockendorf commented on PUP-8470 Re: Unable to modify local user group membership with forcelocal I can't tell if the membership parameter, https://puppet.com/docs/puppet/5.3/type.html#user-attribute-membership, applies to useradd provider. It doesn't look like that parameter applies but wanted to double check. If membership param is not used by useradd then sounds like the change needed would be to run "lgroupmod --member-add= " for each group in a user's groups property. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-346) Orchestrator batching only handles task environment
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-346 Orchestrator batching only handles task environment Change By: Alex Dreyer Release Notes Summary: This allows orchestrator config to be specified in the inventory files and different targets to use different orchestrators Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-331) Script to generate inventory from puppetdb queries
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-331 Script to generate inventory from puppetdb queries Change By: Alex Dreyer Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-346) Orchestrator batching only handles task environment
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-346 Orchestrator batching only handles task environment Change By: Alex Dreyer Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8041) Replace FACTER_url with --resource for puppet device
Title: Message Title Josh Cooper commented on PUP-8041 Re: Replace FACTER_url with --resource for puppet device Merged to 5.3.x in https://github.com/puppetlabs/puppet/commit/0e90cbf8cfe95278ea9701bf9f26f65b2f0c8302 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8488) Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate
Title: Message Title Eric Delaney created an issue Puppet / PUP-8488 Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate Issue Type: Task Assignee: Eric Delaney Created: 2018/02/23 11:45 AM Priority: Normal Reporter: Eric Delaney Convert usage of Puppet.features.microsoft_windows? to Puppet::Util::Platform.windows? where appropriate. We need to be careful when reviewing the usages, its ok to mock the usage of Puppet.features.microsoft_windows? however we should NOT be mocking out the Puppet::Util::Platform.windows?, so care must be taken to ensure the things we convert make sense and that we continue to have the proper testing coverage. Add Comment
Jira (BOLT-350) Add documentation for installing bolt as a system package
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-350 Add documentation for installing bolt as a system package Issue Type: Improvement Assignee: Unassigned Created: 2018/02/23 11:44 AM Fix Versions: Bolt Next Priority: Normal Reporter: Lucy Wyman We should document installing bolt as a package instead of a gem. Questions: Where should these docs go? Should this be explicitly preferred to gem install? Add Comment
Jira (BOLT-349) Update release automation to tag bolt-vanagon and publish packages
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-349 Update release automation to tag bolt-vanagon and publish packages Issue Type: Improvement Assignee: Unassigned Created: 2018/02/23 11:43 AM Fix Versions: Bolt Next Priority: Normal Reporter: Lucy Wyman Bolt-vanagon currently requires manual version tagging + release to begin building system packages. Depending on the expected release cadence, we'd like to automate tagging + building packages when we release Bolt gem. Depending on when we decide to release packages, this may or may not be automatable. Add Comment
Jira (PUP-8041) Replace FACTER_url with --resource for puppet device
Title: Message Title Rick Sherman updated an issue Puppet / PUP-8041 Replace FACTER_url with --resource for puppet device This update brings the query functionality of `puppet resource` into `puppet device`. Users can use the feature with the flag --resource type [optional title] Requires the use of --target to specify which node to query. Users can also use the optional --to_yaml to get data in Hiera format. Unlike `puppet resource` users are unable to modify the state of resources. Change By: Rick Sherman Release Notes Summary: Adds the ability to retrieve current system state as Puppet code from devices using `puppet device`. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-348) Add automated tests of system packages
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-348 Add automated tests of system packages Issue Type: Improvement Assignee: Unassigned Created: 2018/02/23 11:39 AM Fix Versions: Bolt Next Priority: Normal Reporter: Lucy Wyman We should ideally have some basic testing of built system packages that gets run before releasing them. This could potentially be part of the Orchestrator tests. Tests should cover: Running bolt command/task/script/file upload Running bolt plan Running bolt [task|plan] show Add Comment
Jira (PUP-8487) Eliminate use of MethodHelper
Title: Message Title Patrick Carlisle created an issue Puppet / PUP-8487 Eliminate use of MethodHelper Issue Type: Improvement Assignee: Unassigned Created: 2018/02/23 11:37 AM Priority: Normal Reporter: Patrick Carlisle This serves no purpose but to obfuscate code and I've measured it as a significant source of garbage. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-332) Target objects should store state of the Targets
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-332 Target objects should store state of the Targets Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8470) Unable to modify local user group membership with forcelocal
Title: Message Title Melissa Stone commented on PUP-8470 Re: Unable to modify local user group membership with forcelocal Trey Dockendorf it sounds like your proposal is the best to get this moving forward. That satisfies the requirements that Eric set out, and should fix this failure for Chuck. If you're still up for opening that pull request, that would be fantastic! Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8412) In the puppet report, provide details of which provider was used for each resource
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8412 In the puppet report, provide details of which provider was used for each resource Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Release Notes Summary: This version adds the new provider_used field to the report schema for serialization and deserialization. The provider_used field is populated with the provider used to provide the resource. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-8464) puppet help should process its arguments better
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8464 puppet help should process its arguments better Change By: Eric Delaney Release Notes Summary: The 'puppet help' command now prints helpful error messages. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8444 Have "puppet man" default to "--help" when run without arguments Change By: Eric Delaney Release Notes Summary: The 'puppet man' command processes its command line arguments and now prints better useful error messages. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8464) puppet help should process its arguments better
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8464 puppet help should process its arguments better Change By: Eric Delaney Release Notes Summary: The 'puppet help' command prints helpful error messages. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8464) puppet help should process its arguments better
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8464 puppet help should process its arguments better Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8444 Have "puppet man" default to "--help" when run without arguments Change By: Eric Delaney Release Notes Summary: The 'puppet man' command processes its command line arguments and prints better useful error messages. Release Notes: Not Needed Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8444 Have "puppet man" default to "--help" when run without arguments Change By: Eric Delaney Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8445) Deprecate "puppet man"
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8445 Deprecate "puppet man" Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Release Notes Summary: The 'puppet man' command is deprecated and will be removed in a future release. Please use 'puppet help ' or the installed manpages 'man puppet-' Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3855) Bring back PDP manifest / deletion processing
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3855 Bring back PDP manifest / deletion processing Issue Type: Improvement Assignee: Unassigned Created: 2018/02/23 10:39 AM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-3855) Bring back PDP manifest / deletion processing
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3855 Bring back PDP manifest / deletion processing Change By: Russell Mull Sprint: Data Platform 2018-02-28 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8361) Create a CI job to generate manpages
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-8361 Create a CI job to generate manpages Change By: Jorie Tappa Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-337 Nodes in inventory groups should accept "host:port" syntax Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-263) log bolt results to a log file
Title: Message Title Michael Smith assigned an issue to Nick Lewis Puppet Task Runner / BOLT-263 log bolt results to a log file Change By: Michael Smith Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-315) Bolt Packages
Title: Message Title Michael Smith assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-315 Bolt Packages Change By: Michael Smith Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-345
Bolt should provide a better summary of failures
Change By:
Alex Dreyer
When {{bolt file/task/script/command run}} fails on some nodes the summary like in human output should display a comma separated list of what nodes failed that can be copied as a --nodes argument.When there are failures, augment current summary with{code}Successful on 5 nodes: foo-vm211,foo-vm291,foo-vm292,foo-vm294,foo-vm295Failed on 5 nodes: foo-vm190,foo-vm191,foo-vm192,foo-vm194,foo-vm195Ran on 216 nodes in 13.60 seconds{code}Handle singular if only 1 node fails. Use (red) error highlighting for "Failed on ...". Do not show failure or success line unless there is are nodes to display. List successful nodes first, followed by failed nodes followed by current summary so that important information is less likely to be obscured with very large runs If there are no failures, retain the current output.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-345
Bolt should provide a better summary of failures
Change By:
Alex Dreyer
When {{bolt file/task/script/command run}} fails on some nodes the summary like in human output should display a comma separated list of what nodes failed that can be copied as a --nodes argument.When there are failures, augment current summary with{code} Ran Successful on 216 5 nodes in 13.60 seconds : foo-vm211,foo-vm291,foo-vm292,foo-vm294,foo-vm295 Failed on 5 nodes: foo-vm190,foo-vm191,foo-vm192,foo-vm194,foo-vm195 Ran on 216 nodes in 13.60 seconds {code}Handle singular if only 1 node fails. Use (red) error highlighting for "Failed on ...".If there are no failures, retain the current output.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (BOLT-338) Local transport for bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-338 Local transport for bolt Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-338) Local transport for bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-338 Local transport for bolt Change By: Alex Dreyer Executing tasks locally is a powerful method of extending the plan language without writing ruby. Currently bolt has to connect over a normal transport to execute local tasks. Instead bolt should have a special local transport that can be used.Users can target the local transport with the bare string "localhost"Users can target localhost with the protocol 'local'. The rest of the uri will be ignored.Implementation:Windows and linux code should be kept in separate classes with the executor deciding which version to load/use.The Inventory should be responsible for handling the host named 'localhost' and returning a host with the local transport. The task should be copied to a tempdir before execution and that tmpdir should be cleaned up. If 'localhost' is defined with a different transport in inventory that should override 'localhost' matching. Questions Out of scope : Should the Windows implementation. local transport copy task files before execution to make it more useful for iteration during task development? Eventually we may want both options what should we default to or implement first?Should linux support unix environments and shell implementations be separate tickets? error cleaned if it's used on windows Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-337 Nodes in inventory groups should accept "host:port" syntax Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8188) --render-as broken in puppet config print
Title: Message Title Jennifer Solman commented on PUP-8188 Re: --render-as broken in puppet config print Jorie Tappa, release notes added. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8188) --render-as broken in puppet config print
Title: Message Title Jennifer Solman updated an issue Puppet / PUP-8188 --render-as broken in puppet config print Change By: Jennifer Solman Release Notes Summary: --render-as option is now working for puppet config print. Supported options are json and yaml. The default format is unchanged. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-331) Script to generate inventory from puppetdb queries
Title: Message Title David Kramer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-331 Script to generate inventory from puppetdb queries Change By: David Kramer Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8448) "puppet cert clean" only works if at least one cert has already been signed
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8448 "puppet cert clean" only works if at least one cert has already been signed Change By: Jacob Helwig Release Notes Summary: 'puppet cert clean' can now clean certificates even if none of the certificates in the list of certificates it is told to clean have already been signed. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8464) puppet help should process its arguments better
Title: Message Title Jorie Tappa commented on PUP-8464 Re: puppet help should process its arguments better Eric Delaney please add release notes if necessary Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8443 Topscope 'environment' can become nil when setting node parameters in a custom terminus Change By: Jacob Helwig Release Notes Summary: In a custom Node terminus, it was possible to construct the Node object in a way where $::environment would be empty during catalog compilation, even though the Node object had the environment itself properly set. Catalog compilation now consults the node's environment directly when setting $::environment. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8463) Remove existing warnings and run PRs through 'ruby -wc'
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-8463 Remove existing warnings and run PRs through 'ruby -wc' Change By: Jorie Tappa Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8448) "puppet cert clean" only works if at least one cert has already been signed
Title: Message Title Jorie Tappa commented on PUP-8448 Re: "puppet cert clean" only works if at least one cert has already been signed Jacob Helwig please add release notes here too Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8445) Deprecate "puppet man"
Title: Message Title Jorie Tappa commented on PUP-8445 Re: Deprecate "puppet man" Eric Delaney please add release notes for this ticket Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Jorie Tappa commented on PUP-8444 Re: Have "puppet man" default to "--help" when run without arguments Eric Delaney please add release notes if necessary Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8443) Topscope 'environment' can become nil when setting node parameters in a custom terminus
Title: Message Title Jorie Tappa commented on PUP-8443 Re: Topscope 'environment' can become nil when setting node parameters in a custom terminus Jacob Helwig Please add release notes if applicable Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8188) --render-as broken in puppet config print
Title: Message Title Jorie Tappa commented on PUP-8188 Re: --render-as broken in puppet config print Jennifer Solman please add release notes for this ticket. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8412) In the puppet report, provide details of which provider was used for each resource
Title: Message Title Jorie Tappa commented on PUP-8412 Re: In the puppet report, provide details of which provider was used for each resource Eric Delaney please add release notes for this ticket Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Marc Schöchlin commented on BOLT-345 Re: Bolt should provide a better summary of failures A list of successful nodes would also be useful in the case where bolt is used for finding out things. Example: $ bolt command run "sysctl vm.swappiness|grep '= 0'" --nodes `query_puppetdb infrastructure_master` Ran on 216 nodes in 13.60 seconds Failed on 5 nodes: foo-vm190,foo-vm191,foo-vm192,foo-vm194,foo-vm195 Successful on 5 nodes: foo-vm211,foo-vm291,foo-vm292,foo-vm294,foo-vm295 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
