Jira (PDB-2633) PQL & Hashes: Provide new path matching for hashes in AST & PQL
Title: Message Title
Wyatt Alt commented on PDB-2633
Re: PQL & Hashes: Provide new path matching for hashes in AST & PQL
Molly Waggett as just discussed, I think a loose picture of the touchpoints here would be:
investigate whether there's any reason not to change the resource_params_cache column to jsonb as well. My guess is the only thing it buys us today is the ability to do a regex match against parameters. It looks to me like this can be done on jsonb by using the ? operator instead of ~, e.g
puppetdb=# select '{"a":"b"}'::jsonb ? 'a';
?column?
──
t
(1 row)
once resource_params_cache is converted, start working on parsing those dotted paths and forming the json structure to compare against. This will probably involve creation of a new defrecord in engine.clj (JsonContainmentExpression or whatever) that will have a corresponding function in storage_utils.clj that takes a column and value returns the honeysql formatted string "mycolumn @> myvalue". In practice myvalue will be "?" when this gets called, so parameterizing it on value probably isn't strictly necessary.
You will want to trace BinaryExpression through engine.clj and update
Jira (FACT-1451) Update ubuntu kernel version fact regex in facter acceptance tests
Title: Message Title William Hopper updated an issue Facter / FACT-1451 Update ubuntu kernel version fact regex in facter acceptance tests Change By: William Hopper Issue Type: Bug CI Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1451) Update ubuntu kernel version fact regex in facter acceptance tests
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-1451 Update ubuntu kernel version fact regex in facter acceptance tests Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1451) Update ubuntu kernel version fact regex in facter acceptance tests
Title: Message Title William Hopper updated an issue Facter / FACT-1451 Update ubuntu kernel version fact regex in facter acceptance tests Change By: William Hopper Scope Change Category: Found Scope Change Reason: CI blocker for integration team Story Points: 1 Sprint: Client 2016-07-13 (HA, 1.5.3) Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (FACT-1451) Update ubuntu kernel version fact regex in facter acceptance tests
Title: Message Title Britt Gresham created an issue Facter / FACT-1451 Update ubuntu kernel version fact regex in facter acceptance tests Issue Type: Bug Assignee: Unassigned Created: 2016/07/01 3:43 PM Priority: Normal Reporter: Britt Gresham Currently the stable branch is failing because the kernel versions are no longer matching what we are expecting in facter's acceptance tests. Failing job: https://jenkins.puppetlabs.com/view/puppet-agent%20suite%20pipelines/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-stable/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6468) Move PE acceptance tests to puppet core
Title: Message Title John Duarte created an issue Puppet / PUP-6468 Move PE acceptance tests to puppet core Issue Type: Task Assignee: John Duarte Created: 2016/07/01 2:41 PM Priority: Normal Reporter: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-5921) Deprecate source_permissions
Title: Message Title Andrew Henroid assigned an issue to Unassigned Puppet / PUP-5921 Deprecate source_permissions Change By: Andrew Henroid Assignee: Andrew Henroid Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2785) spec tests failing against puppet master
Title: Message Title
Wyatt Alt updated an issue
PuppetDB / PDB-2785
spec tests failing against puppet master
Change By:
Wyatt Alt
see:https://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_mergely-master/244/ Here's the current error:{code}02:38:18 Failures:02:38:18 02:38:18 1) Puppet::Reports::Puppetdb#report_to_hash should include noop_pending or nil02:38:18 Failure/Error: subject["noop_pending"] = false02:38:18 02:38:18 NoMethodError:02:38:18undefined method `[]=' for #02:38:18 # ./spec/unit/reports/puppetdb_spec.rb:109:in `block (3 levels) in '02:38:18 02:38:18 Finished in 5.23 seconds (files took 1.94 seconds to load)02:38:18 176 examples, 1 failure{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-2785) spec tests failing against puppet master
Title: Message Title Wyatt Alt commented on PDB-2785 Re: spec tests failing against puppet master The tests are still failing against master puppet. Trying to reproduce it locally with ruby 2.2 I see this: [~/Documents/puppetdb/puppet] (master) $ rspec /Users/wyatt/Documents/puppetdb/puppet/lib/puppet/face/node/deactivate.rb:6: warning: already initialized constant CommandDeactivateNode /Users/wyatt/Documents/puppetdb/puppet/spec/unit/indirector/node/puppetdb_spec.rb:11: warning: previous definition of CommandDeactivateNode was here FFF. Failures: 1) Puppet::Util::Puppetdb::Config#load with a config file should fail if given an invalid hostname Failure/Error:
Jira (PDB-2528) Expose PQL Parser in HTTP Endpoint
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2528 Expose PQL Parser in HTTP Endpoint Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2649) Puppet::Parser::Compiler failed with error NoMethodError: undefined method `downcase' for :undef:Symbol
Title: Message Title Ryan Senior commented on PDB-2649 Re: Puppet::Parser::Compiler failed with error NoMethodError: undefined method `downcase' for :undef:Symbol What should we do with/about this Kenneth Barber? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-773) Add primary keys to 'edges' and 'resource_events'
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-773 Add primary keys to 'edges' and 'resource_events' Change By: Ryan Senior Sprint: Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1406) Big values become negativ
Title: Message Title Andrew Henroid updated an issue Facter / FACT-1406 Big values become negativ Change By: Andrew Henroid Story Points: 1 Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1406) Big values become negativ
Title: Message Title Andrew Henroid updated an issue Facter / FACT-1406 Big values become negativ Change By: Andrew Henroid Scope Change Category: Adopted Scope Change Reason: onboarding Sprint: Client 2016-07-13 (HA, 1.5.3) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1406) Big values become negativ
Title: Message Title Andrew Henroid assigned an issue to Andrew Henroid Facter / FACT-1406 Big values become negativ Change By: Andrew Henroid Assignee: Andrew Henroid Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1450) Test failure on the Ubuntus
Title: Message Title Rob Braden created an issue Facter / FACT-1450 Test failure on the Ubuntus Issue Type: CI Blocker Assignee: Unassigned Created: 2016/07/01 11:12 AM Priority: Blocker Reporter: Rob Braden https://jenkins.puppetlabs.com/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-master/140/ After some of the Ubuntu templates were updated, facter tests are failing: 12.04: 08:26:30 Test Case tests/facts/ubuntu.rb reported: # 14.04: 08:28:29 Test Case tests/facts/ubuntu.rb reported: #
Jira (PUP-5626) missing the dependencies key in metadata.json breaks puppet module
Title: Message Title
Ben Ford updated an issue
Puppet / PUP-5626
missing the dependencies key in metadata.json breaks puppet module
Change By:
Ben Ford
NOTE:1 The {{metadata . Here's a quickfix PR json}} file in the module https://github.com/puppetlabs/puppetlabs- {{ pe_inifile /pull/4/files2. Needs }} was missing a permanent fix in PMT. Reassign to forge team for an evaluation.---An empty dependencies array in {{ pe_inifile dependencies }} has apparently key. This rendered puppet module tool , and by inoperable. By extension any spec tests that use forge modules , inoperable also break . It's worth noting that the modules in this example are not dependent on each other in any way. {code} [696:2.0.0 root @ rspec- master:~ # puppet |pltraining-classroom/remove_teams]pltraining-classroom $ puppet module install puppetlabs/firewall --modulepath spec/fixtures/modules/ list Notice Error : Preparing to install into /Volumes/Projects/pltraining-classroom/spec/fixtures/modules ... No dependencies module metadata provided for pe_inifile Error: No dependencies module metadata provided for pe_inifileError: Try 'puppet help module install list ' for usage [697:2.0.0@rspec-puppet|pltraining-classroom/remove_teams]pltraining-classroom $ rm -rf spec/fixtures/modules/pe_inifile/[698:2.0.0@rspec-puppet|pltraining-classroom/remove_teams]pltraining-classroom $ puppet module install puppetlabs/firewall --modulepath spec/fixtures/modules/Notice: Preparing to install into /Volumes/Projects/pltraining-classroom/spec/fixtures/modules ...Notice: Downloading from https://forgeapi.puppetlabs.com ...Notice: Installing -- do not interrupt .../Volumes/Projects/pltraining-classroom/spec/fixtures/modules└── puppetlabs-firewall (v1.7.2) {code}Adding {{"dependencies": []}} to {{pe_inifile/metadata.json}} made it work. UPDATE: The module has now been corrected, but PMT should handle that case better.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-5626) missing the dependencies key in metadata.json breaks puppet module
Title: Message Title Ben Ford updated an issue Puppet / PUP-5626 missing the dependencies key in metadata.json breaks puppet module Change By: Ben Ford Summary: empty missing the dependencies key in a module break metadata.json breaks puppet module tool for unrelated modules Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1134) Service Provider 'init' does not detect correct location for script directory on AIX - Patch included
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-1134 Service Provider 'init' does not detect correct location for script directory on AIX - Patch included Change By: Maggie Dreyer Scope Change Category: Adopted Scope Change Reason: onboarding Story Points: 2 Sprint: Client 2016-07-13 (HA, 1.5.3) Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups
Jira (PUP-1134) Service Provider 'init' does not detect correct location for script directory on AIX - Patch included
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-1134 Service Provider 'init' does not detect correct location for script directory on AIX - Patch included Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Glenn Sarti assigned an issue to Daniel Lu Puppet / PUP-6467 Fix Parallel Spec grouping for RSpec 3.5.0 Change By: Glenn Sarti Assignee: Glenn Sarti Daniel Lu Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-6467 Fix Parallel Spec grouping for RSpec 3.5.0 Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-6467 Fix Parallel Spec grouping for RSpec 3.5.0 Change By: Glenn Sarti Scope Change Category: Found Scope Change Reason: Daniel had time to fix it during the sprint. Story Points: 2 Sprint: Windows 2016-07-13 - Choco Un Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from
Jira (PUP-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Glenn Sarti commented on PUP-6467 Re: Fix Parallel Spec grouping for RSpec 3.5.0 Suspect that it's somewhere here.. https://github.com/puppetlabs/puppet/blob/master/util/rspec_grouper#L20-L25 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Glenn Sarti commented on PUP-6467 Re: Fix Parallel Spec grouping for RSpec 3.5.0 Should target stable Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6467) Fix Parallel Spec grouping for RSpec 3.5.0
Title: Message Title Glenn Sarti created an issue Puppet / PUP-6467 Fix Parallel Spec grouping for RSpec 3.5.0 Issue Type: Bug Assignee: Unassigned Created: 2016/07/01 10:23 AM Priority: Normal Reporter: Glenn Sarti It was discovered in PUP-6466 that the Parallel Spec code is not compatible with RSpec 3.5.0. This ticket will cover fixing Puppet parallel spec tests to work with both RSPec 3.5.0 and prior to (3.4.x and below) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6384) Acceptance: test that agent failover behavior works correctly
Title: Message Title Maggie Dreyer commented on PUP-6384 Re: Acceptance: test that agent failover behavior works correctly Most of the actual failover functionality is covered by the acceptance tests for the report (see PUP-6378), so for this ticket we really only need to cover the warnings and priority for the conflicting server settings. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6398) Executing parallel specs on Windows is not reliable
Title: Message Title Glenn Sarti commented on PUP-6398 Re: Executing parallel specs on Windows is not reliable PR as failing Travis due to PUP-6466 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Jane Lu updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Jane Lu Sub-team: emerald Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Jane Lu updated an issue Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Jane Lu Sprint: Server Emerald 2016-07-13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-341) Hiera should support native HOCON to match Puppet Server
Title: Message Title Jane Lu assigned an issue to Jane Lu Hiera / HI-341 Hiera should support native HOCON to match Puppet Server Change By: Jane Lu Assignee: Jane Lu Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6437) directoryservice user provider crashes if no ShadowHashData is found
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6437 directoryservice user provider crashes if no ShadowHashData is found Change By: John Duarte Assignee: qa John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6398) Executing parallel specs on Windows is not reliable
Title: Message Title Craig Gomes assigned an issue to Daniel Lu Puppet / PUP-6398 Executing parallel specs on Windows is not reliable Change By: Craig Gomes Assignee: Daniel Lu Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6384) Acceptance: test that agent failover behavior works correctly
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-6384 Acceptance: test that agent failover behavior works correctly Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6465) Catalog evaltrace should log resource number and totals
Title: Message Title Dominic Cleal commented on PUP-6465 Re: Catalog evaltrace should log resource number and totals I'd expect the total to perhaps be updated as the run continues, so if resources are added then the total reflects the change. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6465) Catalog evaltrace should log resource number and totals
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6465 Catalog evaltrace should log resource number and totals Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6465) Catalog evaltrace should log resource number and totals
Title: Message Title Henrik Lindberg commented on PUP-6465 Re: Catalog evaltrace should log resource number and totals Not sure if that is possible as there are resources generated during the run. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6465) Catalog evaltrace should log resource number and totals
Title: Message Title Dominic Cleal created an issue Puppet / PUP-6465 Catalog evaltrace should log resource number and totals Issue Type: Improvement Assignee: Unassigned Created: 2016/07/01 7:29 AM Priority: Normal Reporter: Dominic Cleal The --evaltrace apply/agent option is valuable for showing which resource in the catalog is currently being evaluated, but it would be useful if the log messages showed the progress through the current catalog, e.g. resource 10 of 42. This would give an overall progress indication of the run. As an example, with a single notify resource plus the standard resources generated in the catalog, I'd expect output similar to: Info: Class[Main]: Starting to evaluate the resource (1 of 10) Info: Class[Main]: Evaluated in 0.00 seconds Info: /Stage[main]/Main/Notify[test]: Starting to evaluate the resource (2 of 10)
Jira (PUP-6464) Cannot find templates in modules with hyphen in module name
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6464 Cannot find templates in modules with hyphen in module name Change By: Henrik Lindberg Summary: Template search behavior changed from v3 to v4 Cannot find templates in modules with hyphen in module name Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6464) Template search behavior changed from v3 to v4
Title: Message Title Henrik Lindberg commented on PUP-6464 Re: Template search behavior changed from v3 to v4 The change regarding hyphens is that "names cannot contain hyphens, irrespective of what they identify (modules, classes, variables, defines, etc.)". Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Thomas Hallgren commented on PUP-4742 Re: Bring semantic_puppet library into Puppet Any news on this? It's been sitting there for three weeks now and it is blocking other work. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Thomas Hallgren commented on PUP-6463 Re: Accessing a required parameter that is unassigned causes bad error message Merged to master at 7376c6e. This merge also contained changes from PUP-6390 which is unrelated to this jira. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6464) Template search behavior changed from v3 to v4
Title: Message Title R.I.Pienaar commented on PUP-6464 Re: Template search behavior changed from v3 to v4 Doc you linked to sends you to https://docs.puppet.com/puppet/latest/reference/upgrade_major_pre.html which links to a many lists of deprecated things and all the warnings you're likely to get etc. But given how massive the change set is there really is no hope for every little case to be listed. You can open a documentation bug I think as it doesnt seem to specifically call out that a module cant have a "-" in it's name, but if a class cant then its kind of obvious a module cant have either. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Thomas Hallgren commented on PUP-6463 Re: Accessing a required parameter that is unassigned causes bad error message Merged to stable at fd15bfd. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6464) Template search behavior changed from v3 to v4
Title: Message Title Brian Sipos commented on PUP-6464 Re: Template search behavior changed from v3 to v4 I understand, I had been using puppet 3.8.4 which is standard in CentOS 7 and I was not seeing any such deprecation warnings, so that did not help my confusion. As you have mentioned "the changelog", I think part of my problem was that my cursory search for 3->4 migration came up with the page I linked to, some various blog articles, but I did not come upon an official 'changelog' page for 3->4 or for 4.0 or however it would be stated. If there is such a thing, then can that document be linked-to from the upgrade guidelines? My frustration was really not being able to find "the official list" wherever that may be. This ticket can be closed, as my issue was my own misunderstanding. Hopefully this may be indexed as a help to anyone else who wound up in my same situation. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6464) Template search behavior changed from v3 to v4
Title: Message Title R.I.Pienaar commented on PUP-6464 Re: Template search behavior changed from v3 to v4 Glad that sorted it out - the guide you linked though is a outline of steps, the changelog for 3->4 is absolutely immense and there would be no point in trying to point out 1 or 2 issues since there are so many breaking changes However I believe puppet 3.latest would have given you a warning about this being deprecated to prepare you for 4..the pre steps in the guide you linked covers how to do that. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6464) Template search behavior changed from v3 to v4
Title: Message Title
Brian Sipos commented on PUP-6464
Re: Template search behavior changed from v3 to v4
Sorry to forget the actual error itself, from the agent side the error appears as:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, Could not find template 'local-data/app/file.erb' at /etc/puppetlabs/code/environments/production/manifests/site.pp:599:16 on node {snip}
I read about dash being unavailable for class names, but I guess I did not realize also not available for module names. I did try to correct this and was able to successfully run puppet v4 on my test host. I suppose that this is more of a "get the message out" issue that I did not realize this change in module name restriction. Could the official docs at https://docs.puppet.com/puppet/latest/reference/upgrade_major_server.html be updated to somehow add a step to "Check all module names and class names conform to naming requirements described at ..." ?
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6463 Accessing a required parameter that is unassigned causes bad error message Change By: Thomas Hallgren Scope Change Category: Found Scope Change Reason: Empty TODO list Sprint: Language Triage 2016-07-13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-6464) Template search behavior changed from v3 to v4
Title: Message Title R.I.Pienaar commented on PUP-6464 Re: Template search behavior changed from v3 to v4 How is it not working? What happens? One thing to note modules cannot have a "-" in their name. Might be that. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
