Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8566  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "puppet config print" needs --quiet option to disable new (default) verbosity   
 

  
 
 
 
 

 
 Daniel Parks this will be in the 5.5.1 release out due out in mid-April.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8566  
 
 
  "puppet config print" needs --quiet option to disable new (default) verbosity   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Priority: 
 Minor Normal  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-397) Rspec puppet for plans

2018-03-26 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-397  
 
 
  Rspec puppet for plans   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 It's hard to write unit tests for plans now. We should add support to rspec-puppet for the testing plans.Requirements:Ability to run a plan with specified parameters and make an assertion about the resultAbility to mock run_task callsAbility to make assertions around run_task callsLater scope: Merge into rspec puppet Ability to mock run_command, run_script and file_upload callsAbility to mock run_plan calls.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit 

Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity

2018-03-26 Thread Daniel Parks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Parks commented on  PUP-8566  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "puppet config print" needs --quiet option to disable new (default) verbosity   
 

  
 
 
 
 

 
 Sorry for the edit and the extra comment: could we bump the priority on this? It's really irritating.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity

2018-03-26 Thread Daniel Parks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Parks commented on  PUP-8566  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "puppet config print" needs --quiet option to disable new (default) verbosity   
 

  
 
 
 
 

 
 In the case where -section is specified: please make the default behavior to not output this, even when in verbose mode. With -section specified it adds no useful information. This extra output is a particular problem in cron jobs, since the standard behavior is to generate an email when there is output. My jobs are only supposed to output on failure, so this means that failures will be lost in the noise. (Fortunately these emails are not coming into my inbox.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?

2018-03-26 Thread Eric Sorenson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 No, I specifically excluded the vendored puppet implementations, the paths show only types and providers inside of modules. But I totally agree - I'm less concerned with keeping the implementation intact than keeping the method signature intact, which is what it looked like this ticket was doing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8592) `puppet config --section main print` writes section info to stderr

2018-03-26 Thread Daniel Parks (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Parks commented on  PUP-8592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: `puppet config --section main print` writes section info to stderr   
 

  
 
 
 
 

 
 I'm running into this in a number of places. For example, I have a script that runs in cron that now is generating mail because of this (cron only sends email if a job generates output).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?

2018-03-26 Thread Ethan Brown (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Brown commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 Eric Sorenson at the very least I think it would be useful to have the Puppet method shadow / defer to the internal Ruby method instead of implementing the code itself. I'm less concerned about the timeline around deprecation and more concerned with replacing the Puppet implementation with a correct one. Without any data to back it up, my gut says that external consumers are likely consuming the Puppet API correctly, and there probably isn't a ton of value in disrupting content authors. FWIW - given I've run similar searches before, I also suspect your search is still returning a number of modules that have chosen to vendor Puppet itself, which falsely inflates the real module count (even with the gem and vendor dirs ignored). The greater concern is the internal Puppet consumers are relying on accidental behavior, and I suspect there are a number of internal defects hiding or errantly passing for the wrong reasons.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version

2018-03-26 Thread Christopher Wood (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Wood commented on  PUP-6518  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet resource package kernel reports the wrong rpm version   
 

  
 
 
 
 

 
 I think if you want a report of all installed package versions, you're probably better off with a fact which does "rpm -qa" under the hood. (Or Puppet Discovery, these days?) Trying to ponder why some rpms get to have multiple base names is the path to insanity.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace

2018-03-26 Thread Eric Sorenson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-4242  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warnings for manifests declaring things in wrong namespace   
 

  
 
 
 
 

 
 Can this just be made to fail when --strict is on?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?

2018-03-26 Thread Eric Sorenson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 What does it hurt to leave this? I ask because unlike many of the deprecations in this epic, this one affects a large number of types and providers in the wild. A search through the forge corpus turned up:   
 
 
 
 
 ag --ignore spec --ignore stdlib --ignore vendor --ignore gem 'absolute_path\?' *  -l | wc -l  
 
 
 53
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more 

Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version

2018-03-26 Thread Verne Lindner (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Verne Lindner commented on  PUP-6518  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet resource package kernel reports the wrong rpm version   
 

  
 
 
 
 

 
 Eric Sorenson Seeing this ticket now, since it's linked to open ticket ENTERPRISE-1150. Not sure that I understand your last comment, but there is a use case for reporting all package versions on a system, which is for vulnerability reporting/remediation. Are kernel packages an exception? We've been thinking and talking in terms of application packages, so I don't know if kernel packages are treated differently?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-361) Gather facts from puppetdb

2018-03-26 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-361  
 
 
  Gather facts from puppetdb   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 Michael Smith  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-361) Gather facts from puppetdb

2018-03-26 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-361  
 
 
  Gather facts from puppetdb   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 Michael Smith Lucy Wyman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-361) Gather facts from puppetdb

2018-03-26 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Michael Smith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-361  
 
 
  Gather facts from puppetdb   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 Lucy Wyman Michael Smith  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity

2018-03-26 Thread Eric Sorenson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8566  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "puppet config print" needs --quiet option to disable new (default) verbosity   
 

  
 
 
 
 

 
 IMO we should make this output only show up when you specify -verbose or -debug ; this preserves the previous behaviour but makes it easy to troubleshoot if you are getting results you don't expect.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8468) Failed to show puppet classes: 500 Api Request

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Henrik Lindberg  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8468  
 
 
  Failed to show puppet classes: 500 Api Request   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Henrik Lindberg  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7584) Remove deprecated execfail method from util/execution

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7584  
 
 
  Remove deprecated execfail method from util/execution   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 Remove the execfail method from {{lib/puppet/util/execution.rb}} as its deprecated. Need to see if this method ever worked, based on comments in https://github.com/puppetlabs/puppet/commit/bf3d94cc50a941d5e4d413568dbf611e95848eb9, it may not have ever worked.None of the modules on the forge are calling the method (except for ones that have vendored puppet).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7115) Un-vendor semantic_puppet gem for Puppet 6

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7115  
 
 
  Un-vendor semantic_puppet gem for Puppet 6   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Acceptance Criteria: 
 Add hard gem dependency on the external semantic_puppet gem. We should require "~> 1.0" accept at least 1.0 or greater and less than 2.0.The gem dependency needs to be updated in 3 places: .gemspec, Gemfile and ext/project_data.yaml.Delete lib/puppet/vendor/load_semantic_puppet.rb and lib/puppet/vendor/semantic_puppet/If you build a puppet gem (bundle exec rake package:implode package:bootstrap and bundle exec rake package:gem), then you should be able install each version (there will be 4 platforms) on a clean VM and it should install the semantic_puppet gem 1.0.x as an external dependency.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7157) Remove 'semantic' shim in Puppet 6

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7157  
 
 
  Remove 'semantic' shim in Puppet 6   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Acceptance Criteria: 
 - "semantic" shim added in PUP-7156 is removed  (lib/puppet/vendor/load_semantic.rb and lib/puppet/vendor/semantic). - Make sure a newly generated module from the pdk or garethr's puppet-module-skeleton does not have the same issue described in PUP-7156.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1841) Facter does not like rto_min in ip route output

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1841  
 
 
  Facter does not like rto_min in ip route output   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Team: 
 Platform OS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1841) Facter does not like rto_min in ip route output

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1841  
 
 
  Facter does not like rto_min in ip route output   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Labels: 
 linux networking  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?

2018-03-26 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle commented on  PUP-7407  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add deprecation warning to Puppet::Util.absolute_path?   
 

  
 
 
 
 

 
 Is this on the table for Puppet 6?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8558) Remove ability to enable non-strict mode in PMT

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8558  
 
 
  Remove ability to enable non-strict mode in PMT   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Acceptance Criteria: 
 * The strict-semver option should be removed in help, man pages, etc , e . g. puppet module install* All of the module APIs for parsing version strings should no longer accept an optional {{strict_semver}} argument, e.g. "def self.parse_module_dependency(where, dep)"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8607) With certificate revocation set to false, why puppet still checks for crl? Error: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=er

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8607  
 
 
  With certificate revocation set to false, why puppet still checks for crl? Error: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=error: certificate verify failed   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Key: 
 PA PUP - 1947 8607  
 
 
Project: 
 Puppet  Agent  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6585) Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)

2018-03-26 Thread Ethan Brown (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6585  
 
 
  Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)   
 

  
 
 
 
 

 
Change By: 
 Ethan Brown  
 
 
Sprint: 
 Windows Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6585) Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)

2018-03-26 Thread Ethan Brown (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6585  
 
 
  Remove internal usage of Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)   
 

  
 
 
 
 

 
Change By: 
 Ethan Brown  
 
 
Team: 
 Platform Core Windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6184) Remove win32-dir code usage from Puppet

2018-03-26 Thread Ethan Brown (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6184  
 
 
  Remove win32-dir code usage from Puppet   
 

  
 
 
 
 

 
Change By: 
 Ethan Brown  
 
 
Team: 
 Platform Core Windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6184) Remove win32-dir code usage from Puppet

2018-03-26 Thread Ethan Brown (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Brown updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6184  
 
 
  Remove win32-dir code usage from Puppet   
 

  
 
 
 
 

 
Change By: 
 Ethan Brown  
 
 
Sprint: 
 Windows Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8553) PAL should be able to run with 'empty' puppet settings

2018-03-26 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  PUP-8553  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PAL should be able to run with 'empty' puppet settings   
 

  
 
 
 
 

 
 I think giving PAL more control of setting would be useful but the PAL users shouldn't have to worry about what the settings are and how to use PAL without accidentally creating a bunch of settings configured directories on disk that don't make much sense outside of an agent run. The most important feature for PAL imo is simply making it easy to run with 'empty' settings. Hopefully the API for that can be fixed without untangling the entire settings mess.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7534) Deprecate using file checksums in `content` property

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Melissa Stone  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7534  
 
 
  Deprecate using file checksums in `content` property   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Jennifer Solman Melissa Stone  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7931) Support HTTPS Compression on report upload

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7931  
 
 
  Support HTTPS Compression on report upload   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 5.5.1  
 
 
Fix Version/s: 
 PUP 6.0.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8592) `puppet config --section main print` writes section info to stderr

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8592  
 
 
  `puppet config --section main print` writes section info to stderr   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Platform Core Hopper  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8592) `puppet config --section main print` writes section info to stderr

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8592  
 
 
  `puppet config --section main print` writes section info to stderr   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Platform Core Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8592) `puppet config --section main print` writes section info to stderr

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8592  
 
 
  `puppet config --section main print` writes section info to stderr   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Platform Core Hopper  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8592) `puppet config --section main print` writes section info to stderr

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8592  
 
 
  `puppet config --section main print` writes section info to stderr   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Platform Core  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8592) `puppet config --section main print` writes section info to stderr

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: `puppet config --section main print` writes section info to stderr   
 

  
 
 
 
 

 
 Based on the thread in https://tickets.puppetlabs.com/browse/PUP-2868?focusedCommentId=515996=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-515996, we decided to always emit which section and environment puppet config operates on. But it sounds like it's too much information... see also PUP-8566.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1545) Exit code is always 0

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1545  
 
 
  Exit code is always 0   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Fix Version/s: 
 FACT 4.0.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1814) Mountpoints Fact available space does not accurately reflect disk usage

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1814  
 
 
  Mountpoints Fact available space does not accurately reflect disk usage   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Fix Version/s: 
 FACT 4.0.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-365) Missing period in "E.g." in usage text

2018-03-26 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti commented on  BOLT-365  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing period in "E.g." in usage text   
 

  
 
 
 
 

 
 Reviewed content on GitHub. Looks good to go.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDOC-180) puppet-strings Tasks support

2018-03-26 Thread Joel Allen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joel Allen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-180  
 
 
  puppet-strings Tasks support   
 

  
 
 
 
 

 
Change By: 
 Joel Allen  
 
 
Epic Status: 
 To Do Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1628) Set of breaking changes staged for facter 4

2018-03-26 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1628  
 
 
  Set of breaking changes staged for facter 4   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Fix Version/s: 
 FACT 4.0.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3884) Improve default logging configuration for PuppetDB

2018-03-26 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3884  
 
 
  Improve default logging configuration for PuppetDB   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/03/26 12:20 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Charlie Sharpsteen  
 

  
 
 
 
 

 
 The default logback configuration bundled with the puppetdb and pe-puppetdb packages can be improved by: 
 
Updating the configuration to no longer require a service restart or reload in order for changes to be picked up (TK-426). 
 
 
Formatting timestamps in application logs to include the time zone in order to enable debugging of geographically distributed installations (PE-13490). 
 These changes will allow DEBUG logging to be enabled without requiring a restart or reload that may destroy application state and improve the usefulness of log data from installations that span multiple time zones. Recommendations: 
 
Logback configuration should include scanPeriod="60 seconds" to allow log levels and other settings to be adjusted without requiring service restarts or reloads. 
 
 
Logback patterns for application logs should use a RFC 3339 compatible representation that includes the Time Zone. A Java SimpleDateFormat that works with logback is: 
  
 
 
 
 
   

Jira (PDB-3884) Improve default logging configuration for PuppetDB

2018-03-26 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3884  
 
 
  Improve default logging configuration for PuppetDB   
 

  
 
 
 
 

 
Change By: 
 Charlie Sharpsteen  
 
 
Issue Type: 
 Bug Improvement  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-395) Improve task-writing documentation

2018-03-26 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti commented on  BOLT-395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve task-writing documentation   
 

  
 
 
 
 

 
 Found content from the Tasks topics draft and added to help: Returning errors in plans http://docs-preview.webteam.puppet.com/docs/bolt/dev/writing_plans.html#ariaid-title6 Returning errors in tasks http://docs-preview.webteam.puppet.com/docs/bolt/dev/writing_tasks.html#ariaid-title5 Original Google Doc https://docs.google.com/document/d/16_d8KUY4fl77nqtC1fvYG0qIP1ZXcsTtLBvlP9QtcYw/edit  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8538) AIX user resource fails with new service packs

2018-03-26 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols commented on  PUP-8538  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AIX user resource fails with new service packs   
 

  
 
 
 
 

 
 Merged to puppet#4.10.x at https://github.com/puppetlabs/puppet/commit/373377d1c4ca52e5fbe8a7f684d1d394128cd924.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8538) AIX user resource fails with new service packs

2018-03-26 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8538  
 
 
  AIX user resource fails with new service packs   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Assignee: 
 Casey Williams  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8583) Fix JrJackson serialization of numbers so we can use it

2018-03-26 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8583  
 
 
  Fix JrJackson serialization of numbers so we can use it   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6344) metrics.time.total does not correlate to time reported in log

2018-03-26 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland assigned an issue to Kris Bosland  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6344  
 
 
  metrics.time.total does not correlate to time reported in log   
 

  
 
 
 
 

 
Change By: 
 Kris Bosland  
 
 
Assignee: 
 Melissa Stone Kris Bosland  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8562) File performance nearly twice as slow after update

2018-03-26 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone assigned an issue to Melissa Stone  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8562  
 
 
  File performance nearly twice as slow after update   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Assignee: 
 Kris Bosland Melissa Stone  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8562) File performance nearly twice as slow after update

2018-03-26 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland assigned an issue to Kris Bosland  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8562  
 
 
  File performance nearly twice as slow after update   
 

  
 
 
 
 

 
Change By: 
 Kris Bosland  
 
 
Assignee: 
 Melissa Stone Kris Bosland  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8592) `puppet config --section main print` writes section info to stderr

2018-03-26 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen commented on  PUP-8592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: `puppet config --section main print` writes section info to stderr   
 

  
 
 
 
 

 
 Yup, seems like this should be DEBUG level info if we already print a warning when --section isn't used.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-414) Run a task with different parameters per target

2018-03-26 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-414  
 
 
  Run a task with different parameters per target   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/03/26 10:39 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Alex Dreyer  
 

  
 
 
 
 

 
 Sometimes a task needs slightly different parameters on different targets. It can be slow to accomplish this with separate calls to run task and breaks what should be a single logical step into multiple. Use cases: A package task where the package has a different name on different targets A task that checks or updates ha proxy which may be using a different socket path on different targets.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

Jira (PUP-8538) AIX user resource fails with new service packs

2018-03-26 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols assigned an issue to Casey Williams  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8538  
 
 
  AIX user resource fails with new service packs   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Assignee: 
 Branan Riley Casey Williams  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1768) libwhereami uses deprecated syntax

2018-03-26 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols assigned an issue to Casey Williams  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1768  
 
 
  libwhereami uses deprecated syntax
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Assignee: 
 Branan Riley Casey Williams  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1768) libwhereami uses deprecated syntax

2018-03-26 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols commented on  FACT-1768  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: libwhereami uses deprecated syntax
 

  
 
 
 
 

 
 Merged to libwhereami#0.1.x at https://github.com/puppetlabs/libwhereami/commit/91e5d2aa97cd20f7d62d9f833ee2fc7d98bec1c1.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8562) File performance nearly twice as slow after update

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8562  
 
 
  File performance nearly twice as slow after update   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 5.5.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8590) puppet device --apply does not support pcore

2018-03-26 Thread Rick Sherman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Sherman commented on  PUP-8590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet device --apply does not support pcore   
 

  
 
 
 
 

 
 This was due to facts using symbols vs strings:    
 
 
 
 
 -facts[:osfamily] = 'cisco-ios-xe'  
 
 
 -facts[:os][:family] = 'cisco-ios-xe'  
 
 
 -facts[:operatingsystem] = 'IOS-XE'  
 
 
 -facts[:os][:name] = 'IOS-XE'  
 
 
 +facts['osfamily'] = 'cisco-ios-xe'  
 
 
 +facts['os']['family'] = 'cisco-ios-xe'  
 
 
 +facts['operatingsystem'] = 'IOS-XE'  
 
 
 +facts['os']['name'] = 'IOS-XE'  
 
 
 
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

Jira (FACT-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley commented on  FACT-1597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX   
 

  
 
 
 
 

 
 The fix I've implemented mostly improves our error checking so we don't try to report on devices which are missing from /dev, or devices which return an error when we attempt to collect their size information. I'm hopeful this will clean up all the bogus warnings, but I can't know for sure until the build goes out. If customers are still seeing this after the next release goes out to them, we can address what's particular about those cases in more detail  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1597  
 
 
  "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Release Notes Summary: 
 Facter now properly checks for errors when gathering disk information on AIX, so it should no longer warn or report bogus results for devices assigned to special uses such as databases.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-375) Add Bolt release tickets to winston

2018-03-26 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-375  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add Bolt release tickets to winston   
 

  
 
 
 
 

 
 I believe this is done.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1597  
 
 
  "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1597  
 
 
  "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Fix Version/s: 
 FACT 3.6.10  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8535) Backport ruby warning rake task

2018-03-26 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig commented on  PUP-8535  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Backport ruby warning rake task   
 

  
 
 
 
 

 
 Josh Cooper, the biggest problem with back-porting that rake task is that it's going to start failing CI runs, because of all of the existing issues in files on the older branches, whenever anyone changes anything. It can't differentiate between "this warning was introduced to this file in these changes", and "this warning already existed in the files affected by these changes". If we do back-port this check to the older branches, we're going to get a ton of failing CI runs because of all of the pre-existing issues that need to be cleaned up, or we'll need to spend the time to re-do all the clean-up work that I'd done before I set up the check on what was the master branch at the time. Were you expecting this ticket to also include the clean-up work?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-370) file_upload() function docs should have a caveat for transferring large files

2018-03-26 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-370  
 
 
  file_upload() function docs should have a caveat for transferring large files   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Sprint: 
 Bolt Ready for Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1628) Set of breaking changes staged for facter 4

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley commented on  FACT-1628  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Set of breaking changes staged for facter 4   
 

  
 
 
 
 

 
 The more I dig into the networking tickets, the more I'm unsure they can be collected into one or two neat fixes. I'm going to punt on adding anything in that space for now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-335) Boltlib functions should have configurable timeouts

2018-03-26 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-335  
 
 
  Boltlib functions should have configurable timeouts   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Sprint: 
 Bolt Discover/Design  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-408) Include a batch plan in Bolt

2018-03-26 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-408  
 
 
  Include a batch plan in Bolt   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 

  
 
 
 
 

 
 Create a batch plan - for running N nodes at a time - to include as part of the out-of-the-box experience with Bolt (similar to aggregate and canary). Alternatively, we could add a {{\_concurrency}} option for run actions.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8535) Backport ruby warning rake task

2018-03-26 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig assigned an issue to Jacob Helwig  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8535  
 
 
  Backport ruby warning rake task   
 

  
 
 
 
 

 
Change By: 
 Jacob Helwig  
 
 
Assignee: 
 Eric Delaney Jacob Helwig  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8588) Support multiple implementations when loading tasks

2018-03-26 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8588  
 
 
  Support multiple implementations when loading tasks   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Sprint: 
 Bolt  Kanban  Ready for Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-135) I want to execute different versions of the task file on different platforms

2018-03-26 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-135  
 
 
  I want to execute different versions of the task file on different platforms   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Sprint: 
 Bolt  Kanban  Ready for Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1677) facter get child interfaces's ip address twice with intended for the primary interface

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley commented on  FACT-1677  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: facter get child interfaces's ip address twice with intended for the primary interface   
 

  
 
 
 
 

 
 Making sure I fully understand this issue: Facter is outputting blocks for both your 'eth1' and 'eth1:1' devices, but is also listing the 'eth1:1' ip as a binding for 'eth1'? Could you provide a bit more information on how the 'eth1:1' device is set up so we can try to reproduce internally?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1453) $ipaddress on openvz container returning 127.0.0.2

2018-03-26 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley commented on  FACT-1453  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: $ipaddress on openvz container returning 127.0.0.2   
 

  
 
 
 
 

 
 Proposed fix for this: When the default route points to an interface with aliases, we should examine those aliases and pick one which is not bound to a loopback address. I do not believe this needs to be considered a breaking change, since the current behavior seems "obviously wrong" in this case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8562) File performance nearly twice as slow after update

2018-03-26 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8562  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: File performance nearly twice as slow after update   
 

  
 
 
 
 

 
 This is a problem because future requests lookup server and serverport in the context, and rely on the context raising an exception when the values aren't set (as is the case when not using server_list)). The exception message contains the entire context stack (serialized as a string). The agent rescues the exception and never looks at the message. After 100 or so requests, the exception message string has length > 200K. So the slowness is due to allocating large chunks of memory unnecessarily. We shouldn't be relying on exceptions for flow control, and the context shouldn't include stack.inspect in the exception message.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-361) Gather facts from puppetdb

2018-03-26 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi assigned an issue to Michael Smith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-361  
 
 
  Gather facts from puppetdb   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Assignee: 
 Lucy Wyman Michael Smith  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-365) Missing period in "E.g." in usage text

2018-03-26 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi assigned an issue to Kate Lopresti  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-365  
 
 
  Missing period in "E.g." in usage text   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Assignee: 
 Michael Smith Kate Lopresti  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-407) Using TargetSpec in plan parameters breaks `bolt plan show`

2018-03-26 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-407  
 
 
  Using TargetSpec in plan parameters breaks `bolt plan show`   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Assignee: 
 Alex Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3862) replace facts failing for some nodes

2018-03-26 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey commented on  PDB-3862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: replace facts failing for some nodes   
 

  
 
 
 
 

 
 Russell Mull candidate for 5.2.2? /cc Jeff Yarnell Nirupama Mantha  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3862) replace facts failing for some nodes

2018-03-26 Thread Kenn Hussey (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kenn Hussey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3862  
 
 
  replace facts failing for some nodes   
 

  
 
 
 
 

 
Change By: 
 Kenn Hussey  
 
 
Affects Version/s: 
 PE Irving  
 
 
Affects Version/s: 
 PDB 5.2.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3883) puppet-client-tools package for Debian 9 (Stretch) is missing

2018-03-26 Thread David Jacob (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Jacob created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3883  
 
 
  puppet-client-tools package for Debian 9 (Stretch) is missing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/03/26 7:55 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 David Jacob  
 

  
 
 
 
 

 
 While trying to install the PuppetDB CLI tools on Debian 9 (Stretch) using these instructions I get the following error message:  
 
 
 
 
 root@my-machine:~# apt install puppet-client-tools  
 
 
 Reading package lists... Done  
 
 
 Building dependency tree 
 
 
 Reading state information... Done  
 
 
 E: Unable to locate package puppet-client-tools
  
 
 
 
  I don't see the package listed in the repository web interface. It seems to be present for Jessie. Debian 9 is listed as a supported platform on the PuppetDB index page so I expected the CLI tools to be 

Jira (PUP-8040) Puppet does not initialize I18N locale per thread

2018-03-26 Thread Enis Inan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Enis Inan assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8040  
 
 
  Puppet does not initialize I18N locale per thread   
 

  
 
 
 
 

 
Change By: 
 Enis Inan  
 
 
Assignee: 
 Enis Inan  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.