Jira (FACT-747) Improve Solaris $::ipaddress accuracy
Title: Message Title Ryan Anderson commented on FACT-747 Re: Improve Solaris $::ipaddress accuracy While appreciated, heroic efforts are needed to get facter3.x dependencies to compile on Solaris, making this less useful than if the fix was given to the now-abandoned facter 2.x gem which I'm still using with puppet 5.x on Solaris. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3885) Make sure our async/threads and go-loops can't evaporate
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3885 Make sure our async/threads and go-loops can't evaporate Issue Type: Task Assignee: Unassigned Created: 2018/03/27 5:13 PM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (PUP-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Kris Bosland commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log As I have been gathering information, I have heard that the puppet agent is a long running process which regularly executes the puppet run. This will make it more challenging to match any reasonable time measurement to what you would see with a start-and-exit-process kind of run (some operations will be once per process work). Another issue is the variety of ways that Puppet can arrive at a catalog load-and-apply, which the report needs to be consistent across. At this point, I am planning to replace the incorrect "total" with what Melissa Stone is measuring above with Internal run time, which will be labeled "total". Release notes will be added explaining what that total means, and I will see if Garrett Guillotte would like to make any relevant doc changes. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-364) Misspelling in usage text
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-364 Misspelling in usage text Change By: Nick Lewis Fix Version/s: BOLT 0.17.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Charlie Sharpsteen commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log So it sounds like we want 'total' to represent as closely as possible what you would get with the wall clock, e.g. 0m30.481s in Melissa Stone's example? Yup! Although realistically, we won't capture the time for report submission at the end of the run — have to stop the clock in order to submit the time with the report Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7808) puppet resource <...> --to_yaml mishandles structured resource values
Title: Message Title
Edwin Wiles commented on PUP-7808
Re: puppet resource <...> --to_yaml mishandles structured resource values
The gist links are identical? What I'm getting from a custom resource is the following, which is a reasonable translation into a .pp format. dpw_wsendpointremoterewriterules { 'BAR:FOO_WEBSERVICE': {{ ensure => 'present',}} {{ domain => 'BAR',}} {{ rules => [}} {{ {}} {{ 'ServicePortMatchRegexp' => '^{https://foo/webservice/}barGet$',}} {{ 'RemoteEndpointProtocol' => 'https',}} {{ 'RemoteEndpointHostname' => 'mock',}} {{ 'RemoteEndpointPort' => 8443,}} {{ 'RemoteEndpointURI' => '/webservice/bar.asmx',}} {{ 'RemoteMQQM' => '',}} {{ 'RemoteTibcoEMS' => '',}} {{ 'RemoteWebSphereJMS' => ''}} {{ }, ...}} But when I specify --to_yaml, I'm getting this half/n/half translation. The rules, which are an array of hashes are not being translated correctly. dpw_wsendpointremoterewriterules: BAR:FOO_WEBSERVICE: ensure: 'present' domain: 'BAR' rules : [ { 'ServicePortMatchRegexp' => '^{https://foo/webservice/}barGet$', 'RemoteEndpointProtocol' => 'https', 'RemoteEndpointHostname' => 'mock', 'RemoteEndpointPort' => 8443, 'RemoteEndpointURI' => '/webservice/bar.asmx', 'RemoteMQQM' => '', 'RemoteTibcoEMS' => '', 'RemoteWebSphereJMS' => '' }, ... I would instead expect to see the following: dpw_wsendpointremoterewriterules: BAR:FOO_WEBSERVICE: ensure: 'present' domain: 'BAR' rules: - 'ServicePortMatchRegexp' => '^{https://foo/webservice/}barGet$', 'RemoteEndpointProtocol' => 'https', 'RemoteEndpointHostname' => 'mock', 'RemoteEndpointPort' => 8443, 'RemoteEndpointURI' => '/webservice/bar.asmx', 'RemoteMQQM' => '', 'RemoteTibcoEMS' => '', 'RemoteWebSphereJMS' => '' - ...
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-5830) Remove crazy symlink behavior
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-5830 Remove crazy symlink behavior Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2973) Get rid of freeze_main
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-2973 Get rid of freeze_main Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7601) Remove built-in LDAP Node Terminus
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-7601 Remove built-in LDAP Node Terminus Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1043) Remove ability to specify file checksum in `content` property
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-1043 Remove ability to specify file checksum in `content` property Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7078) Remove method Puppet.newtype (deprecated since 2011)
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-7078 Remove method Puppet.newtype (deprecated since 2011) Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7584) Remove deprecated execfail method from util/execution
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-7584 Remove deprecated execfail method from util/execution Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5830) Remove crazy symlink behavior
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-5830 Remove crazy symlink behavior Change By: Jacob Helwig Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8528) Remove WriteOnlyYaml node terminus
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8528 Remove WriteOnlyYaml node terminus Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8529) Remove data_binding_terminus setting
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8529 Remove data_binding_terminus setting Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8529) Remove data_binding_terminus setting
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8529 Remove data_binding_terminus setting Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8531) Remove app_management setting
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8531 Remove app_management setting Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8530) Remove trusted_server_facts setting
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8530 Remove trusted_server_facts setting Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8532) Remove pluginsync setting
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8532 Remove pluginsync setting Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8534) Remove configtimeout setting
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8534 Remove configtimeout setting Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8583) Fix JrJackson serialization of numbers so we can use it
Title: Message Title Maggie Dreyer commented on PUP-8583 Re: Fix JrJackson serialization of numbers so we can use it There was a typo in the original PR, this needs to go through CI again. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8533) Remove dead ignorecache setting
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8533 Remove dead ignorecache setting Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6507) Puppet help: Hide bad subcommands, and sort remainder by usefulness
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-6507 Puppet help: Hide bad subcommands, and sort remainder by usefulness Change By: Jacob Helwig Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1952) Run specs against jruby
Title: Message Title Eric Delaney updated an issue Puppet / PUP-1952 Run specs against jruby Change By: Eric Delaney Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7307) Tidy should support 'purge' or update file resource
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Eric Delaney Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6996) Puppet automatically creates the production environment with the incorrect permissions
Title: Message Title Eric Delaney updated an issue Puppet / PUP-6996 Puppet automatically creates the production environment with the incorrect permissions Change By: Eric Delaney Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8583) Fix JrJackson serialization of numbers so we can use it
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8583 Fix JrJackson serialization of numbers so we can use it Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title Daniel Parks commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity Awesome! Thanks! Really appreciate it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Kris Bosland commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log About the "missing" seconds: I was getting 5 seconds with a very simple setup, and Josh Cooper mentioned to me that Facter can be called during the 'require' part, so with multiple environments and custom facts I'm sure there could be a lot of time spent there. So it sounds like we want 'total' to represent as closely as possible what you would get with the wall clock, e.g. 0m30.481s in Melissa Stone's example? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Charlie Sharpsteen commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log And to clarify the acceptance criteria: Currently total is a simple sum of all the other times recorded to the report. This is misleading and unreliable as it double-counts and times that may have measured nested operations. For example, catalog_application, transaction_evaluation, and the per-resource type timings are all nested within each other, so the resources get counted against the total three times and the transaction_evaluation gets counted twice. The total time should represent the amount of time spent by the agent between waking up to start a run and submitting the report at the end of the run. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8441) Error datatype should support to_json
Title: Message Title
Alex Dreyer commented on PUP-8441
Re: Error datatype should support to_json
That was the issue with target. Is there a way in the datatype to cause the result object to be serialized as:
{ "__pcore_value__" : "Result", "__pcore_type__": [ "array of result objects" ] }
instead of:
{ "__pcore_value__" : "Result", "results": [ "array of result objects" ] }
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message
Jira (PUP-8610) PuppetStack.stacktrace is slow with a large stack
Title: Message Title Nick Lewis created an issue Puppet / PUP-8610 PuppetStack.stacktrace is slow with a large stack Issue Type: Bug Assignee: Unassigned Created: 2018/03/27 12:09 PM Priority: Normal Reporter: Nick Lewis Several places in Puppet call PuppetStack.stacktrace[0] to get their "caller". Most notably, log messages where the "source" is a Scope object without an associated resource use that method to determine the "source" to log from. There are also some Puppet functions that use it (empty, create_resource, and more). Those calls become quite slow (I saw up to 50ms) when the stack is large. While it's probably uncommon for the stack to grow that deep, no caller currently uses anything but the top element of the stack, which means this is a straightforward opportunity for improvement. It probably makes sense to either make that method lazy, which is a bit of a challenge as it's both a filter and a map, or to add a method that specifically returns the top element of the stack, which satisfies every current caller. Add Comment
Jira (BOLT-417) Suggest installing native dependencies as OS packages for gem install method
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-417 Suggest installing native dependencies as OS packages for gem install method Issue Type: Improvement Assignee: Unassigned Created: 2018/03/27 12:04 PM Priority: Normal Reporter: Nick Lewis Currently, gem installation of bolt requires a native build toolchain (gcc, make, ruby-devel) for a single native dependency (ffi). It's generally treated as a bad practice to install build tools on production machines. It also introduces additional dependencies and greater complication to the install process. The ffi gem is available as an operating system package on all the OSes where we support gem installation (Ubuntu 16.04, Debian 9, Fedora 25+). We should update the gem installation instructions to recommend installing those packages instead of the build toolchain. Specifically, the section to change is "Install Bolt on *nix": https://puppet.com/docs/bolt/0.x/bolt_installing.html#ariaid-title2 We should change dnf install -y make gcc redhat-rpm-config ruby-devel rubygem-rdoc to dnf install -y ruby rubygem-json rubygem-ffi rubygem-bigdecimal. Also change apt-get install -y make gcc ruby-dev to apt-get install -y ruby ruby-ffi. We should also change (in all occurrences) gem install bolt to gem install bolt --no-ri --no-rdoc. That cut install time from 30 seconds to 3 seconds, and users shouldn't have any need for ri/rdoc docs (anyone who does will know to remove those flags).
Jira (PUP-8396) Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called
Title: Message Title Adam Bottchen commented on PUP-8396 Re: Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called This looks to be the same issue as PUP-6531. The problem is that when /sbin/start is present on the system, the upstart provider will be used by the service resource rather than systemd. Since the upstart service is not running, calls to it by the provider then fail. On Ubuntu 16.04, systemd is the correct provider to use, but installing the upstart package (which is pulled along as a pre-req for ubuntu-desktop) will cause it to incorrectly switch to the upstart provider. One quick workaround is to move the upstart provider out of the way on the Ubuntu agent: # mv /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/upstart.rb /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/upstart.rb.old A quicker re-create for this issue is to start with a base 16.04 install and install the upstart package: # puppet resource service |wc -l 476 # apt-get install upstart Reading package lists... Done ... done Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ...
Jira (PUP-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Charlie Sharpsteen commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log Wow, looks like I misread Melissa Stone's results. It looks like we're missing 15 seconds, which is the difference between the "Internal run time" and the the 30.4 second wall time reported by Bash's time command. That's way too much to be Ruby requires, which should take a second or two at most. We'll always miss a chunk of the run time that occurs after the report is finalized and submitted to the master, but it seems like there is a significant operation occurring that we aren't capturing by instrumenting Puppet::Configurer#run_internal. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8609 Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Change By: Ethan Brown Fix Version/s: PUP 5.5.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Ethan Brown created an issue Puppet / PUP-8609 Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Issue Type: Task Affects Versions: PUP 5.5.0 Assignee: Unassigned Components: Windows Created: 2018/03/27 11:54 AM Fix Versions: PUP 5.5.z Labels: Windows Priority: Normal Reporter: Ethan Brown The pinning of FFI to 1.9.18 done in PUP-8438 is slightly problematic as it means that Puppet cannot be run on Ruby 2.5. This is also causing some issues coordinating FFI versions with PDK and the ubergems like https://rubygems.org/gems/puppet-module-win-default-r2.4 There was initially some concern over the new gems as described in https://github.com/puppetlabs/puppet/commit/d10b21f09107846d03fd8e2df6128f967207366c This ticket should validate the latest FFI, pick a minimum version, and bump the version in puppet-agent in addition to Puppet repo itself.
Jira (PUP-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Kris Bosland commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log I think the missing 5 seconds is in the puppet requires, and maybe .5 seconds or so of ruby itself starting up. It appears that the acceptance criteria of this ticket is to list the "total" time based on a certain calculation or measurement. Charlie Sharpsteen, are you the right person to clarify the AC here or can you tell me who to ask? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8606) Module-defined data types are very verbose when displayed
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8606 Module-defined data types are very verbose when displayed Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7407) Add deprecation warning to Puppet::Util.absolute_path?
Title: Message Title Eric Sorenson commented on PUP-7407 Re: Add deprecation warning to Puppet::Util.absolute_path? E - yes, only one version of each module which was latest as of the time i updated this corpus, maybe ~6 months ago Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-335) Boltlib functions should have configurable timeouts
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-335 Boltlib functions should have configurable timeouts Change By: David Kramer Sub-team: Bolt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-380) Support ed25519 out-of-the-box
Title: Message Title Michael Smith commented on BOLT-380 Re: Support ed25519 out-of-the-box Gene Liverman was there anything specifically challenging around following those instructions? We're wary to make them a required dependency of Bolt, but not sure other options would simplify it (such as a bolt-ed25519 gem that adds the dependencies). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-372) Associate jobs with plans when using the PCP transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Alex Dreyer Sprint: Bolt Discover/Design Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-380) Support ed25519 out-of-the-box
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-380
Support ed25519 out-of-the-box
Change By:
Michael Smith
net-ssh requires several extra libraries for ed25519 support. Without them, users see{code}2018-02-26T13:59:32.131096 WARN Net::SSH: ignoring unimplemented key:unsupported key type `ssh-ed25519'net-ssh requires the following gems for ed25519 support: * rbnacl (>= 3.2, < 5.0) * rbnacl-libsodium, if your system doesn't have libsodium installed. * bcrypt_pbkdf (>= 1.0, < 2.0)See https://github.com/net-ssh/net-ssh/issues/478 for more informationGem::MissingSpecError : "Could not find 'rbnacl' (< 5.0, >= 3.2.0) among 86 total gem(s){code}Add them support for ed25519 in packaging packages .
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you 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-91) multi-task plans swallow output from all but the last task
Title: Message Title David Kramer commented on BOLT-91 Re: multi-task plans swallow output from all but the last task This may not be needed after PUP-8608 is resolved. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-415) Bolt vagrant install
Title: Message Title Michael Smith commented on BOLT-415 Re: Bolt vagrant install We could also consider a self-contained Bolt install. It's not clear how we want to address setup difficulty on Windows and macOS otherwise. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-7407) Add deprecation warning to Puppet::Util.absolute_path?
Title: Message Title Ethan Brown commented on PUP-7407 Re: Add deprecation warning to Puppet::Util.absolute_path? Thanks for the search results - spot check shows the impact isn't too bad. Looks like you also filtered for "latest" versions of modules only? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8416) Remove old acceptance code that now lives in beaker-puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8416 Remove old acceptance code that now lives in beaker-puppet Change By: Kenn Hussey Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-416) integrate the Hands-On Lab into the existing documentation
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-416 integrate the Hands-On Lab into the existing documentation Change By: Kate Lopresti Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8608) Plans should return undef without an explicit return
Title: Message Title David Kramer assigned an issue to Unassigned Puppet / PUP-8608 Plans should return undef without an explicit return Change By: David Kramer Assignee: David Kramer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-416) integrate the Hands-On Lab into the existing documentation
Title: Message Title Kate Lopresti created an issue Puppet Task Runner / BOLT-416 integrate the Hands-On Lab into the existing documentation Issue Type: Improvement Assignee: Kate Lopresti Created: 2018/03/27 9:34 AM Priority: Normal Reporter: Kate Lopresti From the outcome of March 22 team meeting: 1. Docs to copy edit the lab exercises in the repo. 2. Docs to create a new Getting Started page in Bolt docs and link to lab. 3. Docs and Eng to implement strings, code we can pull from the repo into the docs. (Modules team has a process .) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-410) run_* functions should accept a description
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-410 run_* functions should accept a description Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8396) Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-8396 Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called Change By: Adam Bottchen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8608) Plans should return undef without an explicit return
Title: Message Title David Kramer moved an issue Puppet / PUP-8608 Plans should return undef without an explicit return Change By: David Kramer Key: BOLT PUP - 396 8608 Project: Puppet Task Runner Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8608) Plans should return undef without an explicit return
Title: Message Title David Kramer updated an issue Puppet / PUP-8608 Plans should return undef without an explicit return Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-396) Plans should return undef without an explicit return
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-396 Plans should return undef without an explicit return Change By: David Kramer Team: Direct Change Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-396) Plans should return undef without an explicit return
Title: Message Title David Kramer assigned an issue to David Kramer Puppet Task Runner / BOLT-396 Plans should return undef without an explicit return Change By: David Kramer Assignee: David Kramer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-396) Plans should return undef without an explicit return
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-396 Plans should return undef without an explicit return Change By: David Kramer Sub-team: Bolt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-394) SPIKE: Propose changes to puppet task spec to include multiple task implementations
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-394 SPIKE: Propose changes to puppet task spec to include multiple task implementations Change By: David Kramer Summary: Update SPIKE: Propose changes to puppet task spec to include multiple task implementations Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-412) Explore running puppet device operations from a Bolt plan
Title: Message Title Alex Dreyer commented on BOLT-412 Re: Explore running puppet device operations from a Bolt plan There are tasks for puppet-device https://forge.puppet.com/tkishel/puppet_device/tasks plans should probably target the same module. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-365) Missing period in "E.g." in usage text
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-365 Missing period in "E.g." in usage text Change By: Michael Smith Release Notes Summary: Minor update to help text. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8588) Support multiple implementations when loading tasks
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-8588 Support multiple implementations when loading tasks Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-135) I want to execute different versions of the task file on different platforms
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-135 I want to execute different versions of the task file on different platforms Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-365) Missing period in "E.g." in usage text
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-365 Missing period in "E.g." in usage text Change By: Michael Smith Fix Version/s: BOLT NEXT Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-399) Update fact gathering task to leverage cross-platform support
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-399 Update fact gathering task to leverage cross-platform support Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-407) Using TargetSpec in plan parameters breaks `bolt plan show`
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-407 Using TargetSpec in plan parameters breaks `bolt plan show` Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-407) Using TargetSpec in plan parameters breaks `bolt plan show`
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-407 Using TargetSpec in plan parameters breaks `bolt plan show` Change By: Michael Smith Fix Version/s: BOLT NEXT Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-407) Using TargetSpec in plan parameters breaks `bolt plan show`
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-407 Using TargetSpec in plan parameters breaks `bolt plan show` Change By: Michael Smith Release Notes Summary: An issue where 'bolt plan show ' would fail on a plan that uses TargetSpec has been fixed. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title R.I.Pienaar commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf And if someone goes to the trouble of setting up lets say splunk logging or whatever, and make Puppet log there, it's a safe assumption thats where they want to look for problems with puppet. Fall back default that is not where they look for critical errors is grossly irresponsible. I don't care either way, I am just pointing out why things are as they are for some context Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8477) selinux types are being set on every run
Title: Message Title
Tim Skirvin commented on PUP-8477
Re: selinux types are being set on every run
Hmm. This didn't solve all of my problems, I'm still seeing on my host testing 5.5.0:
k5login { '/root/.k5login': principals => unique(sort($princs)), mode => '600' }
-> file { '/root/.k5login': seltype => 'krb5_home_t' }
Notice: /Stage[main]/P_krb5::K5login::Root/K5login[root .k5login]/seluser: seluser changed 'system_u' to 'user_u' Notice: /Stage[main]/P_krb5::K5login::Root/File[/root/.k5login]/seluser: seluser changed 'user_u' to 'system_u' {/code} Note that I'm not setting `user_u` or `system_u` anywhere in my code base; selinux is disabled on the host; and
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-2997) Logdest cannot be set in the puppet.conf
Title: Message Title R.I.Pienaar commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf But it doesn't in so many cases puppet apply, puppet agent --test, etcetc. There's no right thing that handles all cases other than let people tell it what to do always. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-415) Bolt vagrant install
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-415 Bolt vagrant install Issue Type: New Feature Assignee: Unassigned Created: 2018/03/27 8:34 AM Priority: Normal Reporter: Alex Dreyer Some users are having trouble installing bolt next to older puppet agents. We should provide a vagrantfile that will spin up a vm with bolt installed. Users should be able to ssh into the vm with agent forwarding and experiment with bolt from there Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Robert J commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf Then you default log it to the system syslog like it does now... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title R.I.Pienaar commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf The chicken and egg here is that, where do you log when you can't find the config file to tell you where to log? or cant read it? etc Logging it to a default fallback STDERR would be wrong - because then if someone monitors splunk they dont know about it. Specifying it on the CLI only ensures that in all cases the right thing can be done (or at least tried). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-2997 Logdest cannot be set in the puppet.conf Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: Users sometimes want to send their logs to a different location and have this work for ALL invocations of puppet(daemon or CLI). Example cases mentioned in this ticket are to send everything to splunk, or to make the puppet logs available to less privileged users. The wrapper script that was added in Puppet 5 could be modified to source a logdest from some other file such as puppet.conf or if that isn't workable something like environment settings such as sysconfig CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-6936) unable to read last_run_summary.yaml from user
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-6936 unable to read last_run_summary.yaml from user Change By: Nicky Kernohan Method Found: Customer Feedback Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3862) replace facts failing for some nodes
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Kenn Hussey Team: Data Platform Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3862) replace facts failing for some nodes
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Kenn Hussey Fix Version/s: PDB 5.2.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-233) Generated markdown does not always render correctly
Title: Message Title John Lyman created an issue Puppet Strings / PDOC-233 Generated markdown does not always render correctly Issue Type: Improvement Assignee: Unassigned Attachments: output.md.png Created: 2018/03/27 5:29 AM Priority: Normal Reporter: John Lyman Some markdown parsers do not convert atx-style headers correctly unless they are surrounded by blank lines. (See below for example.) The erb templates should be updated so that all headers are surrounded by blank lines to increase the chance of them rendering correctly with different parsers. I have already updated the templates and will submit a PR once my company signs the CLA. Is this something you would consider for a trivial patch exemption since it is just changes to white space formatting? Example rendering of output.md spec fixture on GitLab: Add Comment
Jira (PUP-8396) Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-8396 Puppet Resource Service fails on Debain/Ubuntu when non systemd service is called Change By: Nicky Kernohan Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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.
