Jira (PUP-10038) Add Report HTTP service

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10038  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add Report HTTP service   
 

  
 
 
 
 

 
 Passed CI in 605187329a  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326131.1569367572000.17680.1578541320135%40Atlassian.JIRA.


Jira (PUP-10145) Add Puppet HTTP service

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10145  
 
 
  Add Puppet HTTP service   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 Implement a {{:puppet}} http service with methods for:{noformat}GET /puppet/v3/nodePOST /puppet/v3/catalogPUT /puppet/v3/facts{noformat}h4. NodeAccepts {{name}}, {{environment}}, {{configured_environment}}, {{transaction_uuid}} parameters.h4. CatalogAccepts {{name}}, {{environment}}, {{facts}} , {{facts_format}}, {{transaction_uuid}}, {{job_uuid}}, {{static_catalog}}, {{checksum_type}}  parameters.h4. FactsAccepts {{name}}, {{environment}}, {{facts}}, {{transaction_uuid}} parameters.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit 

Jira (PUP-10146) Add File HTTP service

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10146  
 
 
  Add File HTTP service   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 

  
 
 
 
 

 
 Implement a {{:file}} service with methods for:{noformat}get_file_metadataget_file_metadatasget_file_content{noformat}h4. get_file_metadata  (singular) Required arguments {{ : mount_point}}, {{ : path}}, {{environment}} , where {{mount_point}} can be {{modules}}, {{tasks}}, {{plugins}}, etc, and {{path}} is a file system path encoded in the URL. Optional arguments {{links}}, {{checksum_type}}, {{source_permissions}}, defaulting to whatever puppet 6 doesUse the {{Content-Type}} header in the response to lookup the network formatter.  If the {{Content-Type}} contains a {{charset}}, force encode the response body that that encoding.  Use the formatter to deserialize the {{Puppet::FileServing::Metadata}} instance.If the response code is 404, then I believe we want to treat that as not an error (due to a long standing puppet bug). For example, here is a file request, where the {{mount=modules}} and {{path=foo/file}}:{noformat}HTTP GET https://brown-flurry.delivery.puppetlabs.net:8140/puppet/v3/file_metadata/modules/foo/file?environment=production=manage_type=md5_permissions=ignore{noformat}And a directory request, where the {{mount=modules}} and {{path=foo/directory}}{noformat}HTTP GET https://brown-flurry.delivery.puppetlabs.net:8140/puppet/v3/file_metadata/modules/foo/directory?environment=production=manage_type=md5_permissions=ignore{noformat} h4. get_file_metadatas  (plural) Required arguments {{ : mount_point}}, {{ : environment}}Optional arguments {{ path}}, {{ environment recurse }} Optional arguments ,  {{ recurse recurselimit }}, {{ignore}}, {{links}}, {{checksum_type}}, {{source_permissions}} . Note {{ignore}} can have multiple values, so we should accept an array of values. Use the {{Content-Type}} header in the response to lookup the network formatter. Use the formatter to deserialize an array of {{Puppet::FileServing::Metadata}} instances. If the response code is 404 For example ,  then I believe we want to treat that as not an error (due to  here is  a  long standing  recursive directory request:{noformat}HTTP GET https://brown-flurry.delivery.puppetlabs.net:8140/  puppet  bug) /v3/file_metadatas/modules/foo/directory?environment=production=manage=true_permissions=ignore_type=md5 {noformat}The {{path}} can be omitted when recursing the top-level mount such as {{pluginsync}}:{noformat}HTTP GET https://brown-flurry . delivery.puppetlabs.net:8140/puppet/v3/file_metadatas/plugins?environment=production=follow=true_permissions=ignore=.svn=CVS=.git=.hg_type=md5  {noformat}   h4. get_file_contentRequired arguments {{:mount_point}}, {{:path}}Always set header {{Accept: application/octet-stream}}.Force encode the response body as {{Encoding::BINARY}}.Stream the response body to the caller.  
 

  
 

Jira (PUP-10225) Puppetserver 6 performance regression

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10225  
 
 
  Puppetserver 6 performance regression   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Froyo  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341411.1578473781000.17587.1578529020236%40Atlassian.JIRA.


Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax

2020-01-08 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen commented on  PUP-10113  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Functions are slower if called with chained syntax than with prefix syntax   
 

  
 
 
 
 

 
 Proposed PR: https://github.com/puppetlabs/puppet/pull/7797 The patchset appears to have yielded a nice 10 – 20% performance improvement when applied to a customer site that uses chained functions heavily.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.17624.1578529860639%40Atlassian.JIRA.


Jira (PUP-10145) Add Puppet HTTP service

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10145  
 
 
  Add Puppet HTTP service   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity Grooming Platform Core KANBAN  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335806.1574123423000.17693.1578545280155%40Atlassian.JIRA.


Jira (PUP-10145) Add Puppet HTTP service

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper assigned an issue to Josh Cooper  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10145  
 
 
  Add Puppet HTTP service   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Assignee: 
 Josh Cooper  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335806.1574123423000.17692.1578545280099%40Atlassian.JIRA.


Jira (PUP-10222) Puppet lookup invocation recursion detection not thread-safe

2020-01-08 Thread Maggie Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maggie Dreyer commented on  PUP-10222  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet lookup invocation recursion detection not thread-safe   
 

  
 
 
 
 

 
 So, here's what I think is happening: as we are looking up a key, we store a copy of the current instance of Invocation in the @current class variable here. If, when a new Invocation is initialized, @current is not nil, we think that the value of @current is our parent, so we copy the name_stack from that "parent" to the @name_stack for this instance. However, in a multithreaded environment, it is possible for @current to have been set by a different thread, so the new instance will think it has a parent when it does not. If that parent Invocation was trying to look up a key of the same name as the current instance, we will throw a RecursiveLookup error, because the name stack contains our key already.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341337.157842233.17569.1578528180567%40Atlassian.JIRA.


Jira (PUP-10161) Regresssion: puppet 6.11 can't manage selinux on centos/redhat 8

2020-01-08 Thread James Ralston (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Ralston commented on  PUP-10161  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regresssion: puppet 6.11 can't manage selinux on centos/redhat 8   
 

  
 
 
 
 

 
 Red Hat responded to me. Red Hat asserts (and I have verified) that RHEL7 did build libselinux.so.1 with the rpm_execcon() function. The specific line in the RHEL7 libselinux.spec file (for every version of the RHEL7 libselinux package) is:  
 
 
 
 
 # FIXME: export DISABLE_RPM="y"
  
 
 
 
  This is trivial to verify on a RHEL7 system, using the stock Ruby and libselinux-ruby packages:  
 
 
 
 
 $ /usr/bin/irb   
 
 
 irb(main):001:0> require 'selinux'  
 
 
 => true  
 
 
 irb(main):002:0> Selinux.rpm_execcon(1, 2, 3, 4)  
 
 
 TypeError: Expected argument 1 of type char const *, but got Fixnum 2  
 
 
 in SWIG method 'rpm_execcon'  
 
 
 from (irb):2:in `rpm_execcon'  
 
 
 from (irb):2  
 
 
 from /usr/bin/irb:12:in `'  
 
 
 irb(main):003:0> 
  
 

Jira (PUP-10148) Include X-Puppet-Profiling header

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10148  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Include X-Puppet-Profiling header   
 

  
 
 
 
 

 
 Passed CI in 605187329a  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335811.157412461.17683.1578541380287%40Atlassian.JIRA.


Jira (PUP-10053) Update webmock and vcr

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10053  
 
 
  Update webmock and vcr   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.4.z  
 
 
Fix Version/s: 
 PUP 6.4.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326852.1569539131000.16202.1578495000127%40Atlassian.JIRA.


Jira (FACT-1824) Facter includes offline cpus in processors::physicalcount

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1824  
 
 
  Facter includes offline cpus in processors::physicalcount   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 FACT 3.13.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.237834.151931408.16172.1578494700175%40Atlassian.JIRA.


Jira (FACT-2096) Windows system32 environment variable issue after installation of "RDS-RD-Server"

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2096  
 
 
  Windows system32 environment variable issue after installation of "RDS-RD-Server"   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 FACT 3.13.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332946.1572508394000.16195.1578494880607%40Atlassian.JIRA.


Jira (FACT-2146) facter not returning expected ipaddress details on Solaris 10 with IPMP

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2146  
 
 
  facter not returning expected ipaddress details on Solaris 10 with IPMP   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 FACT 3.13.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.337174.1575268168000.16200.1578494880831%40Atlassian.JIRA.


Jira (FACT-2054) Facter::Core::Execution.execute incorrectly expands shell builtins

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2054  
 
 
  Facter::Core::Execution.execute incorrectly expands shell builtins   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 FACT 3.13.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327886.1570111406000.16185.1578494820439%40Atlassian.JIRA.


Jira (FACT-2016) Add the scope of found ipv6 addresses (global/linklocal/...) as a fact

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2016  
 
 
  Add the scope of found ipv6 addresses (global/linklocal/...) as a fact   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 FACT 3.13.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324361.1568209514000.16182.1578494820307%40Atlassian.JIRA.


Jira (PUP-9562) User resource does not respect forcelocal for the comment parameter

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9562  
 
 
  User resource does not respect forcelocal for the comment parameter   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.4.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300292.1552589325000.16219.1578495300383%40Atlassian.JIRA.


Jira (FACT-2260) remove deprecation of facter --puppet

2020-01-08 Thread Luchian Nemes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Luchian Nemes assigned an issue to Luchian Nemes  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2260  
 
 
  remove deprecation of facter --puppet   
 

  
 
 
 
 

 
Change By: 
 Luchian Nemes  
 
 
Assignee: 
 Luchian Nemes  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340538.1576868667000.16216.1578495300331%40Atlassian.JIRA.


Jira (FACT-2004) cloud fact does not detect Azure with NetworkManager

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2004  
 
 
  cloud fact does not detect Azure with NetworkManager   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 FACT 3.13.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322752.1567082147000.16176.1578494760275%40Atlassian.JIRA.


Jira (PUP-10095) Better error handling for reading task metadata

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10095  
 
 
  Better error handling for reading task metadata   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.4.z  
 
 
Fix Version/s: 
 PUP 6.4.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328355.1570487848000.16204.1578495180263%40Atlassian.JIRA.


Jira (FACT-2258) Facter does not detect t3a instances on AWS

2020-01-08 Thread Gabriel Nagy (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Nagy assigned an issue to Gabriel Nagy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2258  
 
 
  Facter does not detect t3a instances on AWS   
 

  
 
 
 
 

 
Change By: 
 Gabriel Nagy  
 
 
Assignee: 
 Gabriel Nagy  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340118.1576692534000.16224.1578495480167%40Atlassian.JIRA.


Jira (FACT-2261) Resolved facts Nil values are replaced with empty strings even when no user query is provided. They should only be replaced with an empty string when a user query is provided.

2020-01-08 Thread Bogdan Irimie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Bogdan Irimie  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2261  
 
 
  Resolved facts Nil values are replaced with empty strings even when no user query is provided. They should only be replaced with an empty string when a user query is provided.   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341412.1578474663000.16240.1578496560054%40Atlassian.JIRA.


Jira (FACT-2264) Implement fips, scope6 and sysmte32 fact for windows

2020-01-08 Thread Oana Tanasoiu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oana Tanasoiu assigned an issue to Oana Tanasoiu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2264  
 
 
  Implement fips, scope6 and sysmte32 fact for windows   
 

  
 
 
 
 

 
Change By: 
 Oana Tanasoiu  
 
 
Assignee: 
 Oana Tanasoiu  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341433.157849307.16151.1578493140276%40Atlassian.JIRA.


Jira (FACT-2264) Implement fips, scope6 and sysmte32 fact for windows

2020-01-08 Thread Oana Tanasoiu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oana Tanasoiu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2264  
 
 
  Implement fips, scope6 and sysmte32 fact for windows   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/08 6:17 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Oana Tanasoiu  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit 

Jira (PUP-10170) Do not store Puppet stack within Ruby stack / Backport master work to 5.5.x

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10170  
 
 
  Do not store Puppet stack within Ruby stack / Backport master work to 5.5.x   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.12.0  
 
 
Fix Version/s: 
 PUP 6.4.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338793.1576002994000.16212.1578495240139%40Atlassian.JIRA.


Jira (PUP-10149) Systemd provider daemon-reload broken in puppet 6.11.0

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10149  
 
 
  Systemd provider daemon-reload broken in puppet 6.11.0   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.4.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335940.157420669.16206.1578495180351%40Atlassian.JIRA.


Jira (PUP-10057) User resource on Windows confuses domain and local accounts

2020-01-08 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10057  
 
 
  User resource on Windows confuses domain and local accounts   
 

  
 
 
 
 

 
Change By: 
 Jean Bond  
 
 
Release Notes Summary: 
 Puppet no longer checks for domain users or groups when managing local resources on Windows. This fixes a local user management issue where an  AD  Active Directory  account existed with the same name as the local user.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327453.1569921077000.17019.1578512820328%40Atlassian.JIRA.


Jira (PUP-10160) Puppet should not load types and providers during environment convergence

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10160  
 
 
  Puppet should not load types and providers during environment convergence   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Release Notes Summary: 
 Previously puppet agents could fail to apply a catalog if the agent switched environments based on node classification and there were different versions of a module in those environments. As a result of this change, an agent should converge to its server-assigned environment more quickly, only load types and providers once, and only update its cached catalog  if  after  the environment converges.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.337880.157548855.16800.1578509160189%40Atlassian.JIRA.


Jira (PUP-10150) Ruby stacktraces no longer interleave Puppet Code stacktraces

2020-01-08 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10150  
 
 
  Ruby stacktraces no longer interleave Puppet Code stacktraces   
 

  
 
 
 
 

 
Change By: 
 Jean Bond  
 
 
Release Notes Summary: 
 Fixes This release fixes  a bug where stacktraces from errors no longer had the Ruby stack frames interleaved with the Puppet stack frames when using `trace`.  Also This release also  introduces a new setting ,  `puppet_trace`,  that will cause  which prints  the Puppet stack  to be printed  without the Ruby frames interleaved. If  the  `trace`  setting  is enabled, it overrides the value of `puppet_trace`.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.336155.1574344871000.17096.1578513540251%40Atlassian.JIRA.


Jira (PUP-10213) Do not create exceptions for stacktrace information when we know we won't use that information

2020-01-08 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10213  
 
 
  Do not create exceptions for stacktrace information when we know we won't use that information   
 

  
 
 
 
 

 
Change By: 
 Jean Bond  
 
 
Release Notes Summary: 
 Some This release includes improvements to the evaluator, meaning some  compilation warnings  will  now take less time to compute.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340907.1578000208000.17105.1578513601021%40Atlassian.JIRA.


Jira (PUP-10170) Do not store Puppet stack within Ruby stack / Backport master work to 5.5.x

2020-01-08 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond commented on  PUP-10170  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Do not store Puppet stack within Ruby stack / Backport master work to 5.5.x   
 

  
 
 
 
 

 
 Justin Stoller, is PUP-10213 also related to this work? I'm thinking of making one release note to rule them all.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338793.1576002994000.17148.1578514200199%40Atlassian.JIRA.


Jira (PUP-9391) HP-UX usermod syntax is incorrect

2020-01-08 Thread Jean Bond (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jean Bond updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9391  
 
 
  HP-UX usermod syntax is incorrect   
 

  
 
 
 
 

 
Change By: 
 Jean Bond  
 
 
Release Notes Summary: 
 Fixed usermod command arguments order for The  HP-UX  provider forced command line arguments to `usermod` to be in a specific order .  This is now fixed.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290075.1546446054000.17158.1578514740435%40Atlassian.JIRA.


Jira (PUP-10170) Do not store Puppet stack within Ruby stack / Backport master work to 5.5.x

2020-01-08 Thread Justin Stoller (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Justin Stoller commented on  PUP-10170  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Do not store Puppet stack within Ruby stack / Backport master work to 5.5.x   
 

  
 
 
 
 

 
 Yes, this ticket was a performance improvement that has already gone out in the last Platform release (6.11?). Now it will also be going out in 5.5.x and 6.4.x. It caused a regression in stacktrace printing which will be fixed in 6.12, along with that fix we introduced the new feature of the "puppet_trace" setting. 5.5.x & 6.4.x won't see the regression but will get the new "puppet_trace" output option.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338793.1576002994000.17274.1578519300859%40Atlassian.JIRA.


Jira (PUP-10227) Close the http connection prior to sleeping retry-after seconds

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10227  
 
 
  Close the http connection prior to sleeping retry-after seconds   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341492.1578520569000.17314.1578520620239%40Atlassian.JIRA.


Jira (PUP-10227) Close the http connection prior to sleeping retry-after seconds

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10227  
 
 
  Close the http connection prior to sleeping retry-after seconds   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/08 1:56 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 To prevent thundering herds, puppetserver may return Retry-After and ask the agent to sleep. Until recently the agent would keep the connection open, until timeout occurs. To reduce resource usage on puppetserver, we should close the connection immediately. The latest puppetserver version will return Connection: close, but agents may talk to older puppetservers versions which would benefit from this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

Jira (PUP-10226) URL encode paths in http client

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10226  
 
 
  URL encode paths in http client   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/08 1:33 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Josh Cooper  
 

  
 
 
 
 

 
 The various Puppet::HTTP::Service::* methods need to URL encode the HTTP request path. It's not currently an issue for the CA or Report services in practice, because the request path is something like /puppet/v3/certificate/ where  is generally safe US-ASCII. However, in theory it could contain restricted characters based on this regex, and we'll soon support arbitrary file paths in the FileServer service, e.g. /puppet/v3/file_metadata/module/mymodule/a path with spaces" REST based requests using the indirector current encode the URL path using:  
 
 
 
 
 URI.parse(Puppet::Util.uri_encode(key))
  
 
 
 
  So we should do something similar to maintain compatibility.  
 

  
 
 
 
 

 
 
 

 
 

Jira (PUP-10147) Handle PSON downgrade

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10147  
 
 
  Handle PSON downgrade   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335810.1574124508000.17305.1578520380347%40Atlassian.JIRA.


Jira (PUP-10226) URL encode paths in http client

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10226  
 
 
  URL encode paths in http client   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341489.1578519209000.17304.1578520380303%40Atlassian.JIRA.


Jira (PUP-10227) Close the http connection prior to sleeping retry-after seconds

2020-01-08 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10227  
 
 
  Close the http connection prior to sleeping retry-after seconds   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.y  
 
 
Fix Version/s: 
 PUP 6.4.z  
 
 
Fix Version/s: 
 PUP 5.5.z  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341492.1578520569000.17334.1578521640109%40Atlassian.JIRA.


Jira (PUP-10228) Puppet 6 daemons do not release ssl_lockfile

2020-01-08 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10228  
 
 
  Puppet 6 daemons do not release ssl_lockfile   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.11.1  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/08 2:32 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Charlie Sharpsteen  
 

  
 
 
 
 

 
 The puppet service holds ssl_lockfile after submiting a Certificate Signing Request. This blocks other processes from running puppet agent -t or puppet ssl download_cert after the request has been signed by the Puppet CA. 
 
 
 
Reproduction Case 
  
 
 
Install Puppet Server 6.7 on CentOS 7 and initialize it: 
  
 
 
 
 
 yum install -y http://yum.puppetlabs.com/puppet6-release-el-7.noarch.rpm  
 
 
 yum install -y puppetserver  
 
 
    

Jira (PUP-10228) Puppet 6 daemons do not release ssl_lockfile

2020-01-08 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10228  
 
 
  Puppet 6 daemons do not release ssl_lockfile   
 

  
 
 
 
 

 
Change By: 
 Charlie Sharpsteen  
 

  
 
 
 
 

 
 The {{puppet}} service holds {{ssl_lockfile}} after submiting a CertificateSigning Request. This blocks other processes from running {{puppet agent -t}}or {{puppet ssl download_cert}} after the request has been signed by thePuppet CA. ## h2.  Reproduction Case  - Install Puppet Server 6.7 on CentOS 7 and initialize it:{code:bash}yum install -y http://yum.puppetlabs.com/puppet6-release-el-7.noarch.rpmyum install -y puppetserversource /etc/profile.d/puppet-agent.shpuppet config set server $(hostname -f)puppetserver ca setupsystemctl start puppetserver{code}  - Install Puppet Agent 6.11.1 on another CentOS 7 node, configure it to talkwith the server, and start the daemon:{code:bash}yum install -y http://yum.puppetlabs.com/puppet6-release-el-7.noarch.rpmyum install -y puppet-agentsource /etc/profile.d/puppet-agent.shpuppet config set server systemctl start puppet{code}  - Sign the certificate on the server:{code:bash}puppetserver ca sign --certname={code}  - Run {{puppet agent -t}} or {{puppet ssl download_cert}} on the agent. ### h3.  OutcomeBoth commands fail with "Could not run: Another puppet instance is already running; exiting"{noformat}# puppet agent -t --traceError: Could not run: Another puppet instance is already running; exiting/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/state_machine.rb:421:in `with_lock'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/state_machine.rb:392:in `run_machine'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/state_machine.rb:370:in `ensure_client_certificate'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:505:in `wait_for_certificates'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:368:in `run_command'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:382:in `block in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:687:in `exit_on_fail'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:382:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:143:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:77:in `execute'/opt/puppetlabs/puppet/bin/puppet:5:in `'# puppet ssl download_cert --traceError: Could not run: Another puppet instance is already running; exiting/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/state_machine.rb:421:in `with_lock'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/state_machine.rb:392:in `run_machine'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/state_machine.rb:361:in `ensure_ca_certificates'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/ssl.rb:130:in `main'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:390:in `run_command'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:382:in `block in 

Jira (PUP-10225) Puppetserver 6 performance regression

2020-01-08 Thread Iain Buclaw (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Iain Buclaw updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10225  
 
 
  Puppetserver 6 performance regression   
 

  
 
 
 
 

 
Change By: 
 Iain Buclaw  
 

  
 
 
 
 

 
 *Puppet Version: 6.11.1* *Puppet Server Version: 6.7.2* *OS Name/Version: Ubuntu/16.04*High load/cpu usage on puppetserver in version 6.*Desired Behavior:* Same as puppet 5.*Actual Behavior:* 6x more context switches, 6x higher load average for the same amount of traffic/requests as when running puppetserver 5. Attaching host graphs that show before/after for the upgrade from puppetserver 5.3.10 to 6.7.2  !puppetserver-load.png|thumbnail!  !puppetserver-contextswitches.png|thumbnail!  !puppetserver-cpu.png|thumbnail!   
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit 

Jira (PUP-10225) Puppetserver 6 performance regression

2020-01-08 Thread Iain Buclaw (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Iain Buclaw created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10225  
 
 
  Puppetserver 6 performance regression   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.7.2  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 puppetserver-contextswitches.png, puppetserver-cpu.png, puppetserver-load.png  
 
 
Created: 
 2020/01/08 12:56 AM  
 
 
Fix Versions: 
 PUP 5.y  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Iain Buclaw  
 

  
 
 
 
 

 
 Puppet Version: 6.11.1 Puppet Server Version: 6.7.2 OS Name/Version: Ubuntu/16.04 High load/cpu usage on puppetserver in version 6. Desired Behavior: Same as puppet 5. Actual Behavior: 6x more context switches, 6x higher load average for the same amount of traffic/requests as when running puppetserver 5.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

   

Jira (PUP-10224) Add ensure_at_least() function to PE for the package type

2020-01-08 Thread Kevin Reeuwijk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Reeuwijk commented on  PUP-10224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add ensure_at_least() function to PE for the package type   
 

  
 
 
 
 

 
 Josh Cooper the difference is that this time an actual fix has been built, that can be leveraged (see the PR). It's not a generic request to build something new, it's a request to adopt a fix that works. I worked on this with Reid Vandewiele and he acknowledges that this would fulfill a customer demand that has been there for 3+ years.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341101.1578317783000.15950.1578476700187%40Atlassian.JIRA.


Jira (PUP-10225) Puppetserver 6 performance regression

2020-01-08 Thread Iain Buclaw (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Iain Buclaw updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10225  
 
 
  Puppetserver 6 performance regression   
 

  
 
 
 
 

 
Change By: 
 Iain Buclaw  
 
 
Method Found: 
 Needs Assessment Other (please specify in description)  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341411.1578473781000.15933.1578473940050%40Atlassian.JIRA.


Jira (FACT-2034) Extract cache from resolvers in a middle layer that sits between facts and resolvers.

2020-01-08 Thread Bogdan Irimie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2034  
 
 
  Extract cache from resolvers in a middle layer that sits between facts and resolvers.   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 * Right now there is no distinction, from the cache's standpoint,  between a fact that is resolved with a nil value and a fact that is not resolved. This case should be fixed when implementing the global cache because it might bring performance degradations when a resolver cannot resolve a fact and that resolver is called multiple times.  * Global cache should be able to cache custom facts.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit 

Jira (PUP-1519) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number

2020-01-08 Thread Kevin Reeuwijk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Reeuwijk commented on  PUP-1519  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number   
 

  
 
 
 
 

 
 A fix is possible through https://github.com/puppetlabs/puppetlabs-stdlib/pull/1038, as noted in PUP-10224  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.24581.1390679442000.15993.1578476762356%40Atlassian.JIRA.


Jira (FACT-2261) Resolved facts Nil values are replaced with empty strings even when no user query is provided. They should only be replaced with an empty string when a user query is provided.

2020-01-08 Thread Bogdan Irimie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2261  
 
 
  Resolved facts Nil values are replaced with empty strings even when no user query is provided. They should only be replaced with an empty string when a user query is provided.   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Summary: 
 Resolved facts Nil values are replaced with empty strings even when no user query is provided. They should only be replaced with an empty string when a user query is provided.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341412.1578474663000.15945.1578474720189%40Atlassian.JIRA.


Jira (FACT-2261) Nil values are replaced with empty strings even when no user query is provided. They should only be replaced with an empty string when a user query is provided.

2020-01-08 Thread Bogdan Irimie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2261  
 
 
  Nil values are replaced with empty strings even when no user query is provided. They should only be replaced with an empty string when a user query is provided.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/08 1:11 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-10224) Add ensure_at_least() function to PE for the package type

2020-01-08 Thread Kevin Reeuwijk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Reeuwijk commented on  PUP-10224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add ensure_at_least() function to PE for the package type   
 

  
 
 
 
 

 
 This implementation would be specific to PE only, as it leverages the Package Inspector inventory data. It does not work for Open Source Puppet, hence I created it under the PE project instead of the PUP project.  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341101.1578317783000.15997.1578477000163%40Atlassian.JIRA.


Jira (PUP-10021) User resource always reports password changed when account disabled for Win 2012 R2

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10021  
 
 
  User resource always reports password changed when account disabled for Win 2012 R2   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.12.0  
 
 
Fix Version/s: 
 PUP 6.4.5  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324443.1568255866000.16048.1578481020323%40Atlassian.JIRA.


Jira (PUP-9963) The 'value' field of 'selboolean' should accept Booleans

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9963  
 
 
  The 'value' field of 'selboolean' should accept Booleans   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.4.5  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320668.1565704234000.16091.1578485580391%40Atlassian.JIRA.


Jira (PUP-10059) Puppet won't install (some) packages with ensure => held

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10059  
 
 
  Puppet won't install (some) packages with ensure => held   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.4.z  
 
 
Fix Version/s: 
 PUP 5.5.z  
 
 
Fix Version/s: 
 PUP 6.4.5  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit 

Jira (PUP-10102) Systemd provider is not correctly selected on Alpine Linux

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10102  
 
 
  Systemd provider is not correctly selected on Alpine Linux   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.4.5  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.329403.1571128033000.16104.1578485760651%40Atlassian.JIRA.


Jira (PUP-10116) Add GKE hypervisor to pxp-agent and puppet

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10116  
 
 
  Add GKE hypervisor to pxp-agent and puppet   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332952.1572515789000.16107.1578485820247%40Atlassian.JIRA.


Jira (PUP-10116) Add GKE hypervisor to pxp-agent and puppet

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10116  
 
 
  Add GKE hypervisor to pxp-agent and puppet   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.4.5  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332952.1572515789000.16109.1578485820335%40Atlassian.JIRA.


Jira (FACT-2262) Add mechanism for catching require errors in resolvers

2020-01-08 Thread Bogdan Irimie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2262  
 
 
  Add mechanism for catching require errors in resolvers   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/08 3:02 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit 

Jira (FACT-2262) Add mechanism for catching require errors in resolvers

2020-01-08 Thread Bogdan Irimie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Bogdan Irimie  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2262  
 
 
  Add mechanism for catching require errors in resolvers   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341416.1578481328000.16052.1578481380231%40Atlassian.JIRA.


Jira (PUP-10140) puppet service and puppet-agent failing on windows

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10140  
 
 
  puppet service and puppet-agent failing on windows
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.12.0  
 
 
Fix Version/s: 
 PUP 6.4.5  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.335096.1573682215000.16064.1578485340506%40Atlassian.JIRA.


Jira (PUP-10124) Package provider removes colon from package name

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10124  
 
 
  Package provider removes colon from package name   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.12.0  
 
 
Fix Version/s: 
 PUP 6.4.5  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.331590.1571823187000.16060.1578485340367%40Atlassian.JIRA.


Jira (PUP-9562) User resource does not respect forcelocal for the comment parameter

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9562  
 
 
  User resource does not respect forcelocal for the comment parameter   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300292.1552589325000.16087.1578485520203%40Atlassian.JIRA.


Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8949  
 
 
  Package pip provide won't work with ensure latest and custom index   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.261544.1529423125000.16079.1578485400932%40Atlassian.JIRA.


Jira (PUP-7113) Implement forcelocal in AIX providers

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7113  
 
 
  Implement forcelocal in AIX providers   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.12.0  
 
 
Fix Version/s: 
 PUP 6.4.5  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.171015.1484844194000.16076.1578485400799%40Atlassian.JIRA.


Jira (PUP-9391) HP-UX usermod syntax is incorrect

2020-01-08 Thread Dorin Pleava (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dorin Pleava updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9391  
 
 
  HP-UX usermod syntax is incorrect   
 

  
 
 
 
 

 
Change By: 
 Dorin Pleava  
 
 
Fix Version/s: 
 PUP 6.12.0  
 
 
Fix Version/s: 
 PUP 6.4.5  
 
 
Fix Version/s: 
 PUP 5.5.18  
 

  
 
 
 
 

 
 
 

 
 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290075.1546446054000.16084.1578485460187%40Atlassian.JIRA.


Jira (FACT-2263) Fix system profile on macos Catalina

2020-01-08 Thread Bogdan Irimie (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bogdan Irimie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2263  
 
 
  Fix system profile on macos Catalina   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Bogdan Irimie  
 
 
Created: 
 2020/01/08 4:54 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Bogdan Irimie  
 

  
 
 
 
 

 
 System profile info can contain : in value and the SystemProfiler resolver will throw error because it cannot convert to hash ``` facter-ng/lib/resolvers/macosx/system_profiler_resolver.rb:45:in `to_h': wrong array length at 10 (expected 2, was 3) (ArgumentError) # terminated with exception (report_on_exception is true): ```  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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