Jira (PDB-3857) Error during garbage collection: java.sql.BatchUpdateException
Title: Message Title Sebastian Reitenbach commented on PDB-3857 Re: Error during garbage collection: java.sql.BatchUpdateException indeed I get errors logged there as well, should have provided them with the initial report: 2018-03-01 05:53:50.658 CET [89665] ERROR: set-returning functions are not allowed in CASE at character 559 2018-03-01 05:53:50.658 CET [89665] HINT: You might be able to move the set-returning function into a LATERAL FROM item. 2018-03-01 05:53:50.658 CET [89665] STATEMENT: with recursive live_paths(key, path, value) as (select key, key as path, value from (select (jsonb_each(stable||volatile)).* from factsets) as base_case union all select sub_path as key, sub_paths.path||'#~'||sub_path as path, sub_value as value from (select * from (select path, case jsonb_typeof(value) when 'object' then (jsonb_each(value)).key when 'array' then generate_series(0, jsonb_array_length(value - 1))::text end as sub_path, case jsonb_typeof(value) when 'object' then (jsonb_each(value)).value when 'array' then jsonb_array_elements(value) end as sub_value from live_paths) as candidates where candidates.sub_path is not null) as sub_paths) delete from fact_paths fp where not exists (select 1 from live_paths where live_paths.path = fp.path) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-6507) Puppet help: Hide bad subcommands, and sort remainder by usefulness
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6507 Puppet help: Hide bad subcommands, and sort remainder by usefulness Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 6.y Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8176) Puppet Hangs when recursing directories with link to /dev/urandom in the tree
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8176
Puppet Hangs when recursing directories with link to /dev/urandom in the tree
Change By:
Josh Cooper
Summary:
{ALL} : { Puppet Hangs when recursing directories with link to /dev/urandom in the tree }
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8504) Emit deprecation warning for ruby 2.1 and maybe 2.2
Title: Message Title Josh Cooper created an issue Puppet / PUP-8504 Emit deprecation warning for ruby 2.1 and maybe 2.2 Issue Type: Improvement Assignee: Unassigned Created: 2018/02/28 9:03 PM Priority: Normal Reporter: Josh Cooper Ruby 2.1 is EOL. Ruby 2.2 will be EOL March 18. We need to bump the Puppet::OLDEST_RECOMMENDED_RUBY_VERSION to either 2.2 or 2.3 in preparation for Puppet 6. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-7326) Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts
Title: Message Title Glenn Sarti assigned an issue to Ethan Brown Puppet / PUP-7326 Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts Change By: Glenn Sarti Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7326) Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts
Title: Message Title Glenn Sarti commented on PUP-7326 Re: Group resource (with auth_membership) failes if local Windows group contains not resolvable Domain accounts Merged into 4.10.x at; https://github.com/puppetlabs/puppet/commit/addf82ad5b9a43ef9e4330ebd6796bbf7c4d8105 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3858) gRPC ingest allows in schemas with invalid names
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3858 gRPC ingest allows in schemas with invalid names Issue Type: Bug Assignee: Unassigned Created: 2018/02/28 5:03 PM Priority: Normal Reporter: Russell Mull Schema name and namespace need to be checked against the friendly-string regex, and the schema rejected if they don't match. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-338) Local transport for bolt
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-338 Local transport for bolt Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1826) Add JNI support to Facter gem
Title: Message Title Maggie Dreyer created an issue Facter / FACT-1826 Add JNI support to Facter gem Issue Type: Task Assignee: Unassigned Created: 2018/02/28 4:41 PM Priority: Normal Reporter: Maggie Dreyer In order to use the CFacter gem in puppetserver's dev and testing workflows, it needs JNI support. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-363) 'all' target with mixed ssh and winrm transports runs all nodes on both transports
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-363 'all' target with mixed ssh and winrm transports runs all nodes on both transports Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-363) 'all' target with mixed ssh and winrm transports runs all nodes on both transports
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-363 'all' target with mixed ssh and winrm transports runs all nodes on both transports Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8409) Puppet config print lists invalid value for environment_timeout when set to unlimited
Title: Message Title Kris Bosland commented on PUP-8409 Re: Puppet config print lists invalid value for environment_timeout when set to unlimited Merged to master at https://github.com/puppetlabs/puppet/commit/19a7f7bf64dbb81da2250fa5a1123c3fd12196c1 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2868) `puppet config print` confusing for users
Title: Message Title Kris Bosland commented on PUP-2868 Re: `puppet config print` confusing for users Updated acceptance criteria to include info for config set and config delete. Please let me know if you have a comment. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-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 Acceptance Criteria: * rspec tests includes ability to ensure that output is being written to stderr* test to validate warning to stderr when no section provided* config help - manually verify content* stdout is not altered * add the message for section and environment to config set and config delete Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-357) bolt-inventory-pdb omits confusing error with no arguments
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-357 bolt-inventory-pdb omits confusing error with no arguments Change By: Michael Smith Release Notes Summary: bolt-inventory-pdb now provides a clearer and accurate error when called without additional arguments.It will no longer error if a puppetdb.conf file is not present, so CLI flags can be used in place of a config file.It will no longer error if server-urls is a single string instead of an array. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-357) bolt-inventory-pdb omits confusing error with no arguments
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-357 bolt-inventory-pdb omits confusing error with no arguments Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-357) bolt-inventory-pdb omits confusing error with no arguments
Title: Message Title Michael Smith commented on BOLT-357 Re: bolt-inventory-pdb omits confusing error with no arguments Also encompasses other fixes to bolt-inventory-pdb in https://github.com/puppetlabs/bolt/pull/325. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-357) bolt-inventory-pdb omits confusing error with no arguments
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-357
bolt-inventory-pdb omits confusing error with no arguments
Change By:
Michael Smith
When {{bolt-inventory-pdb}} is run with no arguments, it emits {{Error: \ - \ -inventory is a required option}}. However, {{--inventory}} is not a valid option.This should state that an input file is required. It's a positional parameter.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-357) bolt-inventory-pdb omits confusing error with no arguments
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-357 bolt-inventory-pdb omits confusing error with no arguments Change By: Michael Smith Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-336) Treat --nodes as the nodes parameter for run plan
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-336 Treat --nodes as the nodes parameter for run plan Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-336) Treat --nodes as the nodes parameter for run plan
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-336 Treat --nodes as the nodes parameter for run plan Change By: Michael Smith Release Notes Summary: `bolt plan run` will now accept a `--nodes` flag that is equivalent to passing a `nodes` parameter for the plan. If the plan doesn't accept a `nodes` parameter it will error. Like with other commands, `--nodes` can be specified multiple times to construct a list of nodes as well as accept a comma-separated list. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Michael Smith Release Notes Summary: Bolt now provides a summary of succeeded and failed nodes at the end of `bolt file upload`, `bolt task run`, `bolt script run`, or `bolt command run`. That summary is a comma-separated list that can be copied to use as a nodes argument for re-running the successful or failed nodes. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-336) Treat --nodes as the nodes parameter for run plan
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-336 Treat --nodes as the nodes parameter for run plan Change By: Michael Smith Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Michael Smith Fix Version/s: Bolt Next Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-363) 'all' target with mixed ssh and winrm transports runs all nodes on both transports
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-363 'all' target with mixed ssh and winrm transports runs all nodes on both transports Issue Type: Bug Affects Versions: BOLT 0.16.3 Assignee: Unassigned Created: 2018/02/28 3:26 PM Priority: Normal Reporter: Michael Smith I have an inventory that looks something like groups: - name: linux nodes: - node1 - node2 - name: windows
Jira (PUP-8485) Cached failed confine lookups
Title: Message Title Josh Cooper commented on PUP-8485 Re: Cached failed confine lookups I think provider suitability uses this confine logic, e.g. to confine a provider based on a file existing. If so, then we should only cache misses if always_retry_plugins is false (as it is when running puppetserver). Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3852) PuppetDB query nodes based on fact broken
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3852 PuppetDB query nodes based on fact broken Change By: Jeff Yarnell Sprint: Data Platform 2018-03- 14 28 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8503) Agent SSL CLI
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8503 Agent SSL CLI Change By: Josh Cooper Create a new puppet application for managing agent keys, CSR and certificates. It should not rely on the indirector to make network requests. Issues in this epic should supersede/resolve issues in PUP-6828 (to simplify agent SSL initialization). Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3830) Command Queue Grows Steadily Over Time not related to load
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3830 Command Queue Grows Steadily Over Time not related to load Change By: Jeff Yarnell Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3838) Queries to the facts endpoint generates jsonb_each
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3838 Queries to the facts endpoint generates jsonb_each Change By: Jeff Yarnell Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8503) Agent SSL CLI
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8503 Agent SSL CLI Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3830) Command Queue Grows Steadily Over Time not related to load
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3830 Command Queue Grows Steadily Over Time not related to load Change By: Jeff Yarnell Fix Version/s: PDB 5.2.1 Fix Version/s: PDB 5.1.5 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8503) Agent SSL CLI
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8503 Agent SSL CLI Change By: Josh Cooper Team/s: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3857) Error during garbage collection: java.sql.BatchUpdateException
Title: Message Title Russell Mull commented on PDB-3857 Re: Error during garbage collection: java.sql.BatchUpdateException Hi Sebastian, thanks for the bug report! Can you provide any correlated logs from postgresql? I'd expect to see something related to this at the same frequency. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5985) Features are not being re-evaluated when a block is used
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5985
Features are not being re-evaluated when a block is used
Change By:
Josh Cooper
When a block is passed to the add method of Puppet::Util::Feature, it will only get evaluated once. This makes the "feature" feature practically unusable for anything except ruby libraries. *Updated*:Features should behave consistently when passed a block or an explicit list of ruby libraries. By default, they should not cache misses. If {{always_retry_plugins}} is false, then both block and non-block forms should cache misses, so that puppetserver doesn't try to reevaluate features.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-5985) Features are not being re-evaluated when a block is used
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-5985 Features are not being re-evaluated when a block is used Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3857) Error during garbage collection: java.sql.BatchUpdateException
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3857 Error during garbage collection: java.sql.BatchUpdateException Change By: Jeff Yarnell Sprint: Hopper/Triage Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3856 PQL specifying both type and title for class makes pql not find existing class Change By: Jeff Yarnell Sprint: Hopper/Triage Data Platform 2018-03-28 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3856 PQL specifying both type and title for class makes pql not find existing class Change By: Jeff Yarnell Sprint: Hopper/Triage Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5985) Features are not being re-evaluated when a block is used
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5985 Features are not being re-evaluated when a block is used Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5985) Features are not being re-evaluated when a block is used
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5985 Features are not being re-evaluated when a block is used Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5985) Features are not being re-evaluated when a block is used
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5985 Features are not being re-evaluated when a block is used Change By: Josh Cooper Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8503) Agent SSL CLI
Title: Message Title Josh Cooper created an issue Puppet / PUP-8503 Agent SSL CLI Issue Type: Epic Assignee: Unassigned Created: 2018/02/28 2:18 PM Fix Versions: PUP 6.0.0 Priority: Normal Reporter: Josh Cooper Create a new puppet application for managing agent keys, CSR and certificates. It should not rely on the indirector to make network requests. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8493) The differences between the vendored semantic_puppet and the original make it impossible to swap in the original
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8493 The differences between the vendored semantic_puppet and the original make it impossible to swap in the original Change By: Josh Cooper Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8477) selinux types are being set on every run
Title: Message Title Michael Smith commented on PUP-8477 Re: selinux types are being set on every run This seems somewhat related to PUP-2169. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1377) $ecdsakey fact does not represent specific key type
Title: Message Title Michael Smith updated an issue Facter / FACT-1377 $ecdsakey fact does not represent specific key type Change By: Michael Smith Fix Version/s: FACT 4.0.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8502) Puppet lookup always includes classes from the ENC
Title: Message Title Jarret Lavallee created an issue Puppet / PUP-8502 Puppet lookup always includes classes from the ENC Issue Type: Bug Affects Versions: PUP 5.3.5, PUP 4.10.9 Assignee: Thomas Hallgren Components: Hiera & Lookup Created: 2018/02/28 12:38 PM Priority: Normal Reporter: Jarret Lavallee The puppet lookup command evaluates classes that are returned from the ENC when the --compile flag is not specified. This results in failures of the lookup command if the catalog cannot be compiled. Reproduction Steps Install PE or Puppetserver Create a class like the one below. Classify a node with the class in the classifier Run puppet lookup anyhierakey --node A simple class to cause a failure in the lookup is below. class test ( String $myparam,
Jira (BOLT-362) bolt-inventory-pdb docs are not clear on how to configure the PuppetDB connection
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-362 bolt-inventory-pdb docs are not clear on how to configure the PuppetDB connection Issue Type: Improvement Assignee: Unassigned Components: DOCS Created: 2018/02/28 11:50 AM Priority: Normal Reporter: Michael Smith The docs at https://puppet.com/docs/bolt/0.x/inventory_file_generating.html point to the open-source puppet-query docs, but apparently that's easy to miss. Any way we can highlight it? Also, we talk about -token-file, but it's also possible to pass cacert and -url. Those three are required, so maybe we should just mention all of them. Add Comment
Jira (BOLT-362) bolt-inventory-pdb docs are not clear on how to configure the PuppetDB connection
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-362 bolt-inventory-pdb docs are not clear on how to configure the PuppetDB connection Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3832) puppetdb module config.ini mgmt should be in sync with rpm
Title: Message Title Rob Braden updated an issue PuppetDB / PDB-3832 puppetdb module config.ini mgmt should be in sync with rpm Change By: Rob Braden Sprint: Release Engineering Hopper Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8501) Switch to using multi_json
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-8501 Switch to using multi_json Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8501) Switch to using mult_json
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8501 Switch to using mult_json Issue Type: Task Assignee: Unassigned Created: 2018/02/28 11:25 AM Priority: Normal Reporter: Maggie Dreyer As part of an effort to improve puppetserver performance, we want to start using Jackson when running in JRuby (see SERVER-2098). In order to make this change transparently in Puppet, we want to use the multi_json gem to choose which backend to prefer at runtime, based on whether Jackson is installed. We need to update references to the built-in JSON gem to use multi_json instead. While we could confine this change to server-side code only, updating the references everywhere gives us the option to start using a faster library (e.g. Oj) agent-side as well in the future. Add Comment
Jira (PUP-8501) Switch to using multi_json
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8501 Switch to using multi_json Change By: Maggie Dreyer Summary: Switch to using mult_json multi_json Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Michael Smith Assignee: Michael Smith Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-223) Drop Ruby < 2.1.9 and Puppet < 4
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-223 Drop Ruby < 2.1.9 and Puppet < 4 Issue Type: Task Assignee: Unassigned Created: 2018/02/28 10:46 AM Priority: Normal Reporter: Eric Putnam Old Ruby and old Puppet are old. As part of the 2.0.0 major release, we will be dropping support for older Ruby and Puppet versions to modernize the gem and keep in line with the Puppet ecosystem. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.
Title: Message Title
Just updated an issue
Puppet / PUP-8500
puppet lookup cli should support adding facts as arguments, not just from a file.
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*It would be very useful if "puppet lookup" allowed setting fact overrides as direct arguments to a parameter.When automating something that uses "puppet lookup", having to write a temporary file containing some facts, then deleting the file afterwards is a pain, and is potentially fragile.If the facts could be specified directly, there would be no need for the file.*Desired Behavior:*{code:java}/opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --fact boo=test --fact test=boo --fact asdfasd=123~~~8<~~~$ echo $?0{code}*Actual Behavior:*{code:java}/opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --fact boo=test --fact test=boo --fact asdfasd=123Error: Could not parse application options: invalid option: --fact$ echo $?130{code} I've attached a patch which basically works, but I'm not very familiar with the code base, and so there's probably some style and other functional things I'm not considering.I'd be happy to create a PR, but let's see the patch is even close first :)Thanks.
Add Comment
This message was sent by Atlassian JIRA
Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.
Title: Message Title
Just updated an issue
Puppet / PUP-8500
puppet lookup cli should support adding facts as arguments, not just from a file.
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*It would be very useful if "puppet lookup" allowed specify facts setting fact overrides as direct arguments a parameter.When automating something that uses "puppet lookup", having to write a temporary file containing some facts, then deleting the file afterwards is a pain, and is potentially fragile.If the facts could be specified directly, there would be no need for the file.*Desired Behavior:*{code:java}/opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --fact boo=test --fact test=boo --fact asdfasd=123~~~8<~~~$ echo $?0{code}*Actual Behavior:*{code:java}/opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --fact boo=test --fact test=boo --fact asdfasd=123Error: Could not parse application options: invalid option: --fact$ echo $?130{code} I've attached a patch which basically works, but I'm not very familiar with the code base, and so there's probably some style and other functional things I'm not considering.I'd be happy to create a PR, but let's see the patch is even close first :)Thanks.
Add Comment
This message was sent by Atlassian JIRA
Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.
Title: Message Title
Just updated an issue
Puppet / PUP-8500
puppet lookup cli should support adding facts as arguments, not just from a file.
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*It would be very useful if "puppet lookup " allowed specify facts as direct arguments a parameter.When automating something that uses "puppet lookup", having to write a temporary file containing some facts, then deleting the file afterwards is a pain, and is potentially fragile.If the facts could be specified directly, there would be no need for the file.*Desired Behavior:*{code:java} /opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --fact boo=test --fact test=boo --fact asdfasd=123~~~8<~~~$ echo $?0{code}*Actual Behavior:*{code:java} /opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --fact boo=test --fact test=boo --fact asdfasd=123Error: Could not parse application options: invalid option: --fact$ echo $?130{code} I've attached a patch which basically works, but I'm not very familiar with the code base, and so there's probably some style and other functional things I'm not considering.I'd be happy to create a PR, but let's see the patch is even close first :)Thanks.
Add Comment
This message was sent by Atlassian JIRA
Jira (PDOC-222) Release 1.2.0
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-222 Release 1.2.0 Issue Type: Task Assignee: Eric Putnam Created: 2018/02/28 10:24 AM Priority: Normal Reporter: Eric Putnam Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (BOLT-263) log bolt results to a log file
Title: Message Title David Kramer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-263 log bolt results to a log file Change By: David Kramer Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-357) bolt-inventory-pdb omits confusing error with no arguments
Title: Message Title David Kramer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-357 bolt-inventory-pdb omits confusing error with no arguments Change By: David Kramer Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8500) puppet lookup cli should support adding facts as arguments, not just from a file.
Title: Message Title Just created an issue Puppet / PUP-8500 puppet lookup cli should support adding facts as arguments, not just from a file. Issue Type: New Feature Affects Versions: PUP 5.4.0 Assignee: Unassigned Attachments: lookup_direct_fact_option.patch Created: 2018/02/28 10:10 AM Priority: Normal Reporter: Just Puppet Version: 5.4.0 Puppet Server Version: n/a OS Name/Version: Ubuntu 16.04 It would be very useful if "puppet lookup allowed specify facts as direct arguments a parameter. When automating something that uses "puppet lookup", having to write a temporary file containing some facts, then deleting the file afterwards is a pain, and is potentially fragile. If the facts could be specified directly, there would be no need for the file. Desired Behavior: /opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --fact boo=test --fact test=boo --fact asdfasd=123 ~~~8<~~~ $ echo $?
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title
Just updated an issue
Puppet / PUP-8499
puppet lookup cli, using --facts and --node simultaneously breaks
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*When running "puppet lookup" with both the "–node" and "–facts" arguments, it exits with an error:{code:java}Error: Could not run: undefined method `add_extra_values' for nil:NilClass{code}*Desired Behavior:*It should return the correct value from hiera data, or at least not error even if no value is returned.*Actual Behavior:* {code:java}/opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --traceError: Could not run: undefined method `add_extra_values' for nil:NilClass {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node.rb:167:in `add_extra_facts' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:367:in `generate_scope' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:327:in `main' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:383:in `run_command' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:665:in `exit_on_fail' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute' }} {{ /opt/puppetlabs/puppet/bin/puppet:5:in `' }} {code}
Add Comment
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title
Just updated an issue
Puppet / PUP-8499
puppet lookup cli, using --facts and --node simultaneously breaks
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*When running "puppet lookup" with both the "–node" and "–facts" arguments, it exits with an error:{code:java} Error: Could not run: undefined method `add_extra_values' for nil:NilClass{code}*Desired Behavior:*It should return the correct value from hiera data, or at least not error even if no value is returned.*Actual Behavior:* {code:java}/opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none -- traceError traceError : Could not run: undefined method `add_extra_values' for nil:NilClass {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node.rb:167:in `add_extra_facts'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:367:in `generate_scope'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:327:in `main'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:383:in `run_command'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:665:in `exit_on_fail'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute'}} {{ /opt/puppetlabs/puppet/bin/puppet:5:in `'}}{code}
Add Comment
Jira (BOLT-128) Plans sensitive to tasks folder with additional files
Title: Message Title Michael Smith commented on BOLT-128 Re: Plans sensitive to tasks folder with additional files BOLT-246 looks like a duplicate of this. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-325) Set up containers for windows tests
Title: Message Title Michael Smith commented on BOLT-325 Re: Set up containers for windows tests This conflicts with a desire to test against older powershell versions in AppVeyor. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-235) Create encrypted variables in tasks
Title: Message Title Michael Smith commented on BOLT-235 Re: Create encrypted variables in tasks Seems like it would require a config option to provide the decryption secret. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-348) Add automated tests of system packages
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-348 Add automated tests of system packages Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-350) Add documentation for installing bolt as a system package
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-350 Add documentation for installing bolt as a system package Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-349) Update release automation to tag bolt-vanagon and publish packages
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-349 Update release automation to tag bolt-vanagon and publish packages Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-263) log bolt results to a log file
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-263 log bolt results to a log file Change By: Michael Smith Assignee: Michal Ruzicka Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title Just commented on PUP-8499 Re: puppet lookup cli, using --facts and --node simultaneously breaks After looking at the code, I found the problem seemed to be here, in puppet/application/lookup.rb : def generate_scope if options[:node] node = options[:node] else node = Puppet[:node_name_value] # If we want to lookup the node we are currently on # we must returning these settings to their default values Puppet.settings[:facts_terminus] = 'facter' end For some reason, not setting Puppet.settings[:facts_terminus] = 'facter' breaks the
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title Just updated an issue Puppet / PUP-8499 puppet lookup cli, using --facts and --node simultaneously breaks Change By: Just Attachment: lookup_add_extra_values_with_node.patch Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title
Just updated an issue
Puppet / PUP-8499
puppet lookup cli, using --facts and --node simultaneously breaks
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*When running " puppet lookup " with both the " –node " and " –facts " arguments, it exits with an error:{{Error: Could not run: undefined method `add_extra_values' for nil:NilClass}}*Desired Behavior:*It should return the correct value from hiera data, or at least not error even if no value is returned.*Actual Behavior:* { { code:java} /opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none -- trace}}{{Error traceError : Could not run: undefined method `add_extra_values' for nil:NilClass }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node.rb:167:in `add_extra_facts'}}{{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:367:in `generate_scope'}}{{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:327:in `main'}}{{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:383:in `run_command'}}{{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run'}}{{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:665:in `exit_on_fail'}}{{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run'}}{{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run'}}{{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute'}}{{ /opt/puppetlabs/puppet/bin/puppet:5:in `'}} {code}
Add Comment
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title
Just updated an issue
Puppet / PUP-8499
puppet lookup cli, using --facts and --node simultaneously breaks
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*When running ` puppet lookup ` with both the ` –node ` and ` –facts ` arguments, it exits with an error:{{Error: Could not run: undefined method `add_extra_values' for nil:NilClass}}*Desired Behavior:*It should return the correct value from hiera data, or at least not error even if no value is returned.*Actual Behavior:* ``` {{ /opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --trace }}{{ Error: Could not run: undefined method `add_extra_values' for nil:NilClass }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node.rb:167:in `add_extra_facts' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:367:in `generate_scope' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:327:in `main' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:383:in `run_command' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:665:in `exit_on_fail' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run' }} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute' }} {{ /opt/puppetlabs/puppet/bin/puppet:5:in `' }} ```
Add Comment
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title
Just updated an issue
Puppet / PUP-8499
puppet lookup cli, using --facts and --node simultaneously breaks
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*When running "puppet lookup" with both the "–node" and "–facts" arguments, it exits with an error: { { code:java} Error: Could not run: undefined method `add_extra_values' for nil:NilClass {code } } *Desired Behavior:*It should return the correct value from hiera data, or at least not error even if no value is returned.*Actual Behavior:* {code:java} /opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --traceError: Could not run: undefined method `add_extra_values' for nil:NilClass {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node.rb:167:in `add_extra_facts'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:367:in `generate_scope'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:327:in `main'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:383:in `run_command'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:665:in `exit_on_fail'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run'}} {{ /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute'}} {{ /opt/puppetlabs/puppet/bin/puppet:5:in `'}}{code}
Add Comment
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title
Just updated an issue
Puppet / PUP-8499
puppet lookup cli, using --facts and --node simultaneously breaks
Change By:
Just
*Puppet Version: 5.4.0* *Puppet Server Version: n/a* *OS Name/Version: Ubuntu 16.04*When running `puppet lookup` with both the `–node` and `–facts` arguments, it exits with an error: ``` {{ Error: Could not run: undefined method `add_extra_values' for nil:NilClass ``` }} *Desired Behavior:*It should return the correct value from hiera data, or at least not error even if no value is returned.*Actual Behavior:* ```/opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --traceError: Could not run: undefined method `add_extra_values' for nil:NilClass/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node.rb:167:in `add_extra_facts'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:367:in `generate_scope'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:327:in `main'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:383:in `run_command'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:665:in `exit_on_fail'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute'/opt/puppetlabs/puppet/bin/puppet:5:in `'```
Add Comment
Jira (PUP-8499) puppet lookup cli, using --facts and --node simultaneously breaks
Title: Message Title Just created an issue Puppet / PUP-8499 puppet lookup cli, using --facts and --node simultaneously breaks Issue Type: Bug Affects Versions: PUP 5.4.0, PUP 5.3.5 Assignee: Unassigned Created: 2018/02/28 9:25 AM Priority: Normal Reporter: Just Puppet Version: 5.4.0 Puppet Server Version: n/a OS Name/Version: Ubuntu 16.04 When running `puppet lookup` with both the `–node` and `–facts` arguments, it exits with an error: ```Error: Could not run: undefined method `add_extra_values' for nil:NilClass``` Desired Behavior: It should return the correct value from hiera data, or at least not error even if no value is returned. Actual Behavior: ``` /opt/puppetlabs/bin/puppet lookup site_domain --environment boo --facts test_facts.yaml --node myhost.r00.zone1.foo.bar.com --node_terminus=plain --external_nodes=none --trace Error: Could not run: undefined method `add_extra_values' for nil:NilClass /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/node.rb:167:in `add_extra_facts' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:367:in `generate_scope' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/lookup.rb:327:in `main' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:383:in `run_command' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:665:in `exit_on_fail' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:137:in `run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute' /opt/puppetlabs/puppet/bin/puppet:5:in `' ```
Jira (BOLT-336) Treat --nodes as the nodes parameter for run plan
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-336 Treat --nodes as the nodes parameter for run plan Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-336) Treat --nodes as the nodes parameter for run plan
Title: Message Title Lucy Wyman commented on BOLT-336 Re: Treat --nodes as the nodes parameter for run plan This looks good to me, if anyone else wants to take a look. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-345 Bolt should provide a better summary of failures Change By: Michael Smith Assignee: Lucy Wyman Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Michael Smith commented on BOLT-345 Re: Bolt should provide a better summary of failures Oh oops, I probably forgot to add that. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3854) stockpile/discard used to calculate command queue depth
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3854 stockpile/discard used to calculate command queue depth Change By: Jeff Yarnell Team: Data Platform Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (RRAL-1) Manage packages with the remote RAL
Title: Message Title Davin Hanlon updated an issue Remote Resource Abstract Layer / RRAL-1 Manage packages with the remote RAL Change By: Davin Hanlon Epic will detail the requirements for package management with the remote RAL. It will be required to perform package management where there is no Puppet agent installed. The following package managers should be supported initially, others will be added over time. * apt dpkg * rpm * chocolatey (windows) * yum The remote RAL should be able to determine the package manager to use based on what's available on the target. The remote RAL should be able to log in to the remote target, get package information, and also to perform actions (set) on packages on the remote target. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-8498) No title provided and "foo" is not a valid resource reference
Title: Message Title
Gavin Williams updated an issue
Puppet / PUP-8498
No title provided and "foo" is not a valid resource reference
Change By:
Gavin Williams
*Puppet Version:* 5.3.3 *Puppet Server Version:* N/AUpon creating some rspec-puppet tests for a new Puppet module, the following error was encountered:{code:java} 1) actora on centos-7-x86_64 with defaults should compile into a catalogue without dependency cyclesFailure/Error: it { should compile }error during compilation: No title provided and "actora" is not a valid resource reference on node lt0772.local{code}As there was no traceback to a specific file/line provided, this one proved challenging to track down. In the end, the following code was at fault:{code:java} ## install actora rpm (which should install nodejs and npm)package { $actora::package_name: ensure => $actora::version, notify => $actora::service_name, tag => ['actora::package']}{code}The notify here resolves to {{'actora'}}.A simple reproducer is:{code:java} $ cat foo/manifests/init.ppclass foo () { notify { 'testing':notify => xyz, }}$ puppet apply -t --exec 'include foo'Info: Loading factsError: No title provided and "xyz" is not a valid resource reference on node host.example.net{code}Thanks to [~JohnsonEarls] for the reproducer.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (RRAL-2) Get package information
Title: Message Title Davin Hanlon created an issue Remote Resource Abstract Layer / RRAL-2 Get package information Issue Type: Story Assignee: Unassigned Created: 2018/02/28 8:44 AM Priority: Normal Reporter: Davin Hanlon As a systems administrator I want to get package information from an agentless target. Requirements: Customer should be able to run a command to return information where there is no agent present, e.g. puppet resource package --target Return a list of all packages installed. Return details for a given array of packages. The attributes returned should be the installed version, name and package description. Add Comment
Jira (PDB-3857) Error during garbage collection: java.sql.BatchUpdateException
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3857 Error during garbage collection: java.sql.BatchUpdateException Change By: Jeff Yarnell Team: Data Platform Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8498) No title provided and "foo" is not a valid resource reference
Title: Message Title
Gavin Williams created an issue
Puppet / PUP-8498
No title provided and "foo" is not a valid resource reference
Issue Type:
Improvement
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Components:
AIO
Created:
2018/02/28 8:43 AM
Priority:
Normal
Reporter:
Gavin Williams
Puppet Version: 5.3.3 Puppet Server Version: N/A Upon creating some rspec-puppet tests for a new Puppet module, the following error was encountered:
1) actora on centos-7-x86_64 with defaults should compile into a catalogue without dependency cycles
Failure/Error: it { should compile }
error during compilation: No title provided and "actora" is not a valid resource reference on node lt0772.local
As there was no traceback to a specific file/line provided, this one proved
Jira (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3856 PQL specifying both type and title for class makes pql not find existing class Change By: Jeff Yarnell Team: Data Platform Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-345) Bolt should provide a better summary of failures
Title: Message Title Lucy Wyman commented on BOLT-345 Re: Bolt should provide a better summary of failures Michael Smith only nit: "Use (red) error highlighting for "Failed on ...". isn't showing up for me? It's still just white. I think this is fine since it's red in the rest of the output, and is a little hard to miss since it's right on top of my prompt. But others may care? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1810) 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata
Title: Message Title Demian commented on FACT-1810 Re: 60 second timeout in facter when connecting to 169.254.169.254 for ec2 metadata It would be great if you could create a release because there is none after the merge of this PR. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (RRAL-1) Manage packages with the remote RAL
Title: Message Title Davin Hanlon updated an issue Remote Resource Abstract Layer / RRAL-1 Manage packages with the remote RAL Change By: Davin Hanlon Epic will detail the requirements for package management with the remote RAL. It will be required to perform package management where there is no Puppet agent installed. The following package managers should be supported initially, others will be added over time. * apt * rpm * chocolatey (windows) * yumThe remote RAL should be able to determine the package manager to use based on what's available on the target. The remote RAL should be able to get package information from log in to the remote target, get package information, and also to perform actions (set) on packages on the remote target. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (RRAL-1) Manage packages with the remote RAL
Title: Message Title Davin Hanlon created an issue Remote Resource Abstract Layer / RRAL-1 Manage packages with the remote RAL Issue Type: Epic Assignee: Unassigned Created: 2018/02/28 6:52 AM Priority: Normal Reporter: Davin Hanlon Epic will detail the requirements for package management with the remote RAL. It will be required to perform package management where there is no Puppet agent installed. The following package managers should be supported initially, others will be added over time. apt rpm chocolatey (windows) yum The remote RAL should be able to determine the package manager to use based on what's available on the target. The remote RAL should be able to get package information from the remote target, and also to perform actions (set) on packages on the remote target. Add Comment
Jira (PDB-3852) PuppetDB query nodes based on fact broken
Title: Message Title Geoff Nichols updated an issue PuppetDB / PDB-3852 PuppetDB query nodes based on fact broken Change By: Geoff Nichols Team: Data Platform Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1825) Update facter with any changes to facilitate the cfacter gem
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1825 Update facter with any changes to facilitate the cfacter gem Change By: Geoff Nichols Sprint: Platform Core KANBAN OS Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6759) systemd provider does not understand "indirect" status / tries to turn off service on each run
Title: Message Title Fabien Wernli commented on PUP-6759 Re: systemd provider does not understand "indirect" status / tries to turn off service on each run We have the same problem with rpcbind: is-enabled returns 'indirect', and puppet thinks it's not enabled. But we actually need it enabled+running, so in our case, `indirect` should probably return true? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
