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

2020-01-07 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.11.11  
 

  
 
 
 
 

 
 
 

 
 
 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.15907.1578470100487%40Atlassian.JIRA.


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

2020-01-07 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.11.11  
 

  
 
 
 
 

 
 
 

 
 
 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.15902.1578470040620%40Atlassian.JIRA.


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

2020-01-07 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.11.11  
 

  
 
 
 
 

 
 
 

 
 
 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.15894.1578470040499%40Atlassian.JIRA.


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

2020-01-07 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.11.11  
 

  
 
 
 
 

 
 
 

 
 
 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.15889.1578469980463%40Atlassian.JIRA.


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

2020-01-07 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.11.11  
 

  
 
 
 
 

 
 
 

 
 
 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.15883.1578469980306%40Atlassian.JIRA.


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

2020-01-07 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.11.11  
 

  
 
 
 
 

 
 
 

 
 
 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.15879.1578469740183%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10224  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Pretty sure this is a duplicate of 1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number" class="issue-link" data-issue-key="PUP-1519" style="color: #3b73af; text-decoration: none">PUP-1519 and should be closed.  
 

  
 
 
 
 

 
 
 

 
 
 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.15871.1578460200203%40Atlassian.JIRA.


Jira (PUP-10219) Unable to create local user when username already exists in Windows domain

2020-01-07 Thread Steven Towill (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Towill commented on  PUP-10219  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to create local user when username already exists in Windows domain   
 

  
 
 
 
 

 
 Hi Gabriel Nagy, Good news. I've tested changing line 207 in adsi.rb to the upcase syntax provided by you as well as the casecmp syntax suggested by Josh Cooper and both versions work. I've also tested modifying the comment and the groups properties.  One thing I noticed when testing the group change in noop mode is the output isn't correct. The output returned contains references to the groups as defined in the manifest as well as the current built-in group name. 

Notice: Compiled catalog for member01.domain.com in environment production in 0.02 seconds Notice: /Stage[main]/Main/User[test_user]/groups: current_value BUILTIN\Administrators, should be 'Administrators,BUILTIN\Administrators,Remote Management Users' (noop) Notice: Class[Main]: Would have triggered 'refresh' from 1 event Notice: Stage[main]: Would have triggered 'refresh' from 1 event Notice: Applied catalog in 0.06 seconds
 When running without --noop the output is as expected: 

Notice: Compiled catalog for member01.domain.com in environment production in 0.03 seconds Notice: /Stage[main]/Main/User[test_user]/groups: groups changed BUILTIN\Administrators to ['BUILTIN\Administrators', 'BUILTIN\Remote Management Users'] Notice: Applied catalog in 0.14 seconds
 It looks like noop mode is not recognizing that BUILTIN\Group matches Group in the manifest. I know this is cosmetic so I'm not sure if it's worth the effort to correct. Thanks, Steve  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   

Jira (PUP-10092) Support concatenating sensitive values

2020-01-07 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-10092  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support concatenating sensitive values   
 

  
 
 
 
 

 
 That would mean having to encode "sensitive" into each and every value, integers, floats, strings etc. and that could have drastic impact on performance. The trait of being "sensitive" would then need to be handled by all operations on all those types as we need to automatically propagate the sensitive bit to the results of operations. Thus being lots of code that needs to be touched in many places, and would probably result in instabilities and subtle bugs until we manage to sort it out. So no, don't think this is a viable option. I did consider using the "tainted" bit available in Ruby since it handles such propagation, but it is for almost the opposite of what we want and it turned out to be a very bad idea to use it for some other purpose than what it is intended for. I think the best we can do is to have a different function for EPP templates that produces a sensitive result if it interpolates sensitive. For regular string interpolation it is tricky since calling a function would not work since you would like to pass the string with interpolations to it for evaluation and that would mean evaluating it, which would mean getting "redacted" text into the string. It works for EPP since the argument to the epp functions isn't evaluated. For interpolation into a string we would need a special interpolation instruction, or some new keyword / operator in the language that would tell the evaluator that the interpolation should unwrap and wrap the final result in a sensitive if it interpolates a sensitive.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
  

Jira (PUP-10212) SSL negotiation fails with "tls_process_ske_dhe:dh key too small"

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10212  
 
 
  SSL negotiation fails with "tls_process_ske_dhe:dh key too small"   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Method Found: 
 Needs Assessment  
 
 
Issue Type: 
 Sub-task Bug  
 
 
Parent: 
 PUP-8550  
 

  
 
 
 
 

 
 
 

 
 
 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.336537.1574710008000.15456.1578435600608%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10213  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Do not create exceptions for stacktrace information when we know we won't use that information   
 

  
 
 
 
 

 
 Passed CI in 98418778  
 

  
 
 
 
 

 
 
 

 
 
 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.15431.1578434880103%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10213  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Do not create exceptions for stacktrace information when we know we won't use that information   
 

  
 
 
 
 

 
 Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/98418778127368c1f341745b72dfe83abde887b6  
 

  
 
 
 
 

 
 
 

 
 
 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.15427.1578434820651%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10150  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ruby stacktraces no longer interleave Puppet Code stacktraces   
 

  
 
 
 
 

 
 Passed 5.5.x CI in 9841877812  
 

  
 
 
 
 

 
 
 

 
 
 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.15419.1578434760391%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10150  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ruby stacktraces no longer interleave Puppet Code stacktraces   
 

  
 
 
 
 

 
 Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/c49541b4ff17ca383aa8caafd9f907d30f412ddc  
 

  
 
 
 
 

 
 
 

 
 
 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.15416.1578434760259%40Atlassian.JIRA.


Jira (PDB-4624) Broken links on API Overview page

2020-01-07 Thread Mindy Moreland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mindy Moreland commented on  PDB-4624  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Broken links on API Overview page   
 

  
 
 
 
 

 
 Thanks Austin Blatt! Apologies for not checking if this was a known issue.   
 

  
 
 
 
 

 
 
 

 
 
 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.341326.157841948.15411.1578434700267%40Atlassian.JIRA.


Jira (PUP-10145) Add Puppet HTTP service

2020-01-07 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  
 

  
 
 
 
 

 
 
 

 
 
 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.15370.1578434340077%40Atlassian.JIRA.


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

2020-01-07 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Key: 
 PE PUP - 28073 10224  
 
 
Project: 
 Puppet  Enterprise [Internal]  
 

  
 
 
 
 

 
 
 

 
 
 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.15307.1578433140319%40Atlassian.JIRA.


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

2020-01-07 Thread Rob Braden (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Braden updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Rob Braden  
 
 
Team: 
 Night's Watch  
 

  
 
 
 
 

 
 
 

 
 
 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.15311.1578433140495%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10222  
 
 
  Puppet lookup invocation recursion detection not thread-safe   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Initial production testing by Customer0 with Puppet in multithreaded mode has revealed that the code to detect recursive hiera lookups is not thread-safe:{code}2020-01-07T08:41:31.500-08:00 ERROR [qtp612319309-15848] [puppetserver] Puppet Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'ntp::config_template' failed: Recursive lookup detected in [epel::epel_debuginfo_sslclientkey, ntp::tinker, ntp::leapfile, ntp::config_template] (file: /etc/puppetlabs/code/environments/production/site/profile/manifests/time.pp, line: 2, column: 3) on node ldap-testfixture-prod-2.delivery.puppetlabs.net{code}These errors come from https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/lookup/invocation.rb#L84. Current theory is that since the {{@current}} class variable is not thread-safe, if multiple threads look for the same key at the same time, this error could occur.  In their environments, this was happening when doing automatic lookup of class params via hiera.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
 

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

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


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10222  
 
 
  Puppet lookup invocation recursion detection not thread-safe   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Method Found: 
 Needs Assessment Customer Feedback  
 

  
 
 
 
 

 
 
 

 
 
 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.15269.1578431820109%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10222  
 
 
  Puppet lookup invocation recursion detection not thread-safe   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Initial production testing  by Customer0  with Puppet in multithreaded mode has revealed that the code to detect recursive hiera lookups is not thread-safe:{code}2020-01-07T08:41:31.500-08:00 ERROR [qtp612319309-15848] [puppetserver] Puppet Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'ntp::config_template' failed: Recursive lookup detected in [epel::epel_debuginfo_sslclientkey, ntp::tinker, ntp::leapfile, ntp::config_template] (file: /etc/puppetlabs/code/environments/production/site/profile/manifests/time.pp, line: 2, column: 3) on node ldap-testfixture-prod-2.delivery.puppetlabs.net{code}These errors come from https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/lookup/invocation.rb#L84. Current theory is that since the {{@current}} class variable is not thread-safe, if multiple threads look for the same key at the same time, this error could occur.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

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

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


 
 
 
 

 
 
 

 
   
 Maggie Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10222  
 
 
  Puppet lookup invocation recursion detection not thread-safe   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Initial production testing with Puppet in multithreaded mode has revealed that the code to detect recursive hiera lookups is not thread-safe:{code}2020-01-07T08:41:31.500-08:00 ERROR [qtp612319309-15848] [puppetserver] Puppet Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'ntp::config_template' failed: Recursive lookup detected in [epel::epel_debuginfo_sslclientkey, ntp::tinker, ntp::leapfile, ntp::config_template] (file: /etc/puppetlabs/code/environments/production/site/profile/manifests/time.pp, line: 2, column: 3) on node ldap-testfixture-prod-2.delivery.puppetlabs.net{code}These errors come from https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/lookup/invocation.rb#L84. Current theory is that since the {{@ name_stack current }} class variable is not thread-safe, if multiple threads look for the same key at the same time, this error could occur.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
   

Jira (PUP-10223) Allow apply blocks in plans to contain node definitions

2020-01-07 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10223  
 
 
  Allow apply blocks in plans to contain node definitions   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/07 12:20 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nick Lewis  
 

  
 
 
 
 

 
 Currently, Bolt does not support evaluating node definitions when running plans or applying Puppet code. Accordingly, Puppet does not allow node definitions to be specified in plans. In order to now support node definitions with Bolt, we need to relax the restriction in Puppet so the node definitions can be loaded and used by Bolt. For more information: https://github.com/puppetlabs/bolt/issues/1338  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA 

Jira (PUP-10214) Unexpected results on "replace => false" on symlinks

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10214  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected results on "replace => false" on symlinks   
 

  
 
 
 
 

 
 

I thought the links parameter was for how to handle files local to the puppetmaster
 Nah, it's how the the agent should manage the link (either the link itself or the thing the link points to).  
 

  
 
 
 
 

 
 
 

 
 
 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.340916.1578010636000.15112.1578426480603%40Atlassian.JIRA.


Jira (PUP-10214) Unexpected results on "replace => false" on symlinks

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10214  
 
 
  Unexpected results on "replace => false" on symlinks   
 

  
 
 
 
 

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


Jira (PUP-10221) PObjectTypeExtension doesn't implement implementation_class

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10221  
 
 
  PObjectTypeExtension doesn't implement implementation_class   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Bolt  
 

  
 
 
 
 

 
 
 

 
 
 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.341316.1578416535000.15099.1578426300593%40Atlassian.JIRA.


Jira (PUP-10092) Support concatenating sensitive values

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10092  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support concatenating sensitive values   
 

  
 
 
 
 

 
 The ship may have already sailed, but would it be better if Sensitive was a trait of a type instead of a type, e.g. Binary.new("foo", sensitive: true), String.new("foo", sensitive: true) That way interpolation could preserve the "sensitive-ness" trait, but always return a String?  
 

  
 
 
 
 

 
 
 

 
 
 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.328194.1570226898000.15075.1578425700089%40Atlassian.JIRA.


Jira (PUP-10174) Make the environment caching of settings in puppet work properly with threads

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


 
 
 
 

 
 
 

 
   
 Maggie Dreyer assigned an issue to Tony Vu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10174  
 
 
  Make the environment caching of settings in puppet work properly with threads   
 

  
 
 
 
 

 
Change By: 
 Maggie Dreyer  
 
 
Assignee: 
 Tony Vu  
 

  
 
 
 
 

 
 
 

 
 
 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.323045.1567197294000.14928.1578422640391%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Maggie Dreyer assigned an issue to Maggie Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10222  
 
 
  Puppet lookup invocation recursion detection not thread-safe   
 

  
 
 
 
 

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


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

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


 
 
 
 

 
 
 

 
   
 Maggie Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10222  
 
 
  Puppet lookup invocation recursion detection not thread-safe   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2020/01/07 10:38 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Maggie Dreyer  
 

  
 
 
 
 

 
 Initial production testing with Puppet in multithreaded mode has revealed that the code to detect recursive hiera lookups is not thread-safe:  
 
 
 
 
 2020-01-07T08:41:31.500-08:00 ERROR [qtp612319309-15848] [puppetserver] Puppet Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'ntp::config_template' failed: Recursive lookup detected in [epel::epel_debuginfo_sslclientkey, ntp::tinker, ntp::leapfile, ntp::config_template] (file: /etc/puppetlabs/code/environments/production/site/profile/manifests/time.pp, line: 2, column: 3) on node ldap-testfixture-prod-2.delivery.puppetlabs.net
  
 
 
 
  These errors come from https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/lookup/invocation.rb#L84. Current theory is that since the @name_stack class variable is not thread-safe, if multiple threads look for the same key at the same time, this error could occur.  
 

  
 
 
 
 

 
 
 
   

Jira (PDB-4624) Broken links on API Overview page

2020-01-07 Thread Mindy Moreland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mindy Moreland created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4624  
 
 
  Broken links on API Overview page   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 DOCS  
 
 
Created: 
 2020/01/07 9:51 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Mindy Moreland  
 

  
 
 
 
 

 
 Received via the docs feedback form:  Star Rating: 1 Url: https://puppet.com/docs/puppetdb/5.2/api/index.html Comment: Too much broken links... It appears that all the links on this page (in all published versions) are missing the /api/ in their URLs, causing them to 404.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

Jira (PUP-10038) Add Report HTTP service

2020-01-07 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10038  
 
 
  Add Report HTTP service   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Release Notes Summary: 
 The new HTTP code now has a report service it can use for submitting reports  
 
 
Release Notes: 
 Enhancement  
 

  
 
 
 
 

 
 
 

 
 
 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.14580.1578418140407%40Atlassian.JIRA.


Jira (PUP-10221) PObjectTypeExtension doesn't implement implementation_class

2020-01-07 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10221  
 
 
  PObjectTypeExtension doesn't implement implementation_class   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Lucy Wyman  
 
 
Created: 
 2020/01/07 9:02 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Lucy Wyman  
 

  
 
 
 
 

 
 Puppet Version: 6.11.1 Puppet Server Version: OS Name/Version: Ubuntu 16.04 The PObjectTypeExtension, which wraps PObjectType, does not implement the implementation_class method to get the underlying PObjectType implementation class. This raises an error when serializing Puppet::Datatypes::Error objects to pcore.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (PUP-10220) puppet device runs do not currently show errors when performed without --debug option

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10220  
 
 
  puppet device runs do not currently show errors when performed without --debug option   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Network Automation  
 

  
 
 
 
 

 
 
 

 
 
 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.304466.1554994063000.14420.1578415020171%40Atlassian.JIRA.


Jira (PUP-10220) puppet device runs do not currently show errors when performed without --debug option

2020-01-07 Thread David Schmitt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Schmitt commented on  PUP-10220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet device runs do not currently show errors when performed without --debug option   
 

  
 
 
 
 

 
 Moved it to the public tracker, as this is affecting OSP  
 

  
 
 
 
 

 
 
 

 
 
 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.304466.1554994063000.14364.1578412020583%40Atlassian.JIRA.


Jira (PUP-10220) puppet device runs do not currently show errors when performed without --debug option

2020-01-07 Thread David Schmitt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Schmitt moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10220  
 
 
  puppet device runs do not currently show errors when performed without --debug option   
 

  
 
 
 
 

 
Change By: 
 David Schmitt  
 
 
Key: 
 FM PUP - 7956 10220  
 
 
Project: 
 Modules [Internal] 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304466.1554994063000.14360.1578412020407%40Atlassian.JIRA.


Jira (PUP-10136) premature loading of module-provided facts under `-p`

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10136  
 
 
  premature loading of module-provided facts under `-p`   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
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.328315.1570469412000.14292.1578410400451%40Atlassian.JIRA.


Jira (PUP-10136) premature loading of module-provided facts under `-p`

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10136  
 
 
  premature loading of module-provided facts under `-p`   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.12.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328315.1570469412000.14283.1578410340307%40Atlassian.JIRA.


Jira (PUP-10136) premature loading of module-provided facts under `-p`

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10136  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: premature loading of module-provided facts under `-p`   
 

  
 
 
 
 

 
 Merged to master in https://github.com/puppetlabs/puppet/commit/bcd432407d6e61815e70b829620a2e3a0b35efb1  
 

  
 
 
 
 

 
 
 

 
 
 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.328315.1570469412000.14280.1578410340213%40Atlassian.JIRA.


Jira (PUP-10038) Add Report HTTP service

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10038  
 
 
  Add Report HTTP service   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.12.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326131.1569367572000.14267.1578409800320%40Atlassian.JIRA.


Jira (PUP-10038) Add Report HTTP service

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10038  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add Report HTTP service   
 

  
 
 
 
 

 
 Merged to master in https://github.com/puppetlabs/puppet/commit/539749b170efce94f3a781ed186cdfdc5c4d2053  
 

  
 
 
 
 

 
 
 

 
 
 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.14269.1578409800371%40Atlassian.JIRA.


Jira (PUP-10218) Puppet incorrectly detecting stale pidfile

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10218  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet incorrectly detecting stale pidfile   
 

  
 
 
 
 

 
 Thanks for the patch Marcin Deranek! Couple of notes. The code will need to account for posix platforms that don't support -q, e.g. mac osx reports that q is an illegal option. If you want to make a contribution to puppet, could you submit a pull request? If not, that's fine too, we can make the fix ourselves.  
 

  
 
 
 
 

 
 
 

 
 
 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.341249.1578386676000.14255.1578409080255%40Atlassian.JIRA.


Jira (PUP-10218) Puppet incorrectly detecting stale pidfile

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


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10218  
 
 
  Puppet incorrectly detecting stale pidfile   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Night's Watch  
 

  
 
 
 
 

 
 
 

 
 
 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.341249.1578386676000.14253.1578408600135%40Atlassian.JIRA.


Jira (PUP-10219) Unable to create local user when username already exists in Windows domain

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10219  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to create local user when username already exists in Windows domain   
 

  
 
 
 
 

 
 Nit, in ruby it's preferable to use sid.domain.casecmp(Puppet::Util::Windows::ADSI.computer_name) == 0 since it doesn't make 2 copies of the string. I recently enabled the rubocop rule to check for that.  
 

  
 
 
 
 

 
 
 

 
 
 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.341094.157829589.14183.1578406440355%40Atlassian.JIRA.


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

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-10148  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Include X-Puppet-Profiling header   
 

  
 
 
 
 

 
 Additional fix merged in https://github.com/puppetlabs/puppet/commit/912f02edab7e760ef076add99fe13da74c2cf028  
 

  
 
 
 
 

 
 
 

 
 
 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.14163.1578405900123%40Atlassian.JIRA.


Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity

2020-01-07 Thread Thomas Hallgren (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Hallgren commented on  PUP-10210  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet fails with JSON error when a fact value equals Infinity   
 

  
 
 
 
 

 
 I agree. Float["infinity"], Float["-infinity"], and Float["NaN"] should be made to match their corresponding float values.  
 

  
 
 
 
 

 
 
 

 
 
 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.340709.1577387077000.14149.1578401580159%40Atlassian.JIRA.


Jira (PUP-10219) Unable to create local user when username already exists in Windows domain

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


 
 
 
 

 
 
 

 
   
 Gabriel Nagy moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10219  
 
 
  Unable to create local user when username already exists in Windows domain   
 

  
 
 
 
 

 
Change By: 
 Gabriel Nagy  
 
 
Affects Version/s: 
 puppet-agent 6.3.0  
 
 
Key: 
 PA PUP - 3063 10219  
 
 
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341094.157829589.14144.1578400620183%40Atlassian.JIRA.


Jira (PUP-10171) Cannot change flavor on installed dnf module

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


 
 
 
 

 
 
 

 
   
 Gabriel Nagy assigned an issue to Gabriel Nagy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10171  
 
 
  Cannot change flavor on installed dnf module   
 

  
 
 
 
 

 
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.338977.157606706.14139.1578400560129%40Atlassian.JIRA.


Jira (PUP-10177) yum provider does not allow array of strings

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


 
 
 
 

 
 
 

 
   
 Gabriel Nagy assigned an issue to Gabriel Nagy  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10177  
 
 
  yum provider does not allow array of strings   
 

  
 
 
 
 

 
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.339935.157660745.14136.1578400500399%40Atlassian.JIRA.


Jira (PUP-5921) Deprecate source_permissions

2020-01-07 Thread Maximilian Philipps (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Maximilian Philipps commented on  PUP-5921  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate source_permissions   
 

  
 
 
 
 

 
 I don't understand why source_permissions is deprecated. "it doesn't make sense for environments (including PE) that use git for the backend (user/group aren't managed by git)" and if the backend isn't git? Also source_permissions is really useful for mode sensitive files, even if the backend is git.  I am not aware that source may only point to git repositories.  
 

  
 
 
 
 

 
 
 

 
 
 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.117270.1455758203000.14130.1578399360201%40Atlassian.JIRA.


Jira (FACT-2211) mountpoints fact for OSX

2020-01-07 Thread Florin Dragos (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Florin Dragos assigned an issue to Florin Dragos  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2211  
 
 
  mountpoints fact for OSX   
 

  
 
 
 
 

 
Change By: 
 Florin Dragos  
 
 
Assignee: 
 Florin Dragos  
 

  
 
 
 
 

 
 
 

 
 
 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.338917.1576053926000.14109.1578398700138%40Atlassian.JIRA.


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

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau assigned an issue to Mihai Buzgau  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Assignee: 
 Mihai Buzgau  
 

  
 
 
 
 

 
 
 

 
 
 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.338022.1575566536000.14101.1578397920775%40Atlassian.JIRA.


Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity

2020-01-07 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-10210  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet fails with JSON error when a fact value equals Infinity   
 

  
 
 
 
 

 
 Thomas Hallgren yes, that works. We should allow a way to match infinity with a type as well - right now you cannot do that - perhaps Float["infinity"]? Which I guess would also work if you want to create an instance.  
 

  
 
 
 
 

 
 
 

 
 
 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.340709.1577387077000.14088.1578397500155%40Atlassian.JIRA.


Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1903  
 
 
  facter doesn't recognize EC2 i3.metal instances   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.291000.1547052341000.13968.1578394380339%40Atlassian.JIRA.


Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1903  
 
 
  facter doesn't recognize EC2 i3.metal instances   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 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.291000.1547052341000.13966.1578394380251%40Atlassian.JIRA.


Jira (PUP-9966) add acceptance tests for package gem provider

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9966  
 
 
  add acceptance tests for package gem provider   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.321292.1565960513000.13961.1578394320195%40Atlassian.JIRA.


Jira (FACT-2195) facter not returning correct 'os.windows.system32' fact on Windows Server 2012 R2

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2195  
 
 
  facter not returning correct 'os.windows.system32' fact on Windows Server 2012 R2   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.338159.1575596749000.13958.1578394200139%40Atlassian.JIRA.


Jira (PUP-10171) Cannot change flavor on installed dnf module

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10171  
 
 
  Cannot change flavor on installed dnf module   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.338977.157606706.13947.1578393240181%40Atlassian.JIRA.


Jira (PUP-10171) Cannot change flavor on installed dnf module

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10171  
 
 
  Cannot change flavor on installed dnf module   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 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.338977.157606706.13945.1578393240171%40Atlassian.JIRA.


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

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 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.338022.1575566536000.13935.1578393060531%40Atlassian.JIRA.


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

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.338022.1575566536000.13937.1578393060618%40Atlassian.JIRA.


Jira (FACT-2250) Facter ignores signals while waiting for external commands to run

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2250  
 
 
  Facter ignores signals while waiting for external commands to run   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 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.339252.1576183486000.13909.1578391800143%40Atlassian.JIRA.


Jira (PUP-10177) yum provider does not allow array of strings

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10177  
 
 
  yum provider does not allow array of strings   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339935.157660745.13889.1578390600220%40Atlassian.JIRA.


Jira (PUP-10177) yum provider does not allow array of strings

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10177  
 
 
  yum provider does not allow array of strings   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.339935.157660745.13892.1578390600271%40Atlassian.JIRA.


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

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.13886.1578390480127%40Atlassian.JIRA.


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

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 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.13885.1578390480073%40Atlassian.JIRA.


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

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.340538.1576868667000.13878.1578390120155%40Atlassian.JIRA.


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

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR NW  -  Triage  2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.13880.1578390120243%40Atlassian.JIRA.


Jira (PUP-1537) Dpkg package provider misbehaving for held package with specific version

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1537  
 
 
  Dpkg package provider misbehaving for held package with specific version   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 NW - 2019-10-16, NW - 2019-10-30, NW - 2019-11-13, 2019-11-27, 2019-12-11, 2019-12-24 , NW - 2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.24894.1391021944000.13854.1578389162115%40Atlassian.JIRA.


Jira (PUP-9465) group resource type misunderstands/misuses libuser

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9465  
 
 
  group resource type misunderstands/misuses libuser   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18, NW - 2019-10-02, NW - 2019-10-16, NW - 2019-10-30, NW - 2019-11-13, 2019-11-27, 2019-12-11, 2019-12-24 , NW - 2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.293306.1548368109000.13840.1578389161523%40Atlassian.JIRA.


Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9719  
 
 
  Cannot run Puppet Agent as Administrator if first PA run is done as System   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-25, PR - 2019-07-10, PR - 2019-07-23, NW - 2019-08-07, NW - 2019-08-21, NW - 2019-09-03, NW - 2019-09-18, NW - 2019-10-02, NW - 2019-10-16, NW - 2019-10-30, NW - 2019-11-13, 2019-11-27, 2019-12-11, 2019-12-24 , NW - 2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.310162.1558726819000.13827.1578389161060%40Atlassian.JIRA.


Jira (PUP-10117) Read /etc/passwd once per user resource if forcelocal is set

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10117  
 
 
  Read /etc/passwd once per user resource if forcelocal is set   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 2019-11-27, 2019-12-11, 2019-12-24 , NW - 2020-01-22  
 

  
 
 
 
 

 
 
 

 
 
 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.333053.1572524314000.13857.1578389162247%40Atlassian.JIRA.


Jira (PUP-10210) puppet fails with JSON error when a fact value equals Infinity

2020-01-07 Thread Thomas Hallgren (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Hallgren commented on  PUP-10210  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet fails with JSON error when a fact value equals Infinity   
 

  
 
 
 
 

 
 Float::INFINITY is of type Float, both in Ruby and in most other languages. I don't see anything wrong in treating it as a Float in Pcore too. Further more, many serialization formats, including YAML, can handle both NaN and infinity. The way I see it, this is only a problem when serializing using JSON and as such, it doesn't motivate a new data type. The best solution is to improve the Pcore rich-data serialization specifically for JSON so that the values NaN, infinity, and negative infinity are serialized using:  
 
 
 
 
 { "__ptype": "Float", "__pvalue": "NaN"},{ "__ptype": "Float", "__pvalue": "infinity"}, { "__ptype": "Float", "__pvalue": "-infinity"}
  
 
 
 
  i.e. no new data type, just force use of strings on the Float data type.  
 

  
 
 
 
 

 
 
 

 
 
 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 

Jira (PUP-10218) Puppet incorrectly detecting stale pidfile

2020-01-07 Thread Marcin Deranek (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcin Deranek created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10218  
 
 
  Puppet incorrectly detecting stale pidfile   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.11.1  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 pidlock.patch  
 
 
Created: 
 2020/01/07 12:44 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Marcin Deranek  
 

  
 
 
 
 

 
 Puppet Version: 6.11.1 Puppet Server Version: 6.11.1 OS Name/Version: CentOS 7 When Puppet agent is incorrectly terminated (eg. killed by KILL signal) it might have a problem in detecting stale PID file. The code in question is this:  
 
 
 
 
 puppet/lib/ruby/vendor_ruby/puppet/util/pidlock.rb  
 
 
 
 
 def clear_if_stale  
 
 
 begin  
 
 
   Process.kill(0, lock_pid)  
  

Jira (FACT-2220) disks fact for AIX

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


 
 
 
 

 
 
 

 
   
 Bogdan Irimie assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-2220  
 
 
  disks fact for AIX   
 

  
 
 
 
 

 
Change By: 
 Bogdan Irimie  
 
 
Assignee: 
 Mihai Buzgau  
 

  
 
 
 
 

 
 
 

 
 
 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.338926.157605417.13780.1578384240123%40Atlassian.JIRA.


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

2020-01-07 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Team: 
 Night's Watch  
 

  
 
 
 
 

 
 
 

 
 
 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.13769.1578384000328%40Atlassian.JIRA.