Jira (PUP-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title R.I.Pienaar commented on PUP-8405 Re: Knock-out-prefix fails with more than 3 merges Imo this makes this feature more or less useless. It works too differently and have very surprising restrictions orthogonal to the rest of hiera If it can’t be fixed it should be removed rather than just be super weird Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7939) I18N japanese translation does not contain leading spaces
Title: Message Title Erwin Hom assigned an issue to Erwin Hom Puppet / PUP-7939 I18N japanese translation does not contain leading spaces Change By: Erwin Hom Assignee: Erwin Hom Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7939) I18N japanese translation does not contain leading spaces
Title: Message Title Erwin Hom commented on PUP-7939 Re: I18N japanese translation does not contain leading spaces Are the leading spaces in front of text to format the output? If that is case, I believe that the leading spaces should be in the code, not in the string resource. Also, it's quite possible that the segmentation process is not including the leading spaces in the source text view. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8409
Puppet config print lists invalid value for environment_timeout when set to unlimited
Change By:
Past Haus
When running {{puppet config print --all}} on the command line with {{environment_timeout}} set to {{unlimited}} in {{puppet.conf}}, the value for {{environment_timeout}} is listed as {{Infinity}}, which is not a valid setting (it can be an integer, 0 or {{unlimited}}). As a user if I saw this I would presume it was a valid setting.When I try using {{Infinity}} as a setting value for {{environment_timeout}}, I get a not so helpful error message and stack trace.{code}puppet apply --environment_timeout=Infinity -e "notify{'foo':}"/Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:43:in `munge': Invalid 'time to live' format '"Infinity"' for parameter: environment_timeout (Puppet::Settings::ValidationError) from /Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:25:in `munge' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1310:in `interpolate' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1082:in `value_sym' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1054:in `value' from /Users/matthaus/src/puppet/lib/puppet/settings/environment_conf.rb:87:in `environment_timeout' from /Users/matthaus/src/puppet/lib/puppet/environments.rb:414:in `entry' from /Users/matthaus/src/puppet/lib/puppet/environments.rb:345:in `get' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:131:in `module_directories' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:166:in `search_directories' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:100:in `files_to_load' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:220:in `files_to_load' from /Users/matthaus/src/puppet/lib/puppet/application.rb:212:in `available_application_names' from /Users/matthaus/src/puppet/lib/puppet/util/command_line.rb:90:in `find_subcommand' from /Users/matthaus/src/puppet/lib/puppet/util/command_line.rb:73:in `execute' from /usr/bin/puppet:5:in `'{code} The simple reproducer here is:{code}puppet config print --environment_timeout=unlimited environment_timeoutInfinity{code}
Add Comment
Jira (PUP-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title
Past Haus updated an issue
Puppet / PUP-8409
Puppet config print lists invalid value for environment_timeout when set to unlimited
Change By:
Past Haus
When running {{puppet config print --all}} on the command line with {{environment_timeout}} set to {{unlimited}} in {{puppet.conf}} , the default value for {{environment_timeout}} is listed as {{Infinity}}, which is not a valid setting (it can be an integer, 0 or {{unlimited}}). As a user if I saw this I would presume it was a valid setting.When I try using {{Infinity}} as a setting value for {{environment_timeout}}, I get a not so helpful error message and stack trace.{code}puppet apply --environment_timeout=Infinity -e "notify{'foo':}"/Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:43:in `munge': Invalid 'time to live' format '"Infinity"' for parameter: environment_timeout (Puppet::Settings::ValidationError) from /Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:25:in `munge' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1310:in `interpolate' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1082:in `value_sym' from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1054:in `value' from /Users/matthaus/src/puppet/lib/puppet/settings/environment_conf.rb:87:in `environment_timeout' from /Users/matthaus/src/puppet/lib/puppet/environments.rb:414:in `entry' from /Users/matthaus/src/puppet/lib/puppet/environments.rb:345:in `get' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:131:in `module_directories' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:166:in `search_directories' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:100:in `files_to_load' from /Users/matthaus/src/puppet/lib/puppet/util/autoload.rb:220:in `files_to_load' from /Users/matthaus/src/puppet/lib/puppet/application.rb:212:in `available_application_names' from /Users/matthaus/src/puppet/lib/puppet/util/command_line.rb:90:in `find_subcommand' from /Users/matthaus/src/puppet/lib/puppet/util/command_line.rb:73:in `execute' from /usr/bin/puppet:5:in `'{code}
Add Comment
Jira (PUP-8409) Puppet config print lists invalid default value for environment_timeout
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8409 Puppet config print lists invalid default value for environment_timeout Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Past Haus updated an issue Puppet / PUP-8409 Puppet config print lists invalid value for environment_timeout when set to unlimited Change By: Past Haus Summary: Puppet config print lists invalid default value for environment_timeout when set to unlimited Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8409) Puppet config print lists invalid default value for environment_timeout
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8409 Puppet config print lists invalid default value for environment_timeout Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8409 Puppet config print lists invalid value for environment_timeout when set to unlimited Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8409) Puppet config print lists invalid default value for environment_timeout
Title: Message Title
Past Haus commented on PUP-8409
Re: Puppet config print lists invalid default value for environment_timeout
The setting is also case sensitive, so passing Unlimited results in a similar error message.
puppet apply --environment_timeout=Unlimited -e "notify{'foo':}"
/Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:43:in `munge': Invalid 'time to live' format '"Unlimited"' for parameter: environment_timeout (Puppet::Settings::ValidationError)
from /Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:25:in `munge'
from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1310:in `interpolate'
from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1082:in `value_sym'
from /Users/matthaus/src/puppet/lib/puppet/settings.rb:1054:in `value'
from /Users/matthaus/src/puppet/lib/puppet/settings/environment_conf.rb:87:in `environment_timeout'
from /Users/matthaus/src/puppet/lib/puppet/environments.rb:414:in `entry'
from /Users/matthaus/src/puppet/lib/puppet/environments.rb:345:in `get'
Jira (PUP-8409) Puppet config print lists invalid default value for environment_timeout
Title: Message Title
Past Haus created an issue
Puppet / PUP-8409
Puppet config print lists invalid default value for environment_timeout
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/01/30 4:53 PM
Priority:
Normal
Reporter:
Past Haus
When running puppet config print --all on the command line, the default value for environment_timeout is listed as Infinity, which is not a valid setting (it can be an integer, 0 or unlimited). As a user if I saw this I would presume it was a valid setting.
When I try using Infinity as a setting value for environment_timeout, I get a not so helpful error message and stack trace.
puppet apply --environment_timeout=Infinity -e "notify{'foo':}"
/Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:43:in `munge': Invalid 'time to live' format '"Infinity"' for parameter: environment_timeout (Puppet::Settings::ValidationError)
from /Users/matthaus/src/puppet/lib/puppet/settings/ttl_setting.rb:25:in `munge'
Jira (PDB-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title
Jarret Lavallee updated an issue
PuppetDB / PDB-3824
Duplicate unordered structured facts violates unique constraint
Change By:
Jarret Lavallee
Duplicate custom structured facts that are not ordered cause replace_facts to fail with the following error message. {code}2018-01-30 16:10:11,844 ERROR [p.p.command] [10,612] [replace facts] Retrying after attempt 0 for testing.example.com, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\x88680eb39ee03249046efa1c51598d865afc7519) already exists.org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\x88680eb39ee03249046efa1c51598d865afc7519) already exists.{code}The hash is not currently in the database. {code}pe-puppetdb=# select * from fact_values where value_hash = '\x88680eb39ee03249046efa1c51598d865afc7519'; id | value_hash | value_type_id | value_integer | value_float | value_string | value_boolean | value++---+---+-+--+---+---(0 rows){code}This occurs when there are two structured facts with the same contents, but not in the same order. Below is a basic facts payload to be sent into replace_facts reproduce the issue . {code:json}{ "certname": "testing.example.com", "values": {"a_structured_fact": { "element2": {"somevalue": "2" }, "element1": {"somevalue": "1" }},"another_structured_fact": { "element1": {"somevalue": "1" }, "element2": {"somevalue": "2" }} }, "environment": "production", "producer_timestamp": "2018-01-29T15:34:59.792-08:00", "producer": "somemaster.example.com"}{code}If I put both facts in the same order, we do not encounter the error. It sounds like the fix is to sort the structured facts when checking if they already exist. The end result of this issue is that we get many continual retries and discards. The facts are never updated in PuppetDB for these nodes, unless the value_hash already exists in the database.
Add Comment
Jira (PDB-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-3824 Duplicate unordered structured facts violates unique constraint Change By: Jarret Lavallee CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title
Jarret Lavallee updated an issue
PuppetDB / PDB-3824
Duplicate unordered structured facts violates unique constraint
Change By:
Jarret Lavallee
Duplicate custom structured facts that are not ordered , cause replace_facts fails due to fail with the following error message. {code}2018-01-30 16:10:11,844 ERROR [p.p.command] [10,612] [replace facts] Retrying after attempt 0 for testing.example.com, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\x88680eb39ee03249046efa1c51598d865afc7519) already exists.org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "fact_values_value_hash_key" Detail: Key (value_hash)=(\x88680eb39ee03249046efa1c51598d865afc7519) already exists.{code}The hash is not currently in the database. {code}pe-puppetdb=# select * from fact_values where value_hash = '\x88680eb39ee03249046efa1c51598d865afc7519'; id | value_hash | value_type_id | value_integer | value_float | value_string | value_boolean | value++---+---+-+--+---+---(0 rows){code}This occurs when there are two structured facts with the same contents, but not in the same order. Below is a basic facts payload to be sent into replace_facts. {code:json}{ "certname": "testing.example.com", "values": {"a_structured_fact": { "element2": {"somevalue": "2" }, "element1": {"somevalue": "1" }},"another_structured_fact": { "element1": {"somevalue": "1" }, "element2": {"somevalue": "2" }} }, "environment": "production", "producer_timestamp": "2018-01-29T15:34:59.792-08:00", "producer": "somemaster.example.com"}{code}If I put both facts in the same order, we do encounter the error. It sounds like the fix is to sort the structured facts when checking if they already exist. The end result of this issue is that we get many retries and discards. The facts are never updated in PuppetDB for these nodes, unless the value_hash already exists in the database.
Add Comment
Jira (PDB-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-3824 Duplicate unordered structured facts violates unique constraint Change By: Jarret Lavallee Acceptance Criteria: Structured facts in any order should not cause failures in replace_facts. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3824) Duplicate unordered structured facts violates unique constraint
Title: Message Title Jarret Lavallee created an issue PuppetDB / PDB-3824 Duplicate unordered structured facts violates unique constraint Issue Type: Bug Affects Versions: PDB 5.1.3 Assignee: Unassigned Components: PuppetDB Created: 2018/01/30 4:25 PM Environment: Puppet 5.3.3 with PuppetDB 5.1.3 and duplicate structured facts Priority: Normal Reporter: Jarret Lavallee Duplicate custom structured facts that are not ordered, replace_facts fails due to the following error message. 2018-01-30 16:10:11,844 ERROR [p.p.command] [10,612] [replace facts] Retrying after attempt 0 for testing.example.com, due to: org.postgresql.util.PSQL
Jira (PUP-8388) Prepare release announcement (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett commented on PUP-8388 Re: Prepare release announcement (Puppet Platform 5.3.4) Drafted announcement: https://docs.google.com/document/d/1EuAeyjNJFqHZMGgXpZtlvgY8tihr7KnsJqDqLX2HixQ/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8408) Fix misspelled variable and method names in puppet
Title: Message Title Eric Delaney created an issue Puppet / PUP-8408 Fix misspelled variable and method names in puppet Issue Type: Task Affects Versions: PUP 5.3.3 Assignee: Eric Delaney Created: 2018/01/30 3:45 PM Fix Versions: PUP 5.4.0 Priority: Normal Reporter: Eric Delaney A community member found a handful of variable names that are misspelled. This is to correct those misspelled names. -step "should allow param class defaults to be overriden" +step "should allow param class defaults to be overridden"
Jira (PUP-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jean Bond commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module I have some changes I am making to the "Publishing modules on the Forge" page, but they have their own ticket. Besides the release note, I don't think any other docs are needed for this. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-291) Task show displays a confusing type for empty parameters
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-291 Task show displays a confusing type for empty parameters Change By: Zach Reichert Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Eric Delaney commented on PUP-8407 Re: Puppet benchmarks fail due to gettext-setup initialization Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/e1da19b5df7d790faf179f353ff9be9894c38575 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3819) Manually smoke test all artifacts (PuppetDB 5.1.4)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3819 Manually smoke test all artifacts (PuppetDB 5.1.4) Change By: Nirupama Mantha Comment: Covered in the platform-wide smoke testing. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3819) Manually smoke test all artifacts (PuppetDB 5.1.4)
Title: Message Title Nirupama Mantha commented on PDB-3819 Re: Manually smoke test all artifacts (PuppetDB 5.1.4) Covered by Branan and Sean in the platform-wide smoke testing Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7394) Puppet::Util.replace_file cannot be used to create a read-only file (on non-Windows)
Title: Message Title Melissa Stone commented on PUP-7394 Re: Puppet::Util.replace_file cannot be used to create a read-only file (on non-Windows) I manually verified this code change in both windows and non-windows, and it is behaving as expected Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7397) FileBucket should use `Puppet::Util::replace_file` to write contents
Title: Message Title Melissa Stone commented on PUP-7397 Re: FileBucket should use `Puppet::Util::replace_file` to write contents I manually verified this code change in both windows and non-windows, and it is behaving as expected Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-230) Build helper for Bolt installation
Title: Message Title Zach Reichert updated an issue Puppet Task Runner / BOLT-230 Build helper for Bolt installation Change By: Zach Reichert Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-230) Build helper for Bolt installation
Title: Message Title Zach Reichert assigned an issue to Unassigned Puppet Task Runner / BOLT-230 Build helper for Bolt installation Change By: Zach Reichert Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8407 Puppet benchmarks fail due to gettext-setup initialization Change By: Josh Cooper Acceptance Criteria: Running "bundle exec rake benchmark:all:run" should execute all of puppet's benchmarks successfully. Note you may need to include the "development" group when performing a bundle install to pull in ruby-prof. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8407 Puppet benchmarks fail due to gettext-setup initialization Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-230) Build helper for Bolt installation
Title: Message Title Zach Reichert commented on BOLT-230 Re: Build helper for Bolt installation As I am leaving I am unsure who would be responsible for advancing this. I'm going to leave a list of questions here for posterity. Currently this tool pins to bolt 0.7.0 * In the future I think we would want to install the latest * This would require maintenance to this tool as breaking changes occur This tool doesn't yet manage the ruby version on the system that accepts Bolt This tool is not able to install/run bolt on the test coordinator In the modules tests they run a bolt command against 'localhost' * This will need to change in the future Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PUP-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8407 Puppet benchmarks fail due to gettext-setup initialization Change By: Josh Cooper QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title Thomas Hallgren commented on PUP-8405 Re: Knock-out-prefix fails with more than 3 merges Running the lookup with a --explain will provide information on what happens in each merge. The knock-outs are not specifically reported but you see the inputs and the result of each individual merge. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title Thomas Hallgren commented on PUP-8405 Re: Knock-out-prefix fails with more than 3 merges I understand that, but the knock-out is not remembered after a merge. It's a concept implemented by the underlying deep_merge operation and forgotten once a merge has taken place. It doesn't matter if values were actually knocked out or not during that merge. The knock-out is only applicable to the immediate merge with the next level, not with levels beyond that. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title
Ryan Struber updated an issue
Puppet / PUP-8405
Knock-out-prefix fails with more than 3 merges
Change By:
Ryan Struber
When defining multiple levels of hierarchy in hiera.yaml (more than 3), and requesting hiera to lookup a key that is found on more than 3 levels, and lookup options for that key are configured to merge deep with a knockout prefix, the merge fails to knockout the key matching the higher precedence knockout.Steps to reproduce:{code:yaml}hiera.yaml: version: 5 defaults:datadir: data data_hash: yaml_data hierarchy: - name: node specific data path: node/%{::site.node}.yaml - name: product data path: product/%{::site.product}.yaml - name: os data path: os/%{::os.family}.yaml - name: global data path: common.yaml common.yaml: lookup_options:classes: merge:strategy: deepknockout_prefix: -- classes:- profiles::motd- profiles::networkos/RedHat.yaml: classes:- profiles::yumproduct/product.yaml classes: - profiles::applicationnode/node.yaml: classes: - profiles::puppet - agent - -- profiles::network - network{code}*Expected*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::yum- profiles::application- network{code}*Actual*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::network- profiles::yum- profiles::application- network{code}Removing a layer from the hierarchy causes the merge to behave as expected. The difference being:{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l4{code}vs{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l3{code}*Verified Affected Versions*Puppet 4.10.0Puppet 4.10.9Puppet 5.3.1
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Kris Bosland updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Kris Bosland Acceptance Criteria: When a provider fails in prefetch: 1. The agent run should be reported as failed. 2. Resources that use that provider should be marked as failed and not evaluated. 3. Resources that depend on resources that use that provider should not be evaluated. 4. Unrelated resources should still run. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title Ryan Struber commented on PUP-8405 Re: Knock-out-prefix fails with more than 3 merges I'm not sure I got the concept across correctly given your comment. I'm not reporting the knock-out is failing to perform multiple times. Rather if you merge together too many levels, knock-out fails to perform at all. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-290) Decompose --insecure flag
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: Alex Dreyer Release Notes Summary: * Breaking CLI Change *The --insecure and -k options are no longer available. They have been replaced with a [no-]ssl option for winrm and a [no-]check-host-keys option for the ssh transport. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-292) Allow run_* functions to set 'run-as' value
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-292 Allow run_* functions to set 'run-as' value Change By: Alex Dreyer Release Notes Summary: run_command, run_script and run_task functions now accept a `_run_as` arg to allow some actions to escalate in plans. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-81) Error message regarding ssh-agent on successful run
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-81 Error message regarding ssh-agent on successful run Change By: Alex Dreyer Release Notes Summary: Bolt will no longer attempt to connect to the ssh agent if it's not available Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-81) Error message regarding ssh-agent on successful run
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-81 Error message regarding ssh-agent on successful run Change By: Alex Dreyer Fix Version/s: BOLT 0.16.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-304) Show parameter names and types with bolt plan show
Title: Message Title Zach Reichert updated an issue Puppet Task Runner / BOLT-304 Show parameter names and types with bolt plan show Change By: Zach Reichert Fix Version/s: BOLT 0.16.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title Thomas Hallgren commented on PUP-8405 Re: Knock-out-prefix fails with more than 3 merges This is per design. A knock-out prefix is only capable of doing one knock-out. Once the knock-out is performed, it's not remembered. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3020) Add action for deleting settings from puppet config
Title: Message Title Jorie Tappa commented on PUP-3020 Re: Add action for deleting settings from puppet config Did we determine that the section was required? Or that the behavior would mimic some other existing puppet config behavior to determine section if not stated? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Jayant Sane commented on PUP-8378 Re: Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Submitted PR: https://github.com/puppetlabs/puppet/pull/6581 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8407 Puppet benchmarks fail due to gettext-setup initialization Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8407 Puppet benchmarks fail due to gettext-setup initialization Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8407 Puppet benchmarks fail due to gettext-setup initialization Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8407 Puppet benchmarks fail due to gettext-setup initialization Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8407) Puppet benchmarks fail due to gettext-setup initialization
Title: Message Title Josh Cooper created an issue Puppet / PUP-8407 Puppet benchmarks fail due to gettext-setup initialization Issue Type: Bug Assignee: Unassigned Created: 2018/01/30 11:11 AM Fix Versions: PUP 5.3.5 Priority: Normal Reporter: Josh Cooper Puppet Version: 5.3.x Puppet Server Version: n/a Running puppet benchmarks fails: $ bx rake benchmark:many_modules:run mkdir -p /var/folders/8m/d6146zxd6bv_3h8y4ykvvxh4gn/T/many_modules20180130-73932-2mw6bc user system totalreal
Jira (PUP-8404) ssh_authorized_key should mention effective uid on debug output
Title: Message Title Melissa Stone commented on PUP-8404 Re: ssh_authorized_key should mention effective uid on debug output Merged into master with https://github.com/puppetlabs/puppet/commit/d3be04b3bafbadd84989aef0f7ab8eae09ebb5e4 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8404) ssh_authorized_key should mention effective uid on debug output
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8404 ssh_authorized_key should mention effective uid on debug output Change By: Melissa Stone Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8406) Puppet Error datatype uses 'message' not 'msg' as hash key
Title: Message Title Alex Dreyer created an issue Puppet / PUP-8406 Puppet Error datatype uses 'message' not 'msg' as hash key Issue Type: Bug Assignee: Unassigned Created: 2018/01/30 10:16 AM Priority: Normal Reporter: Alex Dreyer This means using it requires translation from bolt task output and does not align with our standard API data representation of hashes that use 'msg'. The error datatype should be updates to create data hashes that include msg not message keys and it should expect that key when it is instantiated from a hash. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8243) Allow ERB templates to be tolerant of a leading BOM
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8243 Allow ERB templates to be tolerant of a leading BOM Change By: Craig Gomes Sprint: Windows Hopper Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6429) Provide a way to install SSL certs on Windows machines
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6429 Provide a way to install SSL certs on Windows machines Change By: Craig Gomes Sprint: Windows Hopper Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8404) ssh_authorized_key should mention effective uid on debug output
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8404 ssh_authorized_key should mention effective uid on debug output Change By: Melissa Stone Assignee: Leo Antunes Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8404) ssh_authorized_key should mention effective uid on debug output
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8404 ssh_authorized_key should mention effective uid on debug output Change By: Melissa Stone Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8404) ssh_authorized_key should mention effective uid on debug output
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8404 ssh_authorized_key should mention effective uid on debug output Change By: Melissa Stone QA Risk Assessment: Needs Assessment No Action Release Notes Summary: Adds additional debug output when creating directories with the ssh authorized key parsed provider Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8404) ssh_authorized_key should mention effective uid on debug output
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8404 ssh_authorized_key should mention effective uid on debug output Change By: Melissa Stone Acceptance Criteria: * debug output includes the additional information of which user the directory is being created with Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-8258 Cached catalogs settings are ignored if noop is set to true Change By: Jacob Helwig Assignee: Jacob Helwig Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8404) ssh_authorized_key should mention effective uid on debug output
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8404 ssh_authorized_key should mention effective uid on debug output Change By: Melissa Stone Sub-team: Coremunity Team: Platform Core Sprint: Platform Core Hopper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-291) Task show displays a confusing type for empty parameters
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-291 Task show displays a confusing type for empty parameters Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-291) Task show displays a confusing type for empty parameters
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-291
Task show displays a confusing type for empty parameters
Change By:
David Kramer
Empty parameters display as type {{Data}} which while technically correct may be confusing. They This should probably instead be displayed as {{Any}} , {{Optional[Any]}}, {{Optional[Data}} or not displayed so that it's clearer to users. *note* This may be migrated to a PUP ticket.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-291) Task show displays a confusing type for empty parameters
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-291 Task show displays a confusing type for empty parameters Change By: David Kramer Summary: Task show displays the wrong a confusing type for empty parameters Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title
Ryan Struber updated an issue
Puppet / PUP-8405
Knock-out-prefix fails with more than 3 merges
Change By:
Ryan Struber
When defining multiple levels of hierarchy in hiera.yaml (more than 3), and requesting hiera to lookup a key that is found on more than 3 levels, and lookup options for that key are configured to merge deep with a knockout prefix, the merge fails to knockout the key matching the higher precedence knockout.Steps to reproduce:{code:yaml}hiera.yaml: version: 5 defaults:datadir: data data_hash: yaml_data hierarchy: - name: node specific data path: node/%{::site.node}.yaml - name: product data path: product/%{::site.product}.yaml - name: os data path: os/%{::os.family}.yaml - name: global data path: common.yaml common.yaml: lookup_options:classes: merge:strategy: deepknockout_prefix: -- classes:- profiles::motd- profiles::networkos/RedHat.yaml: classes:- profiles::yumproduct/product.yaml classes: - profiles::applicationnode/node.yaml: classes: - profiles::puppet-agent - --profiles::network - network{code}*Expected*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::yum- profiles::application- network{code}*Actual*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::network- profiles::yum- profiles::application- network{code}Removing a layer from the hierarchy causes the merge to behave as expected. The difference being:{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l4{code}vs{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l3{code}*Verified Affected Versions*Puppet 4.10.0Puppet 4.10.9 Puppet 5.3.1
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title
Ryan Struber updated an issue
Puppet / PUP-8405
Knock-out-prefix fails with more than 3 merges
Change By:
Ryan Struber
When defining multiple levels of hierarchy in hiera.yaml (more than 3), and requesting hiera to lookup a key that is found on more than 3 levels, and lookup options for that key are configured to merge deep with a knockout prefix, the merge fails to knockout the key matching the higher precedence knockout.Steps to reproduce:{code:yaml}hiera.yaml: version: 5 defaults:datadir: data data_hash: yaml_data hierarchy: - name: node specific data path: node/%{::site.node}.yaml - name: product data path: product/%{::site.product}.yaml - name: os data path: os/%{::os.family}.yaml - name: global data path: common.yaml common.yaml: lookup_options:classes: merge:strategy: deepknockout_prefix: -- classes:- profiles::motd- profiles::networkos/RedHat.yaml: classes:- profiles::yumproduct/product.yaml classes: - profiles::applicationnode/node.yaml: classes: - profiles::puppet-agent - --profiles::network - network{code}*Expected*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::yum- profiles::application- network{code}*Actual*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::network- profiles::yum- profiles::application- network{code}Removing a layer from the hierarchy causes the merge to behave as expected. The difference being:{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l4{code}vs{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l3{code}* Verified Affected Versions*Puppet 4.10.0Puppet 4.10.9
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title
Ryan Struber updated an issue
Puppet / PUP-8405
Knock-out-prefix fails with more than 3 merges
Change By:
Ryan Struber
When defining multiple levels of hierarchy in hiera.yaml (more than 3), and requesting hiera to lookup a key that is found on more than 3 levels, and lookup options for that key are configured to merge deep with a knockout prefix, the merge fails to knockout the key matching the higher precedence knockout.Steps to reproduce:{code:yaml}hiera.yaml: version: 5 defaults:datadir: data data_hash: yaml_data hierarchy: - name: node specific data path: node/%{::site.node}.yaml - name: product data path: product/%{::site.product}.yaml - name: os data path: os/%{::os.family}.yaml - name: global data path: common.yaml common.yaml: lookup_options:classes: merge:strategy: deepknockout_prefix: -- classes:- profiles::motd- profiles::networkos/RedHat.yaml: classes:- profiles::yumproduct/product.yaml classes: - profiles::applicationnode/node.yaml: classes: - profiles::puppet-agent - --profiles::network - network{code}*Expected*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::yum- profiles::application- network{code}*Actual*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::network- profiles::yum- profiles::application- network{code}Removing a layer from the hierarchy causes the merge to behave as expected. The difference being:{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l4{code}vs{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l3{code}* Affect Affected Versions*Puppet 4.10.0Puppet 4.10.9
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland updated an issue Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kris Bosland Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title
Ryan Struber updated an issue
Puppet / PUP-8405
Knock-out-prefix fails with more than 3 merges
Change By:
Ryan Struber
When defining multiple levels of hierarchy in hiera.yaml (more than 3), and requesting hiera to lookup a key that is found on more than 3 levels, and lookup options for that key are configured to merge deep with a knockout prefix, the merge fails to knockout the key matching the higher precedence knockout.Steps to reproduce:{code:yaml}hiera.yaml: version: 5 defaults:datadir: data data_hash: yaml_data hierarchy: - name: node specific data path: node/%{::site.node}.yaml - name: product data path: product/%{::site.product}.yaml - name: os data path: os/%{::os.family}.yaml - name: global data path: common.yaml common.yaml: lookup_options:classes: merge:strategy: deepknockout_prefix: -- classes:- profiles::motd- profiles::networkos/RedHat.yaml: classes:- profiles::yumproduct/product.yaml classes: - profiles::applicationnode/node.yaml: classes: - profiles::puppet-agent - --profiles::network - network{code}*Expected*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::yum- profiles::application- network{code}*Actual*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::network- profiles::yum- profiles::application- network{code}Removing a layer from the hierarchy causes the merge to behave as expected. The difference being:{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l4{code}vs{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l3{code} Verified in puppet version *Affect Versions*Puppet 4.10.0 , Puppet 4.10.9
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title
Ryan Struber updated an issue
Puppet / PUP-8405
Knock-out-prefix fails with more than 3 merges
Change By:
Ryan Struber
When defining multiple levels of hierarchy in hiera.yaml (more than 3), and requesting hiera to lookup a key that is found on more than 3 levels, and lookup options for that key are configured to merge deep with a knockout prefix, the merge fails to knockout the key matching the higher precedence knockout.Steps to reproduce:{code:yaml}hiera.yaml: version: 5 defaults:datadir: data data_hash: yaml_data hierarchy: - name: node specific data path: node/%{::site.node}.yaml - name: product data path: product/%{::site.product}.yaml - name: os data path: os/%{::os.family}.yaml - name: global data path: common.yaml common.yaml: lookup_options:classes: merge:strategy: deepknockout_prefix: -- classes:- profiles::motd- profiles::networkos/RedHat.yaml: classes:- profiles::yumproduct/product.yaml classes: - profiles::applicationnode/node.yaml: classes: - profiles::puppet-agent - --profiles::network - network{code}*Expected*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::yum- profiles::application- network{code}*Actual*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::network- profiles::yum- profiles::application- network{code}Removing a layer from the hierarchy causes the merge to behave as expected. The difference being:{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l4{code}vs{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l3{code} Verified in puppet version 4.10.0, 4.10.9
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title Eric Delaney commented on PUP-6217 Re: site.pp with file resource containing UTF8 failing on certain platforms With the updates for I18n support, this is not a problem as long as you the language setting is a UTF-8 based character set. If the LANGUAGE/LANG is set to use a non-UTF-8 based character set, then ruby will start up with Encoding.default_external set to a non-UTF-8 character and ruby may have issues concatenating the non-UTF-8 strings with UTF-8 strings. On the 5.3.4 branch the test is now running on all platforms. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-123) Better fail function for plans
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-123
Better fail function for plans
Change By:
David Kramer
The puppet fail function results in a ParserError and a backtrace. This makes sense for catalog compilation but it's not well suited for plan execution where failure is expected and probably not related to the code.Plans should have a fail_plan function that accepts either (msg, kind, and details) or (error) and returns a Bolt::Error subclass named Bolt::PlanFailure .{noformat}fail_plan(msg, kind=puppetlabs/plan-error, details={}){noformat}{noformat}fail_plan(error){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-123) Better fail function for plans
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-123 Better fail function for plans Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8405 Knock-out-prefix fails with more than 3 merges Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-123) Better fail function for plans
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-123
Better fail function for plans
Change By:
David Kramer
The puppet fail function results in a ParserError and a backtrace. This makes sense for catalog compilation but it's not well suited for plan execution where failure is expected and probably not related to the code.Plans should have a fail or raise error fail_plan function that accepts either ( msg, kind, and details ) or (error) and returns a Bolt::Error subclass.{noformat}fail_plan(msg, kind=puppetlabs/ plain plan -error, details={}){noformat} {noformat}fail_plan(error){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-8405) Knock-out-prefix fails with more than 3 merges
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-8405 Knock-out-prefix fails with more than 3 merges Change By: Henrik Lindberg Method Found: Needs Assessment Issue Type: Task Bug Key: HI PUP - 595 8405 Project: Hiera Puppet Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-123) Better fail function for plans
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-123
Better fail function for plans
Change By:
David Kramer
The puppet fail function results in a ParserError and a backtrace. This makes sense for catalog compilation but it's not well suited for plan execution where failure is expected and probably not related to the code.Plans should have a fail or raise error function that accepts msg, kind, and details and returns a Bolt::Error subclass.{noformat} raise_error fail_plan (msg, kind=puppetlabs/plain-error, details={}){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-7398) deprecate puppet module generate
Title: Message Title Bryan Jen assigned an issue to Bryan Jen Puppet / PUP-7398 deprecate puppet module generate Change By: Bryan Jen Assignee: Bryan Jen Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-2868 `puppet config print` confusing for users Change By: Kris Bosland Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-253) Set up containers for ssh unit and integration tests
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-253 Set up containers for ssh unit and integration tests Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-253) Set up containers for ssh unit and integration tests
Title: Message Title David Kramer commented on BOLT-253 Re: Set up containers for ssh unit and integration tests If you're looking for prior art, the Modules team uses containers, and the hands-on lab uses containers. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-253) Set up containers for ssh unit and integration tests
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-253 Set up containers for ssh unit and integration tests Change By: David Kramer Sub-team: bolt Bolt Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-218) Bolt file_upload should upload files consistent with the context of run-as
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-218 Bolt file_upload should upload files consistent with the context of run-as Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6237) PMT should gracefully fall back to older, compatible versions of modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6237 PMT should gracefully fall back to older, compatible versions of modules Change By: Josh Cooper Team: Platform Core Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7694) metadata.json created with `puppet module generate --skip-interview` fails validation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7694 metadata.json created with `puppet module generate --skip-interview` fails validation Change By: Josh Cooper Team: Platform Core Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-218) Bolt file_upload should upload files consistent with the context of run-as
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-218
Bolt file_upload should upload files consistent with the context of run-as
Change By:
David Kramer
When using {{run-as}}, uploaded files would be expected to be usable in any subsequent tasks. Potentially the file might be uploaded to a location the non-escalated login user doesn't have permission to write to, and that should work.This change should impact the {{run-as}} option on the CLI, the {{_run_as}} option in the function, and script uploads/runs. This change only impacts the ssh transport at this time. Proposal: All files should be uploaded to a temporary location, their permissions/ownership updated, and then moved to their final location. (Look at replace_file in Puppet for prior art.)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-8258) Cached catalogs settings are ignored if noop is set to true
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8258 Cached catalogs settings are ignored if noop is set to true Change By: Josh Cooper Fix Version/s: PUP 4.10.z Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.5 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-595) Knock-out-prefix fails with more than 3 merges
Title: Message Title
Ryan Struber updated an issue
Hiera / HI-595
Knock-out-prefix fails with more than 3 merges
Change By:
Ryan Struber
When defining multiple levels of hierarchy in hiera.yaml (more than 3), and requesting hiera to lookup a key that is found on more than 3 levels, and lookup options for that key are configured to merge deep with a knockout prefix, the merge fails to knockout the key matching the higher precedence knockout.Steps to reproduce:{code:yaml}hiera.yaml: version: 5 defaults:datadir: data data_hash: yaml_data hierarchy: - name: node specific data path: node/%{::site.node}.yaml - name: product data path: product/%{::site.product}.yaml - name: os data path: os/%{::os.family}.yaml - name: global data path: common.yaml common.yaml: lookup_options:classes: merge:strategy: deepknockout_prefix: -- classes:- profiles::motd- profiles::networkos/RedHat.yaml: classes:- profiles::yumproduct/product.yaml classes: - profiles::applicationnode/node.yaml: classes: - profiles::puppet-agent - --profiles::network - network{code}*Expected*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::yum- profiles::application- network{code}*Actual*{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes profiles::motd- profiles::network- profiles::yum- profiles::application - network {code}Removing a layer from the hierarchy causes the merge to behave as expected. The difference being:{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l4{code}vs{code:java}puppet lookup --knock-out-prefix '--' --merge deep classes | grep 'Found key:' | wc -l3{code}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-218) Bolt file_upload should upload files consistent with the context of run-as
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-218
Bolt file_upload should upload files consistent with the context of run-as
Change By:
David Kramer
When using {{run-as}}, uploaded files would be expected to be usable in any subsequent tasks. Potentially the file might be uploaded to a location the non-escalated login user doesn't have permission to write to, and that should work.This change should impact the {{run-as}} option on the CLI, the {{_run_as}} option in the function, and script uploads/runs. Proposal: All files should be uploaded to a temporary location, their permissions/ownership updated, and then moved to their final location. (Look at replace_file in Puppet for prior art.)
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-218) Bolt file_upload should upload files consistent with the context of run-as
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-218
Bolt file_upload should upload files consistent with the context of run-as
Change By:
David Kramer
When using {{run-as}}, uploaded files would be expected to be usable in any subsequent tasks. Potentially the file might be uploaded to a location the non-escalated login user doesn't have permission to write to, and that should work.This affects both change should impact the {{run-as}} option on the CLI, as well as the {{_run_as}} option in the function , and script uploads/runs .
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-218) Bolt file_upload should upload files consistent with the context of run-as
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-218
Bolt file_upload should upload files consistent with the context of run-as
Change By:
David Kramer
When using {{run-as}}, uploaded files would be expected to be usable in any subsequent tasks. Potentially the file might be uploaded to a location the non-escalated login user doesn't have permission to write to, and that should work. This affects both the {{run-as}} option on the CLI, as well as the {{_run_as option}} in the function.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-218) Bolt file_upload should upload files consistent with the context of run-as
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-218
Bolt file_upload should upload files consistent with the context of run-as
Change By:
David Kramer
When using {{run-as}}, uploaded files would be expected to be usable in any subsequent tasks. Potentially the file might be uploaded to a location the non-escalated login user doesn't have permission to write to, and that should work.This affects both the {{run-as}} option on the CLI, as well as the {{_run_as option }} option in the function.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-315) Bolt Packages
Title: Message Title David Kramer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-315 Bolt Packages Change By: David Kramer Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-315) Bolt Packages
Title: Message Title David Kramer commented on BOLT-315 Re: Bolt Packages Lucy Wyman will create a spike ticket to investigate the questions. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-315) Bolt Packages
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-315 Bolt Packages Change By: David Kramer Sprint: Bolt Ready for Grooming Discover/Design Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-315) Bolt Packages
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-315 Bolt Packages Change By: David Kramer Bolt does not run well under ruby 2.0 which makes it hard for rh-7 users to use bolt. If we release OS packages for bolt that include or depend on ruby 2.3 this shouldn't be a problem. Questions:* What OSes do we want to build packages for?* How do we create packages for those OSes? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7398) deprecate puppet module generate
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7398 deprecate puppet module generate Change By: Josh Cooper Team: Platform OS Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-7398) deprecate puppet module generate
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7398 deprecate puppet module generate Change By: Josh Cooper Team: Platform Core OS Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-307) Standardize success and failure for plans
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-307
Standardize success and failure for plans
Change By:
David Kramer
Plan success should be defined as "returning" any value.Plan failure should be defined as "raising" an Error.h3. raise_error function:(moved to BOLT-123)h3. catch_errors option:Add a new {{\_catch\_errors}} option on the {{run_plan}} function. By default plan execution should stop if a plan called with run_plan errors. When a plan is called with {{\_catch\_errors => true}} it should instead return a pcore {{Error}} object containing the error. This should work both for the exceptions thrown by run_* and from the raise_error function. This will not catch other types of failure (such as the {{fail}} function).h3. output:The plan outputter should display error message in red for {{human}} format and the entire error hash as pretty printed json for the {{json}} format before exiting.h3. Questions:1. Is it a problem that _catch_error in a plan returns an error object while catch_error in a task/command/file/script returns a ResultSet? "no" 2. How do we interact with the Error Datatype? "make it look more like other Bolt error objects"
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-7398) deprecate puppet module generate
Title: Message Title Jean Bond commented on PUP-7398 Re: deprecate puppet module generate Just a vote up from Docs here. I'd love to be able to just tell users not to use `puppet module generate` any more. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-307) Standardize success and failure for plans
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-307 Standardize success and failure for plans Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
