Jira (FACT-1774) Enable testing PA built against system openssl in CI test pipelines on RHEL platform
Title: Message Title Jayant Sane created an issue Facter / FACT-1774 Enable testing PA built against system openssl in CI test pipelines on RHEL platform Issue Type: Task Assignee: Jayant Sane Created: 2017/10/02 9:11 PM Priority: Normal Reporter: Jayant Sane There are some failures when testing PA, built against openssl, in CI pipe lines on RHEL targets. The issue is due to the rhel images having older patch version of openssl package. The install scripts in various project specific acceptance setup needs to be changed to upgrade the openssl lib versions. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8009) Performance regression with lots of modules and gettext
Title: Message Title Casey Williams commented on PUP-8009 Re: Performance regression with lots of modules and gettext Had some puppet i18n test failures in the 5.3.2_release branch tonight after disabling gettext here, all like this: 19:26:10 Errored Tests Cases: 19:26:10 Test Case tests/i18n/check_puppet_run_message.rb reported: #> 19:26:10 Test line: tests/i18n/check_puppet_run_message.rb:8:in `block (2 levels) in run_test' Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs.
Jira (PUP-7842) language for SLES 11.3 service not being set correctly during boot
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7842 language for SLES 11.3 service not being set correctly during boot Change By: Geoff Nichols Sprint: Platform OS Hold Ready for Eng. , Platform OS 2017-09-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7886) Resolve several AAA and TACACS failures in Cisco pipeline
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7886 Resolve several AAA and TACACS failures in Cisco pipeline Change By: Geoff Nichols Sprint: Platform OS Hold Ready for Eng. , Platform OS 2017-09-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3263) Architecture Parameter for Package Resource
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-3263 Architecture Parameter for Package Resource Change By: Geoff Nichols Sprint: Platform OS Hold Ready for Eng. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8017) Bump puppet version to 5.3.2
Title: Message Title Geoff Nichols created an issue Puppet / PUP-8017 Bump puppet version to 5.3.2 Issue Type: Task Assignee: Casey Williams Created: 2017/10/02 7:10 PM Fix Versions: PUP 5.3.2 Priority: Normal Reporter: Geoff Nichols 1) Check that the version number in source for puppet is correct version for puppet should be 5.3.2 check lib/puppet/version.rb for the PUPPETVERSION variable check .gemspec for version variable Add Comment
Jira (PDOC-178) @api private not showing up in generated docs
Title: Message Title Henrik Lindberg commented on PDOC-178 Re: @api private not showing up in generated docs This is by design. It may be possible to modify the yard settings to also get output of private API. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7998) Add an Error data type to puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7998
Add an Error data type to puppet
Change By:
Henrik Lindberg
It is of value to describe a value as being an {{Error\[kind, issue_code]}} - a kind of exceptional result that can be returned from functions and passed around.An error type is parameterised with a "kind" discriminator - a missing parameter means "all kinds". A "kind" is a string that should follow certain conventions, but is not required to. It is typically a string on the form {{authority/name}} where authority is something like "puppetlabs" or "puppet", or the loose notion of "author" (the authority that controls what is valid as a kind-name). The type parameter can be given as {{Variant\[String, Regexp, Type\[Enum], Type\[Pattern], Type\[Any] ]}}, where a given {{String}} is the same as an Enum with that single value, and {{Regexp }}is the same as {{Pattern}} with that single regexp). An {{Error\[Any]}} is the same as {{Error}}.The issue code type parameter is of the same type as kind, but here it is expected that than an issue code (without structure) is used.As an example, the type {{Error\[Any, "SYNTAX_ERROR"]}} would match all error objects from any authority using an issue code of "SYNTAX_ERROR". An {{Error\[/^puppet/]}} would match all errors with "puppet..." as the authority.An error instance is described by:{code:puppet}type Error = Object[ attributes => {message => String,kind => { type => Optional[String], default_value => undef},issue_code => { type => String, default_value => "ERROR" }, partial_result => { type => Optional[Any], default_value => undef }details => { type => Optional[DataHash], default_value = undef } }}{code}Type algebra: An Error {{Error\[K, I] op Error\[K2, I2]}} is true if {{K op K2}} and {{I op I2}} are both true. Error < Object.The "detail" hash is an encoding of additional information such as "exitcode", "stacktrace", "exception", etc. These are included for the purpose of being able to give a user more debugging information. The exact content and details of "details" is left open ended to be flexible for different kinds of error information.
Add Comment
Jira (PUP-7998) Add an Error data type to puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7998
Add an Error data type to puppet
Change By:
Henrik Lindberg
It is of value to describe a value as being an {{Error\[kind, issue_code]}} - a kind of exceptional result that can be returned from functions and passed around.An error type is parameterised with a "kind" discriminator - a missing parameter means "all kinds". A "kind" is a string that should follow certain conventions, but is not required to. It is typically a string on the form {{authority/name}} where authority is something like "puppetlabs" or "puppet", or the loose notion of "author" (the authority that controls what is valid as a kind-name). The type parameter can be given as {{Variant\[String, Regexp, Type\[Enum], Type\[Pattern], Type\[Any] ]}}, where a given {{String}} is the same as an Enum with that single value, and {{Regexp }}is the same as {{Pattern}} with that single regexp). An {{Error\[Any]}} is the same as {{Error}}.The issue code type parameter is of the same type as kind, but here it is expected that than an issue code (without structure) is used.As an example, the type {{Error\[Any, "SYNTAX_ERROR"]}} would match all error objects from any authority using an issue code of "SYNTAX_ERROR". An {{Error\[/^puppet/]}} would match all errors with "puppet..." as the authority.An error instance is described by:{code:puppet}type Error = Object[ attributes => {message => String,kind => { type => Optional[String], default_value => undef},issue_code => { type => String, default_value => "ERROR" }, partial_result => { type => Optional[Any], default_value => undef } details => { type => Optional[DataHash], default_value = undef } }}{code}Type algebra: An Error {{Error\[K, I] op Error\[K2, I2]}} is true if {{K op K2}} and {{I op I2}} are both true. Error < Object.The "detail" hash is an encoding of additional information such as "exitcode", "stacktrace", "exception", etc. These are included for the purpose of being able to give a user more debugging information. The exact content and details of "details" is left open ended to be flexible for different kinds of error information.
Add Comment
Jira (PUP-7998) Add an Error data type to puppet
Title: Message Title Henrik Lindberg commented on PUP-7998 Re: Add an Error data type to puppet In addition to what has already been specified, an error instance should also have an partial_result attribute that is of type Any. While not ideal it is expected that some things when executed can produce partial output and return both an error and the partial result (as far as it got). For that purpose, the error object needs to be able to carry that extra information. It is undef if not specified. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-585) Test PA built against system openssl in CI test pipelines
Title: Message Title Jayant Sane created an issue Hiera / HI-585 Test PA built against system openssl in CI test pipelines Issue Type: Task Assignee: Jayant Sane Created: 2017/10/02 4:38 PM Priority: Normal Reporter: Jayant Sane There are some failures when testing PA, built against openssl, in CI pipe lines on RHEL targets. The issue is due to the rhel images having older patch version of openssl package. The install scripts in various project specific acceptance setup needs to be changed to upgrade the openssl lib versions. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8016) Updated module translations will not be loaded without restarting puppet
Title: Message Title Michael Smith commented on PUP-8016 Re: Updated module translations will not be loaded without restarting puppet This should work with environment caching. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8016) Updated module translations will not be loaded without restarting puppet
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8016 Updated module translations will not be loaded without restarting puppet Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Unassigned Created: 2017/10/02 4:29 PM Priority: Normal Reporter: Maggie Dreyer Once a module's translations have been added to gettext's translation repositories, they will not be updated, even if the underlying translation files change. For modules, in general when source files change at run time, the changes are picked up immediately. We would like to see the same behavior with translations, so we should investigate ways of reloading translation files and adding them to the translation repositories when updates are made to a module's PO files. Add Comment
Jira (FACT-1773) option to install libfacter to specific directory
Title: Message Title James Hogarth created an issue Facter / FACT-1773 option to install libfacter to specific directory Issue Type: Bug Assignee: Unassigned Created: 2017/10/02 4:22 PM Priority: Normal Reporter: James Hogarth The leatherman_install currently installs libfacter to /lib specifically and the ruby bindings use this path. I'm packaging the update to 3.9.0 for Fedora and to comply with our guidelines the 64bit library needs to go into /lib64 (well /usr/lib64 but /lib64 symlinks here). Can this please be made configurable as a CMAKE option so we have the library in the correct place? Add Comment This message was sent by
Jira (FACT-1772) libfacter install should support other directories than /lib
Title: Message Title James Hogarth created an issue Facter / FACT-1772 libfacter install should support other directories than /lib Issue Type: Bug Assignee: Unassigned Created: 2017/10/02 4:15 PM Priority: Normal Reporter: James Hogarth As part of the update to 3.9.0 for Fedora the facter package needs to split into facter, development headers and any bindings (eg ruby bindings) to comply with guidelines. Currently the libfacter library installs directly to /lib and the ruby bindings call on libfacter.so in /lib specifically. The library should be able to be installed to /lib64 (well /usr/lib64 but /lib64 symlinks here) to comply with the guidelines whilst packaging the update. Add Comment
Jira (PUP-8014) Create an evironment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Nick Walker commented on PUP-8014 Re: Create an evironment_ttl setting to clear short-lived puppet environments from memory Henrik Lindberg Thomas Hallgren I'd be interested in your thoughts on how difficult something like this would be to implement. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8014) Create an evironment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title
Nick Walker updated an issue
Puppet / PUP-8014
Create an evironment_ttl setting to clear short-lived puppet environments from memory
Change By:
Nick Walker
h1. The Problem When running puppet server you have two levers to adjust how short-lived Puppet environments are cleared from memory. 1. {{max-requests-per-instance}} in {{puppetserver.conf}}2. {{environment_timeout}} in {{puppet.conf}} /{{environment.conf}} Each option has it's own cons, because neither addresses the core problem we want to tackle. We want to clear Puppet environments from memory when they haven't been used for a while and there's no direct way to do that. With {{max-requests-per-instance}} we're destroying a whole JRuby which takes out all of the Puppet environments that were ever loaded into it. With {{environment_timeout}} we have to clear environments after a certain amount of time even if that environment is getting lots of catalogs compiled against it right now. h1. The solutionCreate a setting that allows for expiring a Puppet environment after it has not been compiled against for a set period of time. If we were to call this setting {{environment_ttl}} and we set it to {{30m}} then that would mean that if you ran an agent against your test environment and then then no other agents checked into that environment for 30m then the test environment would be marked expired. This gets to the bottom of the problem customers see when deploying short-lived Puppet environments. This setting would be a global setting not a per-environment setting. h1. Caveats The setting would presumably interact with the environment_timeout setting. This setting could only be applied when the environment_timeout is not 0. If environment_timeout is 0 then this setting would emit a warning and do nothing. When the environment_timeout < environment_ttl then environment_timeout would take precedence because it would mark the environment expired before the environment_ttl code had a chance to run. When environment_timeout > environment_ttl then this is the primary use case for the setting and environment_ttl finally has a chance to help expire environments more quickly/efficiently than our current settings allow.
Add Comment
Jira (PDOC-178) @api private not showing up in generated docs
Title: Message Title William Yardley created an issue Puppet Strings / PDOC-178 @api private not showing up in generated docs Issue Type: Bug Affects Versions: PDOC 1.1.0 Assignee: Unassigned Created: 2017/10/02 2:58 PM Priority: Normal Reporter: William Yardley As best I can tell, putting @api private doesn't seem to be adding any special text / banner to puppet strings generated docs. # @api private # jmeter::install #
Jira (FACT-1654) Create library for virtualization detection
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1654 Create library for virtualization detection Change By: Geoff Nichols Epic Status: In Progress Done Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8015) Refactor puppet-agent-bootstrap module into something palatable by puppet core
Title: Message Title AJ Roetker moved an issue Puppet / PUP-8015 Refactor puppet-agent-bootstrap module into something palatable by puppet core Change By: AJ Roetker Key: PE PUP - 22360 8015 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8014) Create an evironment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Nick Walker updated an issue Puppet / PUP-8014 Create an evironment_ttl setting to clear short-lived puppet environments from memory Change By: Nick Walker Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8014) Create an evironment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title
Nick Walker updated an issue
Puppet / PUP-8014
Create an evironment_ttl setting to clear short-lived puppet environments from memory
Change By:
Nick Walker
h1. The Problem When running puppet server you have two levers to adjust how short-lived Puppet environments are cleared from memory. 1. {{ max-requests-per-instance }} in {{ puppetserver.conf }} 2. {{ environment_timeout }} in {{ puppet.conf }} Each option has it's own cons, because neither addresses the core problem we want to tackle. We want to clear Puppet environments from memory when they haven't been used for a while and there's no direct way to do that. With {{ max-requests-per-instance }} we're destroying a whole JRuby which takes out all of the Puppet environments that were ever loaded into it. With {{ environment_timeout }} we have to clear environments after a certain amount of time even if that environment is getting lots of catalogs compiled against it right now. h1. The solutionCreate a setting that allows for expiring a Puppet environment after it has not been compiled against for a set period of time. If we were to call this setting {{environment_ttl}} and we set it to {{30m}} then that would mean that if you ran an agent against your test environment and then then no other agents checked into that environment for 30m then the test environment would be marked expired. This gets to the bottom of the problem customers see when deploying short-lived Puppet environments. h1. Caveats The setting would presumably interact with the environment_timeout setting. This setting could only be applied when the environment_timeout is not 0. If environment_timeout is 0 then this setting would emit a warning and do nothing. When the environment_timeout < environment_ttl then environment_timeout would take precedence because it would mark the environment expired before the environment_ttl code had a chance to run. When environment_timeout > environment_ttl then this is the primary use case for the setting and environment_ttl finally has a chance to help expire environments more quickly/efficiently than our current settings allow.
Add Comment
Jira (PUP-8014) Create an evironment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Nick Walker updated an issue Puppet / PUP-8014 Create an evironment_ttl setting to clear short-lived puppet environments from memory Change By: Nick Walker CS Priority: Needs Priority CS Frequency: 5 - >90% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8014) Create an evironment_ttl setting to clear short-lived puppet environments from memory
Title: Message Title Nick Walker created an issue Puppet / PUP-8014 Create an evironment_ttl setting to clear short-lived puppet environments from memory Issue Type: Bug Assignee: Unassigned Created: 2017/10/02 2:39 PM Priority: Normal Reporter: Nick Walker The Problem When running puppet server you have two levers to adjust how short-lived Puppet environments are cleared from memory. 1. max-requests-per-instance in puppetserver.conf 2. environment_timeout in puppet.conf Each option has it's own cons, because neither addresses the core problem we want to tackle. We want to clear Puppet environments from memory when they haven't been used for a while and there's no direct way to do that. With max-requests-per-instance we're destroying a whole JRuby which takes out all of the Puppet environments that were ever loaded into it. With environment_timeout we have to clear environments after a certain amount of time even if that environment is getting lots of catalogs compiled against it right now. The solution Create a setting that allows for expiring a Puppet environment after it has not been compiled against for a set period of time. If we were to call this setting environment_ttl and we set it to 30m then that would mean that if you ran an agent against your test environment and then then no other agents checked into that environment for 30m then the test environment would be marked expired. This gets to the bottom of the problem customers see when deploying short-lived Puppet environments. Caveats The setting would presumably interact with the
Jira (PUP-7955) Update puppet to use the rubocop 0.49 or greater
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7955 Update puppet to use the rubocop 0.49 or greater Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8010) Implement ExecutionResult data type
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8010
Implement ExecutionResult data type
Change By:
Henrik Lindberg
A new datatype {{ExecutionResult}} is needed to encode the execution result on a set of nodes. An instance of this data type is to be returned from run_task() (and other execution functions that operate on a set of nodes).The data type should have the following methods:* {{names()}} - the {{String}} names (node-uris) of all nodes in the set as an Array* {{empty()}} - returns {{Boolean}} if the execution result set is empty* {{count()}} returns an {{Integer}} count of nodes* {{value(node-uri)}} the {{Variant\[Error, Any]}} for the given node-uri* {{values()}} - Array of {{Variant\[Error, Any]}} for the nodes in the result set* {{ok_nodes()}} - returns an ExecutionResult containing all nodes that have a non {{Error}} result* {{error_nodes()}} - returns an ExecutionResult containing all nodes that have an {{Error}} result* {{all_nodes()}} - is not initially needed since this is "self"* {{ok () }} - a {{Boolean}} that is the same as {{error_nodes.empty}}An instance of {{ExecutionResult}} should be {{Iterable}} as if it is a hash of {{String}} node-uri, to {{Variant\[Error, Any]}} - such that iterative functions like {{each}}, {{map}}, {{reduce}}, {{filter}} etc. work.A separate ticket will add support for the {{\[]}} access operator to {{ExecutionResult}}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To
Jira (PUP-8010) Implement ExecutionResult data type
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8010
Implement ExecutionResult data type
Change By:
Henrik Lindberg
A new datatype {{ExecutionResult}} is needed to encode the execution result on a set of nodes. An instance of this data type is to be returned from run_task() (and other execution functions that operate on a set of nodes).The data type should have the following methods:* {{names()}} - the {{String}} names (node-uris) of all nodes in the set as an Array* {{empty()}} - returns {{Boolean}} if the execution result set is empty* {{count()}} returns an {{Integer}} count of nodes* {{value(node-uri)}} the {{Variant\[Error, Any]}} for the given node-uri* {{values()}} - Array of {{Variant\[Error, Any]}} for the nodes in the result set* {{ok_nodes()}} - returns an ExecutionResult containing all nodes that have a non {{Error}} result* {{error_nodes()}} - returns an ExecutionResult containing all nodes that have an {{Error}} result* {{all_nodes()}} - is not initially needed since this is "self" * {{ok}} - a {{Boolean}} that is the same as {{error_nodes.empty}} An instance of {{ExecutionResult}} should be {{Iterable}} as if it is a hash of {{String}} node-uri, to {{Variant\[Error, Any]}} - such that iterative functions like {{each}}, {{map}}, {{reduce}}, {{filter}} etc. work.A separate ticket will add support for the {{\[]}} access operator to {{ExecutionResult}}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To
Jira (PUP-7845) Support leaf certificate CRL checking
Title: Message Title Garrett Guillotte commented on PUP-7845 Re: Support leaf certificate CRL checking Adrien Thebo The external CA doc https://docs.puppet.com/puppet/latest/config_ssl_external_ca.html doesn't differentiate between leaf and chain checks, so I think it also needs updating in addition to the release note. Do we have a test or use case for this setting that I can consult beyond the reference details in the setting's docs so I can explain the differences between chain and leaf and why a user would choose one or the other? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8013) Module translations are not loaded unless module has metadata
Title: Message Title Michael Smith assigned an issue to Geoff Nichols Puppet / PUP-8013 Module translations are not loaded unless module has metadata Change By: Michael Smith Assignee: Geoff Nichols Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8013) Module translations are not loaded unless module has metadata
Title: Message Title Michael Smith created an issue Puppet / PUP-8013 Module translations are not loaded unless module has metadata Issue Type: Bug Assignee: Unassigned Created: 2017/10/02 1:14 PM Priority: Normal Reporter: Michael Smith This is probably acceptable, but thought I'd report it for posterity. If modules don't have metadata, they will not have a forge_name and thus initializing i18n will be skipped. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7845) Support leaf certificate CRL checking
Title: Message Title Garrett Guillotte commented on PUP-7845 Re: Support leaf certificate CRL checking Kenn Hussey Adrien Thebo Got it, thanks Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title Geoff Nichols commented on PUP-7988 Re: resources/group/should_create test fails on fedora-26-64a PR #6251 merged to puppet#4.10.x at https://github.com/puppetlabs/puppet/commit/c57ee8cecb1085a72949af874d51bebc6c94b28a. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title John Duarte commented on PUP-7988 Re: resources/group/should_create test fails on fedora-26-64a PR filed to update beaker options file used by `ci:test:aio` rake task to use the pre-suite disabling the `sssd` service. https://github.com/puppetlabs/puppet/pull/6251 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7967) Add a file_upload() function
Title: Message Title Josh Cooper assigned an issue to John Duarte Puppet / PUP-7967 Add a file_upload() function Change By: Josh Cooper Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7979) Add a run_command() function
Title: Message Title Josh Cooper assigned an issue to Eric Sorenson Puppet / PUP-7979 Add a run_command() function Change By: Josh Cooper Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7980) Add a run_script() function to enable this bolt feature from the language
Title: Message Title Josh Cooper assigned an issue to Eric Sorenson Puppet / PUP-7980 Add a run_script() function to enable this bolt feature from the language Change By: Josh Cooper Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8012) Make access operator [] work on ExecutionResult
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8012 Make access operator [] work on ExecutionResult Change By: Henrik Lindberg Sprint: Tasks Kanban Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8012) Make access operator [] work on ExecutionResult
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8012 Make access operator [] work on ExecutionResult Issue Type: New Feature Assignee: Unassigned Created: 2017/10/02 10:52 AM Priority: Normal Reporter: Henrik Lindberg The access operator [] when applied to an ExecutionResult (PUP-8010) should use the index as a node-uri and return the same as the value(node-uri) method. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1770) Facter acceptance test ticket_1238_hostname_fqdn.rb fails on Solaris 11 x86_6
Title: Message Title Enis Inan updated an issue Facter / FACT-1770 Facter acceptance test ticket_1238_hostname_fqdn.rb fails on Solaris 11 x86_6 Change By: Enis Inan Summary: Facter acceptance tests fail test ticket_1238_hostname_fqdn.rb fails on Solaris 11 x86_64 x86_6 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8010) Implement ExecutionResult data type
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8010 Implement ExecutionResult data type Issue Type: New Feature Assignee: Unassigned Created: 2017/10/02 10:39 AM Priority: Major Reporter: Henrik Lindberg A new datatype ExecutionResult is needed to encode the execution result on a set of nodes. An instance of this data type is to be returned from run_task() (and other execution functions that operate on a set of nodes). The data type should have the following methods: names() - the String names (node-uris) of all nodes in the set as an Array empty() - returns Boolean if the execution result set is empty count() returns an Integer count of nodes value(node-uri) the Variant[Error, Any] for the given node-uri values() - Array of Variant[Error, Any] for the nodes in the result set ok_nodes() - returns an ExecutionResult containing all nodes that have a non Error result error_nodes() - returns an
Jira (FACT-1771) Additional hypervisor support in libwhereami
Title: Message Title Branan Riley updated an issue Facter / FACT-1771 Additional hypervisor support in libwhereami Change By: Branan Riley Fix Version/s: whereami 0.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1771) Additional hypervisor support in libwhereami
Title: Message Title Casey Williams created an issue Facter / FACT-1771 Additional hypervisor support in libwhereami Issue Type: Epic Assignee: Unassigned Components: libwhereami Created: 2017/10/02 10:21 AM Priority: Normal Reporter: Casey Williams Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message
Jira (PUP-7845) Support leaf certificate CRL checking
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-7845 Support leaf certificate CRL checking See the `certificate_revocation` documentation for more information about the new `leaf` setting. https://github.com/puppetlabs/puppet/blob/5.3.1/lib/puppet/defaults.rb#L859 Change By: Adrien Thebo Release Notes Summary: Puppet can be configured to perform end entity certificate revocation checking. When the `certificate_revocation` setting is set to `leaf` and Puppet is authenticating an SSL connection, Puppet will check the revocation status of the end entity certificate of the peer, instead of attempting to check the revocation status of every certificate in the chain. This allows users to perform basic revocation checking when using an intermediate CA certificate with Puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8009) Performance regression with lots of modules and gettext
Title: Message Title Michael Smith created an issue Puppet / PUP-8009 Performance regression with lots of modules and gettext Issue Type: Bug Affects Versions: PUP 5.3.1 Assignee: Unassigned Created: 2017/10/02 10:16 AM Fix Versions: PUP 5.3.2 Priority: Critical Reporter: Michael Smith We've seen a ~30% reduction in compilation capacity with Puppet 5.3 (over Puppet 4.10). It appears to be related to gettext setup at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/gettext/config.rb#L37-L69. We haven't fully isolated why, but the best guess is that code related to accessing modules during compilation is being called too frequently, and resulting in lots of disk-related activity. Add Comment
Jira (PUP-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Thanks Henrik Lindberg. I'll give that a try today. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1770) Facter acceptance tests fail on Solaris 11 x86_64
Title: Message Title Enis Inan created an issue Facter / FACT-1770 Facter acceptance tests fail on Solaris 11 x86_64 Issue Type: CI Blocker Assignee: Unassigned Attachments: 20171002-puppet-agent-1.10-facter-test.log Created: 2017/10/02 9:17 AM Fix Versions: FACT 3.6.z Priority: Normal Reporter: Enis Inan Link to the job: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/1.10.x/view/Non-Standard/job/platform_puppet-agent_intn-van-sys_suite-secondary-facter-1.10.x/SLAVE_LABEL=beaker,TEST_TARGET=solaris11-64a/14/ Relevant part of the output: 13:41:29 Failed Tests Cases: 13:41:29 Test Case tests
Jira (PUP-8007) In module ruby loading does not work in Pal API
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8007 In module ruby loading does not work in Pal API Change By: Kenn Hussey Sprint: Tasks ELP Kanban Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title Enis Inan commented on PUP-7988 Re: resources/group/should_create test fails on fedora-26-64a Failure happened again: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/1.10.x/view/Suite/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-1.10.x/SLAVE_LABEL=beaker,TEST_TARGET=fedora26-64a/68/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8007) In module ruby loading does not work in Pal API
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8007 In module ruby loading does not work in Pal API Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8006) Wrong PID dir
Title: Message Title Michael Smith commented on PUP-8006 Re: Wrong PID dir You seem to have an inconsistent installation of Puppet. In Puppet 4, the PID location was changed from /var/log/puppet to /var/log/puppetlabs. (Of course, I can't find the file where that changed happen at the moment). This may be an issue with upgrading, where the service isn't stopped before code is updated, and then you're unable to restart the service. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8008) puppet module install fails to install apt 4.2.0
Title: Message Title David Mallon commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 I've passed the ticket on to Jesse Scott to investigate too Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7845) Support leaf certificate CRL checking
Title: Message Title Kenn Hussey commented on PUP-7845 Re: Support leaf certificate CRL checking Garrett Guillotte do you have what you need here? This is going out with 5.3.1. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Thomas Honey commented on PUP-8008 Re: puppet module install fails to install apt 4.2.0 That looks very likely !! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8008 puppet module install fails to install apt 4.2.0 Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8008) puppet module install fails to install apt 4.2.0
Title: Message Title Geoff Nichols moved an issue Puppet / PUP-8008 puppet module install fails to install apt 4.2.0 Change By: Geoff Nichols Component/s: Process & Documentation Component/s: PMT Key: PA PUP - 1585 8008 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7992) Puppetserver errors reading pcore objects with non-english locale
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7992 Puppetserver errors reading pcore objects with non-english locale Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Jakob commented on FACT-1284 Re: Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result Branan, yeah, good idea - I just filed FACT-1769. To be honest I don't know where the canonical documentation for Facter is located. rubydoc.info describes Facter::Core::Execution#execute(http://www.rubydoc.info/gems/facter/2.4.6/Facter/Core/Execution#execute-class_method) like this: :on_fail (Object) — How to behave when the command could not be run. Specifying :raise will raise an error, anything else will return that object on failure. Default is :raise. Because of the suggestion in this comment thread, I made the mistake of interpreting this as meaning that on_fail would be invoked when the command executed but exited with a non-zero status code. Its intended meaning seems obvious in hindsight, but perhaps it could be phrased even clearer. I'm not sure what the relation is between Facter::Core::Execution.execute and Facter::Util::Resolution.exec, if any. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1769) Ruby API for command execution with status code in result
Title: Message Title Jakob commented on FACT-1769 Re: Ruby API for command execution with status code in result This issued urged in comment section of linked issue Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1769) Ruby API for command execution with status code in result
Title: Message Title Jakob created an issue Facter / FACT-1769 Ruby API for command execution with status code in result Issue Type: New Feature Assignee: Unassigned Created: 2017/10/02 6:33 AM Priority: Normal Reporter: Jakob Facter::Util::Resolution.exec returns standard output and sets `$?` aka `$CHILD_STATUS`. These two globals are hard (impossible?) to stub in tests. A more testable API would be nice. Additionally, it would be nice if standard error was available in addition to standard output. The ability to specify the content of standard input might also be an idea. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8007) In module ruby loading does not work in Pal API
Title: Message Title Thomas Hallgren moved an issue Puppet / PUP-8007 In module ruby loading does not work in Pal API Change By: Thomas Hallgren Key: BOLT PUP - 86 8007 Project: Puppet Task Runner Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8005) undefined method `set_optional' when using Option[Struct] in an EPP
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8005 undefined method `set_optional' when using Option[Struct] in an EPP Change By: Kenn Hussey Fix Version/s: PUP 5.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8006) Wrong PID dir
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8006 Wrong PID dir Change By: Kenn Hussey Fix Version/s: PUP 5.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Thomas Hallgren commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Ben Ford, do you have an environment where this can be reproduced? I'm not able to, but I think I might have a fix. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Nicky Kernohan updated an issue Puppet / PUP-8002 "Attempt to redefine entity" caused by using a resource collector Change By: Nicky Kernohan CS Priority: Major CS Severity: 3 - Serious CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1768) libwhereami uses deprecated syntax
Title: Message Title James Hogarth created an issue Facter / FACT-1768 libwhereami uses deprecated syntax Issue Type: Bug Affects Versions: whereami 0.1.2 Assignee: Unassigned Components: libwhereami Created: 2017/10/02 4:23 AM Environment: Fedora 28 (rawhide) build environment: boost: 1.64 cmake: 3.93 gcc: 7.2.1 Priority: Normal Reporter: James Hogarth I'm getting Facter updated in Fedora from the fairly ancient 2.4.3 to the current version. A new optional dependency on on libwhereami was added in 3.9.0 and I'd like to include this if possible. In a rawhide environment running the build results in warnings of deprecated syntax though:
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-8002 "Attempt to redefine entity" caused by using a resource collector Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Thomas Hallgren commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector I think this might be the same problem as in PE-22152 where the user provided I got a stacktrace using from a puppet lookup --compile. The resource collector query is resolved using PuppetDB which in turn creates a parser resource. Creating parser resources is bad in combination with puppet generate types. If the collector is the first to resolve the type, and that resolution is done through PuppetDB, then this error will happen everytime. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3684) PDB performance issues with large structured facts
Title: Message Title Martin Ewings updated an issue PuppetDB / PDB-3684 PDB performance issues with large structured facts Change By: Martin Ewings As _emphasized text_As outlined in PDB-2631, PuppetDB encounters severe performance degradation in the presence of large structured facts. In support, we have seen this impact with mountpoint or partitions facts of only 20-30 KiB, which is not terribly uncommon. As noted in that ticket, the expectation is that PDB will be able to handle anything Facter might throw at it.This issue was resolved in PDB-3249, but the fix was removed by PDB-3611. We need a solution that will allow large structured facts to be stored in PDB without causing causing query performance issues. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3684) PDB performance issues with large structured facts
Title: Message Title Martin Ewings updated an issue PuppetDB / PDB-3684 PDB performance issues with large structured facts Change By: Martin Ewings _emphasized text_As As outlined in PDB-2631, PuppetDB encounters severe performance degradation in the presence of large structured facts. In support, we have seen this impact with mountpoint or partitions facts of only 20-30 KiB, which is not terribly uncommon. As noted in that ticket, the expectation is that PDB will be able to handle anything Facter might throw at it.This issue was resolved in PDB-3249, but the fix was removed by PDB-3611. We need a solution that will allow large structured facts to be stored in PDB without causing causing query performance issues. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Kevin Reeuwijk commented on PUP-1974 Re: Theme: Sensitive Data in Catalogs Owen Rodabaugh customers fail audits when systems they manage have regulatory requirements on security and the auditor finds a catalog file on the system that contains plaintext secrets. From what KPN told me, they can pass the audits (for now) if the cleartext issues are limited to the Puppet server (i.e. PuppetDB and agent logs), but not if there are unprotected secrets on client machines. I've played around with the node_encrypt module, but it's Redact() function only works for arguments that were passed to the module it's called in. You can't simply protect any bit of information (like you can with Sensitive()), you really have to design the flow of information to work with how node_encrypt was designed. This isn't obvious at first, causing confusion for people who try to use the module and vague error messages that lead people to believe the module is broken. Which it isn't, the Redact() function is just designed for a very particular use case that doesn't cover all our needs. I agree that ideally the Sensitive data type comes with it's own built-in encryption. However this may take significantly longer to implement as it touches many points in the system. A good stopgap measure that would help customers like KPN today, is to encrypt the agent's catalog file on disk. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8005) undefined method `set_optional' when using Option[Struct] in an EPP
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8005 undefined method `set_optional' when using Option[Struct] in an EPP Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8005) undefined method `set_optional' when using Option[Struct] in an EPP
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-8005 undefined method `set_optional' when using Option[Struct] in an EPP Change By: Thomas Hallgren Affects Version/s: PUP 5.2.0 Affects Version/s: PUP 5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8006) Wrong PID dir
Title: Message Title steclest created an issue Puppet / PUP-8006 Wrong PID dir Issue Type: Bug Affects Versions: PUP 5.2.0 Assignee: Laura Raney Components: Functions Created: 2017/10/02 1:23 AM Environment: Linux 2.6.32-696.1.1.el6.x86_64 puppet-agent-5.2.0-1.el6.x86_64 Fix Versions: PUP 5.2.0 Priority: Normal Reporter: steclest Hello all, the init script for Puppet agent (V 5.2.0) seems to be broken. It sets piddir=/var/run/puppetlabs for agent.pid, but the PID is not in this folder. I find this file in the old PID folder, i. e., /var/run/puppet . As a workaround, I hacked the init script. In order to run "service puppet status/stop"
