Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored

2019-10-02 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PDB-2487  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored   
 

  
 
 
 
 

 
 The workaround used by Support is a single:  
 
 
 
 
 su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c 'TRUNCATE resource_events'"
  
 
 
 
  and then a scheduled:  
 
 
 
 
 su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c \"DELETE FROM resource_events WHERE timestamp < NOW() - INTERVAL '2 days'\""';
  
 
 
 
  like:  
 
 
 
 
 cron { 'sudo_resource_events_ttl':  
 
 
   ensure  => 'present',  
 
 
   command => 'su - pe-postgres -s /bin/bash -c "/opt/puppetlabs/server/bin/psql -d pe-puppetdb -c \"DELETE FROM resource_events WHERE timestamp < NOW() - INTERVAL \'2 days\'\""',  
 
 
   hour=> ['8'],  
 
 
   minute  => ['0'],  
 
 
   target  => 'root',  
 
 
   user=> 'root',  
 
 

Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored

2019-10-02 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PDB-2487  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored   
 

  
 
 
 
 

 
 Does that mean in a .z of Lovejoy? Because this is a high-impact problem for the above PE users.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10056) a warn function, to compliment fail, so it will be seen in agent log

2019-10-01 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-10056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: a warn function, to compliment fail, so it will be seen in agent log   
 

  
 
 
 
 

 
 I have been relaying for a user with a PE ticket, so I've asked them to reply here to remove me form the middle ...  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10056) a warn function, to compliment fail, so it will be seen in agent log

2019-10-01 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-10056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: a warn function, to compliment fail, so it will be seen in agent log   
 

  
 
 
 
 

 
 Works on the command line with puppet apply:  
 
 
 
 
 [root@pe-201911-agent ~]# puppet apply -e "warning('TJK')"  
 
 
 Warning: Scope(Class[main]): TJK  
 
 
 Notice: Compiled catalog for pe-201911-agent.puppetdebug.vlan in environment production in 0.01 seconds  
 
 
 Notice: Applied catalog in 0.01 seconds
  
 
 
 
  But not via a service run :  
 
 
 
 
 node 'pe-201911-agent.puppetdebug.vlan' {  
 
 
   notify{"YO!":}  
 
 
   warning('TJK')  
 
 
 }
  
 
 
 
   
 
 
 
 
 Oct  1 15:20:04 pe-201911-agent puppet-agent[28915]: Caught TERM; exiting  
 
 
 Oct  1 15:20:04 pe-201911-agent systemd: Stopping Puppet agent...  
   

Jira (PUP-10056) a warn function, to compliment fail, so it will be seen in agent log

2019-09-30 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-10056  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: a warn function, to compliment fail, so it will be seen in agent log   
 

  
 
 
 
 

 
 Support user request.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10056) a warn function, to compliment fail, so it will be seen in agent log

2019-09-30 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10056  
 
 
  a warn function, to compliment fail, so it will be seen in agent log   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/09/30 3:45 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Oh, darn, there really should be a warn function, to compliment fail, so it will be seen in agent log.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-10017  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
 For a more extreme example:  
 
 
 
 
 class rrr {  
 
 
   file { '/fail/file_in_rrr.txt':  
 
 
 content => 'hello',  
 
 
   }  
 
 
 }  
 
 
    
 
 
 class ddd {  
 
 
   require rrr  
 
 
   range(1,99).each |$n| {  
 
 
 file { "/tmp/file_${n}_in_ddd.txt":  
 
 
   content => 'hello',  
 
 
 }  
 
 
   }  
 
 
 }  
 
 
  

Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-10017  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
 The above is implemented in the PR.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10017  
 
 
  Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 without_coalesce.png  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10017  
 
 
  Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 

  
 
 
 
 

 
 When a Class has a failed dependency, every individual resource in the class generates a notice level message about the dependency failure and a warning level message about skipping the resource, as well as a skip event in the report.  This can generate a large number of messages and a large report if there are many dependencies, or multiple layers of dependencies. At large-node and/or large-code scale, one dependency failure can create an overwhelming number of warnings ... obscuring the root cause and increasing the use of system resources required to process and store the resulting reports.  If possible, all of the skipped resources should be collapsed into the containing class and the messages and skip event should be done at the class level.  It looks like the most recent work on this was done in PUP-3930 and commit 32e2bf2.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
   

Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10017  
 
 
  Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 with_coalesce.png  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10017  
 
 
  Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 with_and_without_coalesce.png  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10019) file resource checks source even if the file exists and replace is false

2019-09-13 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10019  
 
 
  file resource checks source even if the file exists and replace is false   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.4.3  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/09/13 11:42 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Puppet Version: 6.4.3 and presumably others Puppet Server Version: NA OS Name/Version: NA Desired Behavior: Skip the use of source if the file exists and replace is false. Actual Behavior:  
 
 
 
 
 [root@pe-201911-master-ha ~]# cat a.pp   
 
 
 file { '/tmp/test.txt':  
 
 
   ensure => present,  
 
 
   replace => false,  
 
 
   source => "/tmp/source.txt",  
 
 
 

Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-13 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-10017  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
 A (let's say) suppress_inherited_dependency_failures option would affect the logic here: https://github.com/puppetlabs/puppet/blob/5.5.x/lib/puppet/transaction.rb#L285 https://github.com/puppetlabs/puppet/blob/5.5.x/lib/puppet/transaction.rb#L398 When suppress_inherited_dependency_failures is true ...  
 
 
 
 
 if a resource has a parent  
 
 
   if the parent is a class  
 
 
 if the class has a dependency relationship  
 
 
   if the dependent is a failed resource (or the dependent is a class containing a failed resource)  
 
 
 mark the class as failed (and mark the resource as failed)  
 
 
   report (just once) that we are skipping the containing class of the resource  suppress the report that we are skipping the resource  
 
 
 
  Use case when enabled: given a failure in a resource that is required by a class, a user would see (one) class failure in the report, and could perform a puppet run without suppress_inherited_dependency_failures to identify the resources in the class that were skipped, if necessary. But since the solution to the dependency failure is to resolve the failure in the dependent resource, that would only be valuable for auditing everything that was skipped: the user's attention should be focused on the failed resource (in the example, File['/impossible/xxx.txt']).  
 

  
 
 
 
 

 
 
 

 

Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-13 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-10017  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
 Implementing this should also address the high volume of skips associated with resources using the schedule metaparameter when the run is outside the schedule window.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

2019-09-11 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows   
 

  
 
 
 
 

 
 I defer to a principle engineer about principles  That's reasonable, especially if we actually fix this in P7.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-10017) Collapse dependency failures into Class level failures

2019-09-11 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-10017  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Collapse dependency failures into Class level failures   
 

  
 
 
 
 

 
 Given one class that requires another ...  
 
 
 
 
 class xxx {  
 
 
   file { '/impossible/xxx.txt':  
 
 
     content => 'hello',  
 
 
   }  
 
 
 }  
 
 
    
 
 
 class www {  
 
 
   require xxx  
 
 
   file { '/tmp/yyy.txt':  
 
 
     content => 'hello',  
 
 
   }  
 
 
   file { '/tmp/zzz.txt':  
 
 
     content => 'hello',  
 
 
   }  
 
 

Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

2019-09-10 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows   
 

  
 
 
 
 

 
 I realize this may be a matter of principle ... but I'm imagining trying to explain this to a user in documentation or a support ticket.  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

2019-09-10 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows   
 

  
 
 
 
 

 
 Yes  but it is counterintuitive that ... On Windows, the gem provider installs into Puppet On Linux, the gem provider installs into system Ruby On both Linux and Windows, the puppet_gem provider installs into 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.125405.1459986358000.93024.1568160120533%40Atlassian.JIRA.


Jira (PUP-9974) allow_virtual => true matches too much for dpkg provider

2019-08-23 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9974  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: allow_virtual => true matches too much for dpkg provider   
 

  
 
 
 
 

 
 Maybe:  
 
 
 
 
   if @resource.allow_virtual?  
 
 
 query_output = dpkgquery(  
 
 
   "-W",  
 
 
   "--showformat",  
 
 
   self.class::DPKG_QUERY_PROVIDES_FORMAT_STRING  
 
 
 )  
 
 
 virtual_package_line = query_output.lines.find { |line|  
 
 
   if matched = line.match(/\[(?.*)\]/)  
 
 
 if matched[:package_provides].split(',').include?(@resource[:name])  
 
 
   matched  
 
 
 end  
 
 
   end  
 
 
 }  
 
 
 if 

Jira (PUP-9750) optionally add pe_version to server_facts

2019-08-23 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: optionally add pe_version to server_facts   
 

  
 
 
 
 

 
 Switched to `peserverversion` to match the other keys in server_facts, which do not use underscores. Reverting would be a trivial search and replace.  
 

  
 
 
 
 

 
 
 

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


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

2019-08-16 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9966  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: add acceptance tests for package gem provider   
 

  
 
 
 
 

 
 https://github.com/tkishel/puppet/blob/PUP-9966_acceptance_tests_package_gem_provider/acceptance/tests/provider/package/gem.rb  
 

  
 
 
 
 

 
 
 

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


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

2019-08-16 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 master.txt  
 

  
 
 
 
 

 
 
 

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


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

2019-08-16 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 agent.txt  
 

  
 
 
 
 

 
 
 

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


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

2019-08-16 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9966  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: add acceptance tests for package gem provider   
 

  
 
 
 
 

 
 Even with a corrected PATH (with our paths post-pended) puppet is executed via the system Ruby when it is instaled ... but only on a host with just 'agent' not on a host with 'master' and 'agent':  
 
 
 
 
 # master:  
 
 
 execve("/opt/puppetlabs/puppet/bin/puppet", ["/opt/puppetlabs/puppet/bin/puppe"..., "apply", "package_gem_colorize_present.pp"], [/* 22 vars */]) = 0  
 
 
 brk(NULL)   = 0x16b7000
  
 
 
 
   
 
 
 
 
 # agent  
 
 
 execve("/usr/local/sbin/ruby", ["ruby", "/opt/puppetlabs/bin/puppet", "apply", "package_gem_colorize_present.pp"], [/* 21 vars */]) = -1 ENOENT (No such file or directory)  
 
 
 execve("/usr/local/bin/ruby", ["ruby", "/opt/puppetlabs/bin/puppet", "apply", "package_gem_colorize_present.pp"], [/* 21 vars */]) = -1 ENOENT (No such file or directory)  
 
 
 execve("/sbin/ruby", ["ruby", "/opt/puppetlabs/bin/puppet", "apply", "package_gem_colorize_present.pp"], [/* 21 vars */]) = -1 ENOENT (No such file or directory)  
 
 
 execve("/bin/ruby", ["ruby", "/opt/puppetlabs/bin/puppet", "apply", "package_gem_colorize_present.pp"], [/* 21 vars */]) = 0  
 
 
 brk(NULL)   = 0x82b000
  
 

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

2019-08-16 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/08/16 6:01 AM  
 
 
Environment: 
 Beaker  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Desired Behavior: Acceptance test coverage for the gem provider of the package resource.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

2019-08-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows   
 

  
 
 
 
 

 
 I remember there being a concern with this change similar to "but what about users who depend on this bug to mange Puppet Ruby gems (instead of using the puppet_gem provider" but I don't thank that is common or valid, and they have/should use the the puppet_gem provider.  BTW: I've implemented Ethan's recommendation on 2017/01/04 3:09 PM via the command attribute in PUP-6488. I'm writing acceptance tests for PUP-8949 now, and once those are complete, I'll re-review this and add a test for this ...  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-08-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8736  
 
 
  /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Comment: 
 9628  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-08-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8736  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
 9628  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-08-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8736  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
 There is a collision here with a File resource that recursively purges this directory in the device_managar module that needs to be addressed. Details in a MODULES ticket ...  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows

2019-08-06 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6382  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add "Automatic (delayed start)" as option for Service Resource on Windows   
 

  
 
 
 
 

 
 Maybe ...  
 
 
 
 
 # Service config codes  
 
 
 # https://docs.microsoft.com/en-us/windows/win32/api/winsvc/nf-winsvc-changeserviceconfig2w  
 
 
 SERVICE_CONFIG_DESCRIPTION  = 0x0001  
 
 
 SERVICE_CONFIG_FAILURE_ACTIONS  = 0x0002  
 
 
 SERVICE_CONFIG_DELAYED_AUTO_START   = 0x0003  
 
 
 SERVICE_CONFIG_FAILURE_ACTIONS_FLAG = 0x0004  
 
 
 SERVICE_CONFIG_SERVICE_SID_INFO = 0x0005  
 
 
 SERVICE_CONFIG_REQUIRED_PRIVILEGES_INFO = 0x0006  
 
 
 SERVICE_CONFIG_PRESHUTDOWN_INFO = 0x0007  
 
 
 SERVICE_CONFIG_TRIGGER_INFO = 0x0008  
 
 
 SERVICE_CONFIG_PREFERRED_NODE   = 0x0009  
 
 
 SERVICE_CONFIG_LAUNCH_PROTECTED = 0x0012  
 
 
   

Jira (PUP-9337) Puppet sets permissions for Puppet files every run

2019-07-29 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9337  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet sets permissions for Puppet files every run   
 

  
 
 
 
 

 
 This is marked as fixed in Puppet 5.5.12 so PE 2018.1.8 (which ships with 5.5.14) or newer, as per ... https://puppet.com/docs/pe/2019.1/component_versions_in_recent_pe_releases.html  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-9563) Using max_queued_requests, agents return to originally scheduled run times

2019-07-25 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9563  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using max_queued_requests, agents return to originally scheduled run times   
 

  
 
 
 
 

 
 So  ... would the puppet agent receiving the 503 need to send a signal to the puppet service to reset the timer in the following?   https://github.com/puppetlabs/puppet/blob/5.5.x/lib/puppet/daemon.rb https://github.com/puppetlabs/puppet/blob/5.5.x/ext/windows/service/daemon.rb  
 

  
 
 
 
 

 
 
 

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


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

2019-07-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8949  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Package pip provide won't work with ensure latest and custom index   
 

  
 
 
 
 

 
 https://github.com/puppetlabs/puppet/pull/7633  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows

2019-07-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6382  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add "Automatic (delayed start)" as option for Service Resource on Windows   
 

  
 
 
 
 

 
 We could implement this with something like ...   lib/puppet/type/service.rb  
 
 
 
 
  newproperty(:enable, :required_features => :enableable) do  
 
 
   ...  
 
 
  newvalue(:delayed, :event => :service_delayed_start) do  
 
 
provider.delayed_start  
 
 
  end
  
 
 
 
  lib/puppet/provider/service/windows.rb  
 
 
 
 
   def delayed_start  
 
 
 enable  
 
 
 Puppet::Util::Windows::Service.set_startup_mode_delayed( @resource[:name] )  
 
 
   rescue => detail  
 
 
 raise Puppet::Error.new(_("Cannot enable %{resource_name} for delayed start, error was: %{detail}") % { resource_name: @resource[:name], detail: detail }, detail )  
 
 
   end
  
 
 

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

2019-07-23 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8949  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Package pip provide won't work with ensure latest and custom index   
 

  
 
 
 
 

 
 Let me set up a test ...  
 

  
 
 
 
 

 
 
 

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


Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)

2019-07-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9471  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User management fails on MacOS 10.14 (Mojave)   
 

  
 
 
 
 

 
 Ahh, thx!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9471) User management fails on MacOS 10.14 (Mojave)

2019-07-16 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9471  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User management fails on MacOS 10.14 (Mojave)   
 

  
 
 
 
 

 
 Geoff Nichols I don't think this is resolved, as Puppet, Inc. is currently suffering from the same issue. I was unable to workaround this by whitelisting puppet  I had to whitelist Terminal That should not resolve the issue when run via a LaunchDaemon Adding launchd (if even possible) would be a security issue. Also, we need to audit our other binaries, like (pxp-agent}} Finally, we need to provide guidance on how to automate this (if even possible) at scale. or document that it cannot be automated to save users frustration .    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open

2019-07-11 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1936  
 
 
  facter -p segfaults with facts that call open-uri.open   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 

  
 
 
 
 

 
 *Puppet Version:* 6.0.9*Facter Version:* 3.12.4 (commit ce9452fd2d15ed91eed9b8cc7823af783c9275a8) *OS Name/Version:* Windows 2012This custom fact succeeds on Linux but segfaults on Windows ... but only when calling {{facter -p}} not with {{puppet facts}} or {{puppet agent -t}} {code}require 'open-uri'require 'json'require 'timeout'Facter.add('test') do  response = nil  beginurl = ''Timeout::timeout(4) do  response = open(url).readend  rescuenil  end  if !response.to_s.empty?result = JSON.parse(response)setcode do  result['ip']end  endend{code} {code}C:\Users\Administrator>facter -p C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/protocol.rb:45: [BUG] Segmentation fault ruby 2.5.3p105  ( 2018-10-18 revision 65156) [x64-mingw32]  -- Control frame information --- c:0082 p: s:0522 e:000521 CFUNC  :wait_readable c:0081 p:0093 s:0517 e:000516 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/protocol.rb:45 c:0080 p:0557 s:0510 E:002178 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/http.rb:981 c:0079 p:0004 s:0497 e:000496 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/http.rb:920 c:0078 p:0029 s:0493 e:000492 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/net/http.rb:909 c:0077 p:0521 s:0489 e:000488 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:337 c:0076 p:0017 s:0468 e:000467 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:755 c:0075 p:0029 s:0461 e:000460 BLOCK  C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:226 [FINISH] c:0074 p: s:0458 e:000457 CFUNC  :catch c:0073 p:0365 s:0453 E:001398 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:224 c:0072 p:0328 s:0438 e:000437 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:165 c:0071 p:0018 s:0426 e:000425 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:735 c:0070 p:0071 s:0420 e:000419 METHOD C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/open-uri.rb:35 c:0069 p:0007 s:0412 e:000411 BLOCK  C:/ProgramData/PuppetLabs/puppet/cache/lib/facter/test.rb:11 c:0068 p:0030 s:0409 E:002298 BLOCK  C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/timeout.rb:93 c:0067 p:0005 s:0403 e:000402 BLOCK  C:/Program Files/Puppet 

Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open

2019-07-11 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1936  
 
 
  facter -p segfaults with facts that call open-uri.open   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 seg.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1936) facter -p segfaults with facts that call open-uri.open

2019-07-11 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1936  
 
 
  facter -p segfaults with facts that call open-uri.open   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Windows  
 
 
Created: 
 2019/07/11 12:23 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Puppet Version: 6.0.9 Facter Version: 3.12.4 (commit ce9452fd2d15ed91eed9b8cc7823af783c9275a8)  OS Name/Version: Windows 2012 This custom fact succeeds on Linux but segfaults on Windows ... but only when calling facter -p not with puppet facts or puppet agent -t  
 
 
 
 
 require 'open-uri'  
 
 
 require 'json'  
 
 
 require 'timeout'  
 
 
    
 
 
 Facter.add('test') do  
 
 
   

Jira (PUP-9820) managing a File user or group or mode breaks require on Windows

2019-07-11 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9820  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: managing a File user or group or mode breaks require on Windows   
 

  
 
 
 
 

 
 Caused by a call to validate here: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/file/windows.rb#L85 Which calls supports_acl? which includes the "Failed to get volume information" error here: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/security.rb#L163  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9820) managing a File user or group or mode breaks require on Windows

2019-07-11 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9820  
 
 
  managing a File user or group or mode breaks require on Windows   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Windows  
 
 
Created: 
 2019/07/11 11:13 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 
 
Puppet Version:* 6.0.9 
Puppet Server Version: 2019.0.3 
OS Name/Version: Windows 2002 
 A File resource that depends (via require) on another resource to create the volume of the file fails to honor the dependency when managing owner, group, and/or mode ... but only on Windows where it generates a Validation ... failed error.  
 
 
 
 
 node 'pe-201903-agent-win2012' {  
 
 
   exec { 'Make Drive':  
 
 
 command  => 'sleep 5',  
 
 
 provider => powershell,  
   

Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

2019-06-25 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9794  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)   
 

  
 
 
 
 

 
 This is an unsupported method of patching:   
 
 
 
 
 # a.pp  
 
 
 file_line { 'PUP-9794':  
 
 
   path  => '/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/package_targetable.rb',  
 
 
   line  => "require 'puppet/provider/package' # PUP-9794",  
 
 
   after => "# Rather, .*",  
 
 
 }
  
 
 
 
   
 
 
 
 
 root@ip-10-0-0-1:~# puppet apply a.pp   
 
 
 Error: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)  
 
 
 Error: Facter: error while resolving custom facts in /opt/puppetlabs/puppet/cache/lib/facter/package_provider.rb: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)  
 
 
 Notice: Compiled catalog for ip-10-0-0-1.us-west-2.compute.internal in environment production in 0.02 seconds  
 
 

Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

2019-06-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9794  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)   
 

  
 
 
 
 

 
 The AMI used to test is: ami-1ee65166  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9790) undefined method `pip_version' with pip3 provider

2019-06-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9790  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: undefined method `pip_version' with pip3 provider   
 

  
 
 
 
 

 
 Found, fixed, and spec updated: https://github.com/puppetlabs/puppet/pull/7593 Even when I added a receive count to the older/incorrect stub, the test passes?  
 
 
 
 
 allow(@provider).to receive(:pip_version).with("/fake/bin/pip").and_return('1.0.1').exactly(99).times
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

2019-06-21 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9794  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)   
 

  
 
 
 
 

 
 https://github.com/puppetlabs/puppet/pull/7590  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)

2019-06-21 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9794  
 
 
  Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.5.0  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/06/21 12:52 PM  
 
 
Environment: 
  
 
 
 
 
 puppet -V; puppetserver -v; /opt/puppetlabs/puppet/bin/ruby -v  
 
 
 6.5.0  
 
 
 puppetserver version: 6.4.0  
 
 
 ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux]
  
 
 
 
  Triggered by package_provider fact in puppetlabs-stdlib  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Puppet Version: 6.5.0 Puppet Server 

Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH

2019-06-20 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gem provider should allow alternative gem command; should not rely on $PATH   
 

  
 
 
 
 

 
 I've added a commit to the pending PR for the puppetserver_gem module that resolves this: https://github.com/puppetlabs/puppetlabs-puppetserver_gem/pull/27 The change adds:  
 
 
 
 
   def self.provider_command  
 
 
 command(:puppetservercmd)  
 
 
   end
  
 
 
 
  (This is an example of why I suggested the puppetserver_gem provider be moved from a module to Puppet Core.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet 

Jira (PUP-9750) optionally add pe_version to server_facts

2019-06-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: optionally add pe_version to server_facts   
 

  
 
 
 
 

 
 See also: https://puppet.com/docs/puppet/latest/lang_facts_and_builtin_vars.html#serverfacts-variable `serverversion` is the current version of Puppet on the Puppet master, so maybe server_facts['pe_version' should be server_facts['peserverversion` ? That would avoid a collision with the PE fact or function names, and the fact names in the puppetlabs-stdlib module.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9750) optionally add pe_version to server_facts

2019-06-13 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: optionally add pe_version to server_facts   
 

  
 
 
 
 

 
 This sets server_facts['pe_version'] which sets/overrides the pe_version fact ... but only in the catalog compiled by the server:  
 
 
 
 
 [root@pe-201818-master ~]# cat /etc/puppetlabs/code/environments/production/manifests/site.pp  
 
 
 node default {  
 
 
   $gpev = get_pe_version()  
 
 
   if $gpev { notify { "PE Version ${gpev} | ${server_facts['pe_version']} | ${pe_version}": } }  
 
 
 }
  
 
 
 
   
 
 
 
 
 [root@pe-201818-agent ~]# puppet agent -t  
 
 
 Info: Using configured environment 'production'  
 
 
 Info: Retrieving pluginfacts  
 
 
 Info: Retrieving plugin  
 
 
 Info: Retrieving locales  
 
 
 Info: Loading facts  
 
 
  

Jira (PUP-9750) optionally add pe_version to server_facts

2019-06-12 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: optionally add pe_version to server_facts   
 

  
 
 
 
 

 
 If this PR is approved (and added to Puppet 7) then we could add this function to puppetlabs-stdlib ...  
 
 
 
 
 # This needs to be a function rather than updating the 3.x `pe_version` fact.  
 
 
 #  
 
 
 # In Puppet 3.x, PE is a property of the agent.  
 
 
 # In Puppet 4.x and newer, PE is a property of the compiling master.  
 
 
 # In Puppet 4.x to 6.x, inspect the `pe_version` file on the compiling master.  
 
 
 # In Puppet 7.x and newer, inspect server_facts['pe_version'].  
 
 
    
 
 
 Puppet::Functions.create_function(:get_pe_version) do  
 
 
   def get_pe_version  
 
 
 scope = closure_scope  
 
 
 facts = scope['facts']  
 
 
    
 
 
 if Puppet::Util::Package.versioncmp(facts['puppetversion'], '3.9.9') < 0  
   

Jira (PUP-9750) optionally add pe_version to server_facts

2019-06-12 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9750  
 
 
  optionally add pe_version to server_facts   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/06/12 12:17 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Members of the Puppet Community have requested a standardized best practice to determine if a Puppet Agent is a PE or FOSS Puppet Agent. Since Puppet 4.x, there is no concept of a PE or FOSS Puppet Agent, but a Puppet Agent can be served a catalog by a PE or FOSS Puppet Server. A non-empty pe_version fact would both differentiate between PE or FOSS, but would allow for conditional code depending upon the specific version of PE. The pe_version fact is available in Puppet / PE 3.x. The pe_compiling_server_version function (which calls pe_server_version) is available on a PE Puppet Server after PE 3.x, but is not available on a FOSS Puppet Server, requiring the use of the is_function_available} function to avoid generating an error when calling {{pe_compiling_server_version function on a FOSS Puppet Server. The is_function_available function is itself now deprecated.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
  

Jira (BOLT-1166) Windows compatibility for orchestrator_client-ruby persistent http connections

2019-05-16 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  BOLT-1166  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows compatibility for orchestrator_client-ruby persistent http connections
 

  
 
 
 
 

 
 Docs: https://puppet.com/docs/pe/2018.1/bolt_configure_orchestrator.html#adjust-the-orchestrator-configuration-files "Set up the orchestrator API for Bolt in the same configuration file that is used for PE client tools" is vague.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH

2019-05-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6488  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Gem provider should allow alternative gem command; should not rely on $PATH   
 

  
 
 
 
 

 
 Release note ready for review. Thanks for your help with this!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH

2019-05-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6488  
 
 
  Gem provider should allow alternative gem command; should not rely on $PATH   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Release Notes Summary: 
 Package providers now support a targeted package management commandPuppet package providers use `which` to find the first package management command (for example: `gem` for Ruby, `pip` for Python) in the `PATH`. That prevented Puppet from managing other installations of the same software.This release adds a `targetable` feature to the Package type, allowing Package providers to implement a `command` attribute. The gem and pip providers now implement that attribute.```package { 'colorize':  name => 'colorize',  provider => gem,}package { 'colorize-opt':  name => 'colorize',  provider => gem,  command  => '/opt/ruby/bin/gem',}```This feature allows Puppet to manages the packages in software collections (multiple versions of the same software) such as Red Hat Software Collections.PUP-1082, PUP-6488  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

   

Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-05-14 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8736  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
 Could we move/replace: /opt/puppetlabs/puppet/cache/devices/DEVICE/ssl with a symlink to: /etc/puppetlabs/puppet/devices/ssl/DEVICE ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1922) Log file being spammed with the error: floppy: error -5 while reading block 0

2019-05-10 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  FACT-1922  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Log file being spammed with the error: floppy: error -5 while reading block 0   
 

  
 
 
 
 

 
 On CentOS/RedHat, the log entry is blk_update_request: I/O error, dev fd0, sector 0 Those error messages can be triggered by facter filesystems or facter mountpoints or an operating system command such as fdisk -l that enumerates all available block devices when the floppy driver is loaded but there is no floppy device. Testing show that if I disable the floppy module with rmmod floppy the error messages stop. Remarkably, if I re-enable the floppy module with modprobe floppy, the errors messages do not reoccur until after the next reboot. Search the internet for blacklist floppy for solutions at the operating system level.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1922) Log file being spammed with the error: floppy: error -5 while reading block 0

2019-05-10 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1922  
 
 
  Log file being spammed with the error: floppy: error -5 while reading block 0   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Affects Version/s: 
 PE 2018.1.5  
 
 
Affects Version/s: 
 FACT 3.11.6  
 
 
Key: 
 ENTERPRISE FACT - 1256 1922  
 
 
Project: 
 Puppet Enterprise Facter  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

Jira (FACT-1354) Facter ec2_userdata handles binary data incorrectly

2019-05-09 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  FACT-1354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Facter ec2_userdata handles binary data incorrectly   
 

  
 
 
 
 

 
 Might there be a way to provide guidance to detect the extra bytes and strip them?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0

2019-04-26 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0   
 

  
 
 
 
 

 
 No problem!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0

2019-04-25 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0   
 

  
 
 
 
 

 
 Jean Bond The release notes I suggested have been replaced with the release notes for PUP-9565   ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0

2019-04-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0   
 

  
 
 
 
 

 
 Done!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0

2019-04-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9395  
 
 
  provider gem in package type doesn't work anymore when rubygems is >= 3.0.0   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Release Notes Summary: 
 Puppet now uses the `--no-document` option instead of the deprecated `--no-rdoc --no-ri` options when installing gems, allowing compatibility with `rubygems` >= 3.0.0. [PUP-9395]  
 
 
Release Notes: 
 Bug Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDB-4257) PuppetDB skips message files with LONGNAME_HASH

2019-01-25 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4257  
 
 
  PuppetDB skips message files with LONGNAME_HASH   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 log.txt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDB-4257) PuppetDB skips message files with LONGNAME_HASH

2019-01-25 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PDB-4257  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PuppetDB skips message files with LONGNAME_HASH   
 

  
 
 
 
 

 
 These are the commands associated with the attached log file.  
 
 
 
 
 cd /opt/puppetlabs/server/data/puppetdb/stockpile  
 
 
    
 
 
 service pe-puppetdb stop  
 
 
    
 
 
 cp /tmp/78342822-1548132638857_report_8_sensu-server-i-03f0ac940c00b0a97.redactedxx.xxx.xxx.xxx_711bfaa65d298e501ef503231bc4e54b0739c167.json cmd/q/  
 
 
    
 
 
 service pe-puppetdb start  
 
 
    
 
 
 service pe-puppetdb stop  
 
 
    
 
 
 mv cmd/q/78342822-1548132638857_report_8_sensu-server-i-03f0ac940c00b0a97.redactedxx.xxx.xxx.xxx_711bfaa65d298e501ef503231bc4e54b0739c167.json cmd/q/78342822-1548132638857_report_8_sensu-server-i-03f0ac940c00b0a97.redactedxx.xxx.xxx.xxx.json  
 
 
    
 
 
 service pe-puppetdb start
  
   

Jira (PDB-4257) PuppetDB skips message files with LONGNAME_HASH

2019-01-25 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4257  
 
 
  PuppetDB skips message files with LONGNAME_HASH   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PDB 5.2.6  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 PuppetDB  
 
 
Created: 
 2019/01/25 10:11 AM  
 
 
Environment: 
 PE 2018.1.5  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Given: https://puppet.com/docs/puppetdb/5.2/pdb_support_guide.html#message-queue  > Note that the certname may be altered to accommodate filesystem restrictions. Currently that means replacing the characters “/”, “:”, “", and 0 with “-“, and truncating the certname so that it’s UTF-8 encoding never exceeds about 255 characters. A truncated certname will be followed by an underscore and a hash of the full certname.  PuppetDB is failing to process messages with a hashed certname in the filename with a Command has disappeared error. For example:  
 
 
 
 
 2019-01-25T17:48:41.687Z ERROR [p.p.queue] Command has disappeared: #puppetlabs.stockpile.queue.MetaEntry{:id 78342822, :metadata "1548132638857_report_8_sensu-server-i-03f0ac940c00b0a97.redactedxx.xxx.xxx.xxx-711bfaa65d298e501ef503231bc4e54b0739c167_1958dee5369fb75326e4b32d8876ceaf51c25d22.json"}
  
 

Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0

2019-01-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0   
 

  
 
 
 
 

 
 https://github.com/puppetlabs/puppet/pull/7320 targets 5.5.x   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0

2019-01-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0   
 

  
 
 
 
 

 
 Yes: https://github.com/puppetlabs/puppet/blob/099ab2efb8b1bd7649586a3a79312166dfb62e90/lib/puppet/provider/package/gem.rb#L135  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-2354) agent is confused about cert state

2019-01-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2354  
 
 
  agent is confused about cert state   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
CS Priority: 
 Needs Priority  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-2354) agent is confused about cert state

2019-01-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2354  
 
 
  agent is confused about cert state   
 

  
 
 
 
 

 
 If `allow_duplicate_certs` is broken, we should document it as a known issue to spare users the frustration of trying to utilize it?  
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Release Notes: 
 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2354) agent is confused about cert state

2019-01-02 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-2354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: agent is confused about cert state   
 

  
 
 
 
 

 
 Tama, your best practices question falls outside the scope of this product engineering ticketing system. That said, certificates are integral to the Puppet Agent/Server model as they are used to establish identity as well as encryption, so there is no supported practice to select as best.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

2018-12-28 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows   
 

  
 
 
 
 

 
  https://github.com/puppetlabs/puppet/pull/7311 should be preferred over https://github.com/puppetlabs/puppet/pull/5814 as it includes the same stripping of Puppet's RUBY_DIR from PATH prior to setting gemcmd on Windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

2018-12-06 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-6134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows   
 

  
 
 
 
 

 
 Oh, yes. There are other issues with more activity without a workaround.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9316) implement no_proxy in puppet.conf

2018-11-15 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9316  
 
 
  implement no_proxy in puppet.conf   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/11/15 2:21 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Puppet implements the following settings in puppet.conf:  
 
 
 
 
  http_proxy_host  
 
 
  http_proxy_password  
 
 
  http_proxy_port  
 
 
  http_proxy_user
  
 
 
 
  Puppet also reads those same settings from ENV. But it only reads the associated no_proxy setting from ENV. This requires configuring puppet proxy settings in two disparate locations.  
 

  
 
 
 
 

 
 
  

Jira (PUP-9312) puppet package provider fails when reading from registry

2018-11-12 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9312  
 
 
  puppet package provider fails when reading from registry   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 

  
 
 
 
 

 
 *Puppet Version: 5.5.6* *Puppet Server Version: 5.3.5* *OS Name/Version: Windows 2016*The ClaySys AppForms 6 application creates a Registry key in:{{HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\ClaySys AppForms_6\ConnectionString}}... that causes the Windows package provider to fail. The data appears to binary but {{reg_enum_value}} expects a string and calls {{read_wide_string}} in ...https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/package.rb#L28https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/registry.rb#L62https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/registry.rb#L120*Desired Behavior: It does not fail.**Actual Behavior:*   {code} [ Debug:  Prefetching windows resources for package}}*Debug:  Unable to convert value "8\xB3zk\xF6\xBB\xDF\n\x18lK8\xA1\xAA\x96\xA9T0\tB \xFC\xF5\v\xC0>\xE2\xC0\xDAEI\x98\xC2h\x00\xD21\xE8*\xA2\xB2rW\xAF5R\xB8\xDDm\ }}* xB4n0\xE1\xD9\xDC@J\xA1\x86\xC3\b\xD8)q\x96\xED\x8A\xB50\x83\xC8J\xAB\xAD\xCA\xACI\x05\f\xFC\xE9\xD6A\xEF\xB5\t\xE7B\x1D\x18\fc\x1EM\x9BS\x83\xE8\xA6\x84c;\x87\xF5?e1\x97\x1C\xB9\xAA?\xDF@\xBB\xBCs\x9A\x18\x95\xFD\xBE\xBE\x05SB\bI\xA3\x8E\xAB\xDD\xA2Yl\xF3\xB5\xFC\x04\xC9\x8A\xB7`\xD9\x96\xC1\xFD=\xF4\xA8\xE4\xB3\xBC\xFCb\xDA\xC6\xF0\b\xD7\x89\xAABO\xAC\xB6\x1C\xC8\x8E\xD1\x80\x10Q\xFE\x00\x0F\x99\xAFB\xB5\xFBU\x8BJ\x1C\xEC'.".force_encoding("UTF-16LE") to encoding UTF-8 due to #  Error: Cannot collect packages for Puppet::Type::Package::ProviderWindows provider; "\xB8\xDD" on UTF-16LE  {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

   

Jira (PUP-9312) puppet package provider fails when reading from registry

2018-11-12 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9312  
 
 
  puppet package provider fails when reading from registry   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9312) puppet package provider fails when reading from registry

2018-11-12 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9312  
 
 
  puppet package provider fails when reading from registry   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.6  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Windows  
 
 
Created: 
 2018/11/12 9:27 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Puppet Version: 5.5.6 Puppet Server Version: 5.3.5 OS Name/Version: Windows 2016 The ClaySys AppForms 6 application creates a Registry key in: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\ClaySys AppForms_6\ConnectionString ... that causes the Windows package provider to fail. The data appears to binary but reg_enum_value expects a string and calls read_wide_string in ... https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/windows/package.rb#L28 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/registry.rb#L62 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/registry.rb#L120 Desired Behavior: It does not fail. Actual Behavior:   
 
 
 
 
 [Debug: Prefetching windows resources for package}}*  
 
 
 Debug: Unable to convert value "8\xB3zk\xF6\xBB\xDF\n\x18lK8\xA1\xAA\x96\xA9T0\tB \xFC\xF5\v\xC0>\xE2\xC0\xDAEI\x98\xC2h\x00\xD21\xE8*\xA2\xB2rW\xAF5R\xB8\xDDm\}}*
  
 

Jira (PUP-7814) HTTPS file sources with non-puppet-trusted certs can't be used

2018-11-05 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-7814  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HTTPS file sources with non-puppet-trusted certs can't be used   
 

  
 
 
 
 

 
 Large customer affected by this 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9248) add support for devices to puppet ssl

2018-10-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9248  
 
 
  add support for devices to puppet ssl   
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9248) add support for devices to puppet ssl

2018-10-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9248  
 
 
  add support for devices to puppet ssl   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 PUP 6.0.0  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/10/18 3:20 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 After PUP-9156 ... An SSL error involving a device prompts the user to run the 'puppet ssl clean' command which cleans agent ssl files instead of the device ssl files, and prompts the user to run 'puppet agent' instead of 'puppet device'.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

Jira (PUP-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent

2018-10-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9156  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent   
 

  
 
 
 
 

 
 Gah, branch named and PR filed using PUP-9156. Let me know if you would like me to undo any of 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 post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent

2018-10-18 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9156  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent   
 

  
 
 
 
 

 
 I have a PR that may address this, posting soon ...  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent

2018-10-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9156  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent   
 

  
 
 
 
 

 
 I've copied the changes in the commit to my test master and agent, but it appears the puppet ssl clean action needs to implement a --device  parameter to differentiate between the default and (incorrectly assumed only) ssldir on the agent and the ssldir(s) of devices. As implemented now, a device certificate mismatch on an agent will output a message that instructs the user to run a command that will delete the agent ssldir rather than the device ssldir ...  
 
 
 
 
 [root@pe-201900-agent ~]# puppet device -v --waitforcert 0  
 
 
 Info: starting applying configuration to cisco.example.com at file:///etc/puppetlabs/puppet/devices/cisco.example.com.conf  
 
 
 Error: Could not request certificate: The certificate retrieved from the master does not match the agent's private key. Did you forget to run as root?  
 
 
 Certificate fingerprint: 48:11:BB:CC:AB:E7:F7:8A:2A:8E:7B:5E:A8:D3:DC:10:A9:01:FA:F6:F6:D6:85:15:A6:D8:61:0F:90:C1:93:98  
 
 
 To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certificate.  
 
 
 On the master:  
 
 
   puppetserver ca clean --certname cisco.example.com  
 
 
 On the agent:  
 
 
   1. puppet ssl clean  
 
 
   2. puppet agent -t  
 
 

Jira (PUP-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent

2018-10-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9156  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent   
 

  
 
 
 
 

 
 The pre-commit output does find the correct ssldir/cert_dir for the device:  
 
 
 
 
 [root@pe-201900-agent ~]# puppet device -v  
 
 
 Info: starting applying configuration to cisco.example.com at file:///etc/puppetlabs/puppet/devices/cisco.example.com.conf  
 
 
 Info: Creating a new SSL key for cisco.example.com  
 
 
 Info: Downloaded certificate for ca from pe-201900-master.puppetdebug.vlan  
 
 
 Info: Downloaded certificate for cisco.example.com from pe-201900-master.puppetdebug.vlan  
 
 
 Error: Could not request certificate: The certificate retrieved from the master does not match the agent's private key. Did you forget to run as root?  
 
 
 Certificate fingerprint: 48:11:BB:CC:AB:E7:F7:8A:2A:8E:7B:5E:A8:D3:DC:10:A9:01:FA:F6:F6:D6:85:15:A6:D8:61:0F:90:C1:93:98  
 
 
 To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certificate.  
 
 
 On the master:  
 
 
   puppetserver ca clean --certname cisco.example.com  
 
 
 On the agent:  
 
   

Jira (PUP-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent

2018-10-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9156  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent   
 

  
 
 
 
 

 
 Sigh.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2018-10-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8736  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
 Hence the ticket  While the use case that triggered it is specific to using a monolithic master as a device proxy, the wrongness exceeds that case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9156) Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent

2018-10-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9156  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent   
 

  
 
 
 
 

 
 Does this cover certificates for device agents? Those are stored in /opt/puppetlabs/puppet/cache/devices//ssl https://tickets.puppetlabs.com/browse/PUP-8736  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment

2018-10-04 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet lookup --compile returns incorrect results when trusted facts define environment
 

  
 
 
 
 

 
 This does not involve a transition from one environment to another: repeated testing (including puppet agent runs and the above puppet lookups) returns the same results. Empirically, it appears that trusted facts are not in scope when using "puppet lookup --compile" ... causing the (environment) node group rule (based upon a trusted fact != a specific value, in the example: "pp_role != ppserver") ... to include the node instead of excluding it ... changing the environment of the node in the context of the lookup ... resulting in the lookup reading from different environment than would be read during a puppet agent run.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment

2018-10-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet lookup --compile returns incorrect results when trusted facts define environment
 

  
 
 
 
 

 
 This may be relevant: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/application/lookup.rb#L49  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment

2018-10-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9207  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet lookup --compile returns incorrect results when trusted facts define environment
 

  
 
 
 
 

 
 See attached screen captures for Console view of the test Groups, Rules, and Nodes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment

2018-10-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9207  
 
 
  puppet lookup --compile returns incorrect results when trusted facts define environment
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 trusted.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment

2018-10-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9207  
 
 
  puppet lookup --compile returns incorrect results when trusted facts define environment
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 matching_nodes.,png.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment

2018-10-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9207  
 
 
  puppet lookup --compile returns incorrect results when trusted facts define environment
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 rules.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment

2018-10-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9207  
 
 
  puppet lookup --compile returns incorrect results when trusted facts define environment
 

  
 
 
 
 

 
Change By: 
 Thomas Kishel  
 
 
Attachment: 
 groups.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment

2018-10-03 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9207  
 
 
  puppet lookup --compile returns incorrect results when trusted facts define environment
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 groups.png  
 
 
Created: 
 2018/10/03 2:06 PM  
 
 
Environment: 
 PE 2018.1.3 and PE 2018.1.4 and possibly others  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 When the agent's environment is defined by node group membership based upon a trusted fact not equaling a value, puppet lookup --compile returns results from the wrong environment.  
 
 
 
 
 [root@puppet-master-201813 ~] cat /etc/puppetlabs/code/environments/development/hieradata/common.yaml  
 
 
 ---  
 
 
 env: 'development'  
 
 
    
 
 
  

Jira (PUP-9143) Puppet device raises `undefined method` error

2018-09-17 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9143  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet device raises `undefined method` error   
 

  
 
 
 
 

 
 Manual test of PR 7096/7097:   
 
 
 
 
 [root@pe-20190nightly-master production]# diff /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/device.rb device.rb.55   
 
 
    
 
 
 378a379,383  
 
 
 >   # We need to specify a ca location for all of the SSL-related  
 
 
 >   # indirected classes to work; in fingerprint mode we just need  
 
 
 >   # access to the local files and we don't need a ca.  
 
 
 >   Puppet::SSL::Host.ca_location = :remote  
 
 
 >   
 
 
 386a392  
 
 
 > 
  
 
 
 
   
 
 
 
 
 [root@pe-20190nightly-master production]# puppet device --verbose --trace --strict=error --target cisco.example.com  
 
 
 

Jira (PUP-8997) Deprecate Faces related to CA and certificate handling

2018-08-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-8997  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate Faces related to CA and certificate handling   
 

  
 
 
 
 

 
 Deprecation documented in: https://puppet.com/docs/puppet/5.5/release_notes.html#deprecations  
 
 
 
 
 [root@pe-201814-master ~]# puppetserver ca --help  
 
 
 Usage: puppetserver ca  [options]  
 
 
    
 
 
 Manage the Private Key Infrastructure for  
 
 
 Puppet Server's built-in Certificate Authority  
 
 
    
 
 
 Available Actions:  
 
 
 clean	Clean files from the CA for certificate(s)  
 
 
 create	Create a new certificate signed by the CA  
 
 
 generate	Generate a root and intermediate signing CA for Puppet Server  
 
 
 import	Import the CA's key, certs, and crls  
 
 
 list	List all certificate requests  
 
 
 revoke	Revoke a given certificate  
  

Jira (PUP-9027) Deprecate CA-related settings in puppet.conf

2018-08-24 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9027  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deprecate CA-related settings in puppet.conf   
 

  
 
 
 
 

 
 You can suppress deprecation warnings with this setting in puppet.conf:  
 
 
 
 
 [main]  
 
 
 disable_warnings = deprecations
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-614) I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1

2018-06-27 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  BOLT-614  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1   
 

  
 
 
 
 

 
 Bolt docs state that "a task can also have multiple implementation (sic)" and "This information about writing tasks applies for both Puppet Enterprise and Bolt" but in 2018.1.2 ...  
 
 
 
 
 [root@pe-201812-master ~]# puppet task show example  
 
 
 puppetlabs.orchestrator.task/invalid-task: Task example includes multiple matching task files
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

  1   2   >