Jira (PDB-4330) (DO NOT MERGE) trash bad state on build server

2019-04-03 Thread gepetto-bot (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 gepetto-bot created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4330  
 
 
  (DO NOT MERGE) trash bad state on build server   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/03 11:40 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 gepetto-bot  
 

  
 
 
 
 

 
 I don't have SSH access to the build server, so using this to run a couple quick commands  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

Jira (PUP-9601) mount resource should trigger 'systemctl daemon-reload'

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9601  
 
 
  mount resource should trigger 'systemctl daemon-reload'   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 
 
Sprint: 
 PR - 2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts

2019-04-03 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-7326  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts   
 

  
 
 
 
 

 
 Thanks for the report Halim Wijaya. Please file a new issue instead of reopening 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.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts

2019-04-03 Thread Halim Wijaya (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Halim Wijaya updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7326  
 
 
  Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts   
 

  
 
 
 
 

 
Change By: 
 Halim Wijaya  
 
 
Comment: 
 [^debugtraceoutput.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 (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts

2019-04-03 Thread Halim Wijaya (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Halim Wijaya updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7326  
 
 
  Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts   
 

  
 
 
 
 

 
Change By: 
 Halim Wijaya  
 
 
Attachment: 
 debugtraceoutput.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 (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts

2019-04-03 Thread Halim Wijaya (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Halim Wijaya commented on  PUP-7326  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts   
 

  
 
 
 
 

 
 debugtraceoutput.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 (PUP-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Vadym Chepkov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov commented on  PUP-9602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
 Interesting, so some code compiles fine. I reduced code fragment to this and it fails:    
 
 
 
 
 [root@master ~]# cat psql.pp   
 
 
   class { 'puppetdb::database::postgresql':  
 
 
     manage_package_repo => true,  
 
 
     postgres_version    => '9.6',  
 
 
   }  
 
 
    
 
 
    
 
 
 [root@master ~]# puppet apply psql.pp   
 
 
 Notice: Compiled catalog for master.localdomain in environment production in 0.41 seconds  
 
 
 Error: Could not autoload puppet/type/anchor: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/anchor'. Set at unknown location  
 
 
 Error: Could not autoload puppet/type/anchor: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/anchor'. Set at unknown location
  
 
 
 
   
 

  
 
  

Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Vadym Chepkov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov commented on  PUP-9602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
 Hmm, so, that means some other module contributes to it? You can check my bootstrap code here - https://github.com/vchepkov/puppet-bootstrap, it's easily reproducible        
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-8983) validate_cmd creates tmp file with inconsistent permissions

2019-04-03 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8983  
 
 
  validate_cmd creates tmp file with inconsistent permissions   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Sprint: 
 Platform Core KANBAN  
 
 
Component/s: 
 Community  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-8983) validate_cmd creates tmp file with inconsistent permissions

2019-04-03 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone assigned an issue to Melissa Stone  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8983  
 
 
  validate_cmd creates tmp file with inconsistent permissions   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Assignee: 
 Melissa Stone  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
 I'm having difficulty reproducing this:  
 
 
 
 
 [root@evnap2q7bofh6pf ~]# rpm -q puppet-agent  
 
 
 puppet-agent-6.4.0-1.el7.x86_64  
 
 
 root@evnap2q7bofh6pf ~]# puppet module install puppetlabs-stdlib  
 
 
 Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...  
 
 
 Notice: Downloading from https://forgeapi.puppet.com ...  
 
 
 Notice: Installing -- do not interrupt ...  
 
 
 /etc/puppetlabs/code/environments/production/modules  
 
 
 └── puppetlabs-stdlib (v5.2.0)  
 
 
 [root@evnap2q7bofh6pf ~]# puppet generate types  
 
 
 Notice: Generating Puppet resource types.  
 
 
 Notice: Generating '/etc/puppetlabs/code/environments/production/.resource_types/anchor.pp' using 'pcore' format.  
 
 
 Notice: Generating '/etc/puppetlabs/code/environments/production/.resource_types/file_line.pp' using 'pcore' format.  
 

Jira (PUP-9601) mount resource should trigger 'systemctl daemon-reload'

2019-04-03 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9601  
 
 
  mount resource should trigger 'systemctl daemon-reload'   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Labels: 
 mount  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9601) mount resource should trigger 'systemctl daemon-reload'

2019-04-03 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9601  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: mount resource should trigger 'systemctl daemon-reload'   
 

  
 
 
 
 

 
 ping Mihai Buzgau  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To 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-9601) mount resource should trigger 'systemctl daemon-reload'

2019-04-03 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9601  
 
 
  mount resource should trigger 'systemctl daemon-reload'   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Team: 
 Puppet Romania  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1202) Write developer docs for using Bolt::Spec run

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1202  
 
 
  Write developer docs for using Bolt::Spec run   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1202) Write developer docs for using Bolt::Spec run

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1202  
 
 
  Write developer docs for using Bolt::Spec run   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Fix Version/s: 
 BOLT Next  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1202) Write developer docs for using Bolt::Spec run

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1202  
 
 
  Write developer docs for using Bolt::Spec run   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Release Notes Summary: 
 docs only  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1202) Write developer docs for using Bolt::Spec run

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1202  
 
 
  Write developer docs for using Bolt::Spec run   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Labels: 
 docs  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1200) Localhost target should supply the puppet-agent feature

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer assigned an issue to Alex Dreyer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1200  
 
 
  Localhost target should supply the puppet-agent feature   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Assignee: 
 Alex Dreyer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9589) waitforcert not working in 6.4

2019-04-03 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9589  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: waitforcert not working in 6.4   
 

  
 
 
 
 

 
 Merged to 6.4.x in https://github.com/puppetlabs/puppet/commit/e1a1ff9894e53b85c7429fc4cf43e3a8dc2ca5d6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9589) waitforcert not working in 6.4

2019-04-03 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9589  
 
 
  waitforcert not working in 6.4   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Release Notes Summary: 
 Fixes a regression in 6.4.0 that prevented the waitforcert option working with the puppet device application.  
 
 
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 (BOLT-1223) Inconsistencies in Result outputs vs access methods

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  BOLT-1223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inconsistencies in Result outputs vs access methods   
 

  
 
 
 
 

 
 having to always index into the actual value of a task result is too verbose. If we're going to standardize it will be by eliminating a layer from the JSON output rather than adding a layer of boilerplate to the more common interaction of indexing into the Result object in a plan.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9591) Prepare JIRA and Confluence for release (Puppet Platform 5.5.13)

2019-04-03 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9591  
 
 
  Prepare JIRA and Confluence for release (Puppet Platform 5.5.13)   
 

  
 
 
 
 

 
Change By: 
 Nirupama Mantha  
 
 
Due Date: 
 2019/04/ 10 03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9592) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.13)

2019-04-03 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9592  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.13)   
 

  
 
 
 
 

 
Change By: 
 Nirupama Mantha  
 
 
Due Date: 
 2019/04/ 10 03  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9593) Prepare documentation updates and release notes (Puppet Platform 5.5.13)

2019-04-03 Thread Nirupama Mantha (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9593  
 
 
  Prepare documentation updates and release notes (Puppet Platform 5.5.13)   
 

  
 
 
 
 

 
Change By: 
 Nirupama Mantha  
 
 
Due Date: 
 2019/04/ 12 05  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-901) Improve Plan Logging with apply

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-901  
 
 
  Improve Plan Logging with apply   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting* All actions and plan output function(notice/warm/etc) are handed to the outputter.* {{--verbose}} becomes an option for the outputter not the logger.* By default "single actions" {{bolt command run}} {{bolt task run}} as opposed to {{bolt plan run}} are run with {{--verbose}} {{--no-verbose}} becomes and option to override this behavior.* "plan logging" becomes and outputter concept used by the json outputter initially* {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with {{--verbose}}* With apply human outputter only prints summary of entire run without verbose* With {{--verbose}} apply human outputter prints logs from the report showing at least changes.JSON outputter:* When in non-plan mode behaves are it does currently.* When in plan mode logs only the plan result to stdout.* When in plan mode and verbose mode sends intermediate results to stderr.(perhaps through logger.notice?) * logs entire jsonformat of apply result on stderr for each node at {{--verbose}}   Puppet log functions:* Eventually these should be handled by the outputter rather then the logger directly but this is left to a later ticket.apply_prep/get_resources:* these probably need to have specific events the outputter can handle. That is out of scope for this ticket. For now just rely on {{without_default_logging}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
  

Jira (BOLT-901) Improve Plan Logging with apply

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-901  
 
 
  Improve Plan Logging with apply   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting* All actions and plan output function(notice/warm/etc) are handed to the outputter.* {{--verbose}} becomes an option for the outputter not the logger.* By default "single actions" {{bolt command run}} {{bolt task run}} as opposed to {{bolt plan run}} are run with {{--verbose}} {{--no-verbose}} becomes and option to override this behavior.* "plan logging" becomes and outputter concept used by the json outputter initially* {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with {{--verbose}}* With apply human outputter only prints summary of entire run without verbose* With {{--verbose}} apply human outputter prints logs from the report showing at least changes.JSON outputter:* When in non-plan mode behaves are it does currently.* When in plan mode logs only the plan result to stdout.* When in plan mode and verbose mode sends intermediate results to stderr.(perhaps through logger.notice?)Puppet log functions:* Eventually these should be handled by the outputter rather then the logger directly but this is left to a later ticket. Apply_prep apply_prep/get_resources :*  this needs  these probably need  to have  better log  specific  events  the outputter can handle .  that  That  is out of scope for this ticket. For now just rely on {{without_default_logging}}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

Jira (BOLT-901) Improve Plan Logging with apply

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-901  
 
 
  Improve Plan Logging with apply   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting* All actions and plan output function(notice/warm/etc) are handed to the outputter.* {{--verbose}} becomes an option for the outputter not the logger.* By default "single actions" {{bolt command run}} {{bolt task run}} as opposed to {{bolt plan run}} are run with {{--verbose}} {{--no-verbose}} becomes and option to override this behavior.* "plan logging" becomes and outputter concept used by the json outputter initially* {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.Human outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with {{--verbose}}* With apply human outputter only prints summary of entire run without verbose* With {{--verbose}} apply human outputter prints logs from the report showing at least changes.JSON outputter:* When in non-plan mode behaves are it does currently.* When in plan mode logs only the plan result to stdout.* When in plan mode and verbose mode sends intermediate results to stderr.(perhaps through logger.notice?)Puppet log functions:* Eventually these should be handled by the outputter rather then the logger directly but this is left to a later ticket. Questions Apply_prep :*  How should the steps  this needs to have better log events. that is out  of  apply_prep be logged? Ideally each apply prep would be a single action with a single result  scope  for  each target at  this ticket. For now just rely on  {{ --verbose without_default_logging }} .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 

Jira (BOLT-901) Improve Plan Logging with apply

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-901  
 
 
  Improve Plan Logging with apply   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan.Refactor logging and outputting* All actions and plan output function(notice/warm/etc) are handed to the outputter.* {{--verbose}} becomes an option for the outputter not the logger.* By default "single actions" {{bolt command run}} {{bolt task run}} as opposed to {{bolt plan run}} are run with {{--verbose}} {{--no-verbose}} becomes and option to override this behavior.* "plan logging" becomes and outputter concept used by the json outputter initially * {{without_default_logging}} becomes state tracked on the outputter that causes it to simply ignore action events.   Human outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with {{--verbose}}* With apply human outputter only prints summary of entire run without verbose* With {{--verbose}} apply human outputter prints logs from the report showing at least changes.JSON outputter:* When in non-plan mode behaves are it does currently.* When in plan mode logs only the plan result to stdout.* When in plan mode and verbose mode sends intermediate results to stderr.(perhaps through logger.notice?)Puppet log functions:* Eventually these should be handled by the outputter rather then the logger directly but this is left to a later ticket.Questions:* How should the steps of apply_prep be logged? Ideally each apply prep would be a single action with a single result for each target at {{--verbose}}.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
  

Jira (BOLT-901) Improve Plan Logging with apply

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-901  
 
 
  Improve Plan Logging with apply   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 ProblemI want useful human readable output showing the events from each targets apply during a plan. This is especially useful when debugging an apply statement in a plan. Solution Refactor logging and outputting  When the format is human * All actions  and  plan_logging is active every run action should trigger the same  plan  output  it would if  function(notice/warm/etc) are handed to  the  action was run on it's own from the CLI  outputter .  * {{ plan_logging --verbose }} : is only part of  becomes an option for  the  human format and plan logging messages are printed on stdout  outputter  not  stderr  the logger. *  info level logging is primarily about logging full input/output of each action from a  By default "single actions" {{bolt command run}} {{bolt task run}} as opposed to {{bolt  plan . * notice level logging is only used initially  run}} are run  with  the  {{ notice --verbose }}  function from plans.*  {{ plan_logging --no-verbose }}  messages should be indented  becomes and option  to  make it easier to scan  override this behavior. *  Individual node results should be output as part of  "  plan logging  when there are fewer than " becomes and outputter concept used by the json outputter initiallyHuman outputter* Human outputter without verbose prints starting action and summary for action messages.* Human outputter prints full node-level result with  {{ n --verbose }}  targets for an action.  Questions: *  How can we show  With apply  human  readable  outputter only prints summary of entire run without  verbose * With {{--verbose}}  apply  output(ie event  human outputter prints  logs from  an apply  the  report )?  showing at least changes.  JSON outputter: *  Do we need  When in non-plan mode behaves are it does currently.* When in plan mode logs only the plan result  to  expose access to print human readable messages to  stdout  as a plan function or is {{notice}} enough? (defer and build if needed) . *  Do we need  When in plan mode and verbose mode sends intermediate results  to  show progress of actions when the format is json?  stderr.  ( not initially defer and build later if needed perhaps through logger.notice? ) Puppet log functions: *  Do we need an option for  Eventually these should be handled by  the  bolt user (  outputter rather then the  author)  logger directly but this is left  to  suppress individual node results from the human format?(defer and build  a  later  if needed)* How will this work with BoltSpec? (defer and build later if needed  ticket .  pass a noop outputter to executor for now)  Possible short term fixes Questions :*  add new formatter "verbose-human". verbose human output  How  should  print full results from actions during a plan run.* clean up output from {{  the steps of apply_prep }} and {{  be logged? Ideally each apply }} so they only logs  prep would be  a single  action with a single  result for e

Jira (BOLT-1227) Document how Bolt will use local SSH config

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1227  
 
 
  Document how Bolt will use local SSH config   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Sprint: 
 Bolt Ready for Grooming  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (BOLT-1227) Document how Bolt will use local SSH config

2019-04-03 Thread Nick Walker (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Walker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1227  
 
 
  Document how Bolt will use local SSH config   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/03 10:39 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nick Walker  
 

  
 
 
 
 

 
 The Problem Bolt will use local SSH config under certain circumstances and we should list when and how that works.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   

Jira (PUP-9470) Add note to logs about which value we're getting the server from

2019-04-03 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone commented on  PUP-9470  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add note to logs about which value we're getting the server from   
 

  
 
 
 
 

 
 This has passed 5.5.x ci as a part of puppet-agent 5.5.12.35.gcb02e38  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9586) Failed refreshonly resources generate duplicate event

2019-04-03 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone commented on  PUP-9586  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed refreshonly resources generate duplicate event   
 

  
 
 
 
 

 
 All three commits associated with this change have passed ci for the 5.5.x branch as a part of puppet-agent 5.5.12.35.gcb02e38  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1223) Inconsistencies in Result outputs vs access methods

2019-04-03 Thread Chris Barker (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Barker commented on  BOLT-1223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inconsistencies in Result outputs vs access methods   
 

  
 
 
 
 

 
 Wouldn't those be returned under $result['result']['object'] if we put all task results there (or 'value' to make it consistent with the api / internals) - again making the hash you access match the hash you'd see above in the notice($result) output?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Vadym Chepkov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov commented on  PUP-9602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
 Henrik Lindberg, yes, I mentioned earlier, puppet agent works properly    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
 After bouncing this off some other folks - this is probably related to the work done on the agent to support loading of data types (specifically the `Deferred` data type). What happens is that it probably ended up with a mix of loading both the generated types and the actual resource type implementations. The agent most certainly needs to load the resource type implementations and should ignore the generated types completely. Vadym Chepkov This means that it is broken in the apply case, but should work just fine when used when compiling catalogs with a master.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1026) Bolt package should include hiera-eyaml

2019-04-03 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue assigned an issue to Cas Donoghue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1026  
 
 
  Bolt package should include hiera-eyaml   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
Assignee: 
 Cas Donoghue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1226) Allow `token` pcp transport option, as alternative to `token-file`

2019-04-03 Thread Reid Vandewiele (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reid Vandewiele created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1226  
 
 
  Allow `token` pcp transport option, as alternative to `token-file`   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/03 9:57 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Reid Vandewiele  
 

  
 
 
 
 

 
 In the inventory.yaml file, especially when dealing with groups of nodes accessible across multiple Orchestrator endpoints, it would be convenient to be able to specify rbac tokens directly, rather than a path to a file containing the token. E.g.  
 
 
 
 
 ---  
 
 
 groups:  
 
 
   - name: stack-1  
 
 
 config:  
 
 
   transport: pcp  
 
 
   pcp:  
 
 

Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  BOLT-1223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inconsistencies in Result outputs vs access methods   
 

  
 
 
 
 

 
 We will never be able to allow result['object']. The task spec allows tasks to return arbitrary keys so object could be a value from the task itself. It would have to be result['_object'] to avoid collisions.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1223) Inconsistencies in Result outputs vs access methods

2019-04-03 Thread Chris Barker (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Barker commented on  BOLT-1223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inconsistencies in Result outputs vs access methods   
 

  
 
 
 
 

 
 Great - .to_json or .to_json would be useful, but I guess I'm coming from the background of structured facts where you access nested data via $facts['os']['family'] etc. I can see why we can't just make [] render all of Result as a hash without introducing a breaking change since thats how you access value - but there's really the general inconsistency that one can create a thing named $foo that could be treated as a hash when printed, but can't be accessed like a hash would be when called vs all the other examples of interacting with a hash. While in the interim having $result.to_json['object'] be a working alternative until $result['object'] could be introduced as a breaking change may be acceptable - it's not intuitive that when I print $result via notice($result) I see a json hash, so to access it I need to call it as $result.to_json['object'] in my code.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1223) Inconsistencies in Result outputs vs access methods

2019-04-03 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  BOLT-1223  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inconsistencies in Result outputs vs access methods   
 

  
 
 
 
 

 
 Agreed type is a problem, we will change the name and make it available with a function on the Result object. Adding .to_json and/or .to_data to the Result and ResultSet objects should make them easier to pass to tasks and interact with in the pure data format. This seems like it may be what you really want. Injecting _status, _target into the value of the result and later moving the result key to the top level is probably the solution for BOLT-833. Deciding how to roll that out in the least disruptive fashion is a bit of a problem and it will need to be mimicked in PE's orchestrator responses at some point.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1052) Support run-as for shell localhost transport.

2019-04-03 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman commented on  BOLT-1052  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support run-as for shell localhost transport.   
 

  
 
 
 
 

 
 One issue I'm not sure how to get around is that I get STDERR: bash: /usr/bin/sudo: Argument list too long trying to run with huge input and sudo. However, I get the same error when running with --run-as over SSH with bolt currently, so I think this is expected behavior (uysu3yvr9mzc2wa.delivery.puppetlabs.net for centOS with current Bolt master installed)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1052) Support run-as for shell localhost transport.

2019-04-03 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman commented on  BOLT-1052  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support run-as for shell localhost transport.   
 

  
 
 
 
 

 
 I've got this PR installed on Windows 10 at r8ek30rsifi97m4.delivery.puppetlabs.net - I created a user 'bolt' with password 'bolt', and the config file is at C:\Users\Administrator\bolt\bolt.yaml Also testing on osx at s0k96i5zfsptrgg.delivery.puppetlabs.net. I uploaded our spec fixtures there to test reading from stdin, piping in a json file, etc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Vadym Chepkov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov commented on  PUP-9602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
 Same result with only one file present:  
 
 
 
 
 [root@master .resource_types]# ls -lA  
 
 
 total 4  
 
 
 -rw-r--r--. 1 root root 1746 Apr  3 13:26 anchor.pp  
 
 
 [root@master .resource_types]# puppet apply -e 'include bootstrap::master'   
 
 
 Notice: Compiled catalog for master.localdomain in environment production in 0.82 seconds  
 
 
 Error: Could not autoload puppet/type/anchor: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/anchor'. Set at unknown location  
 
 
 Error: Could not autoload puppet/type/anchor: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/anchor'. Set at unknown location
  
 
 
 
   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

   

Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Vadym Chepkov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov commented on  PUP-9602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
 Removed anchor.pp, it fails on the next file:  
 
 
 
 
 [root@master ~]# rm /etc/puppetlabs/code/environments/production/.resource_types/anchor.pp   
 
 
 rm: remove regular file ‘/etc/puppetlabs/code/environments/production/.resource_types/anchor.pp’? y  
 
 
 [root@master ~]# puppet apply -e 'include bootstrap::master'   
 
 
 Notice: Compiled catalog for master.localdomain in environment production in 0.74 seconds  
 
 
 Error: Could not autoload puppet/type/postgresql_conn_validator: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/postgresql_conn_validator'. Set at unknown location  
 
 
 Error: Could not autoload puppet/type/postgresql_conn_validator: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/postgresql_conn_validator'. Set at unknown location
  
 
 
 
     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9602  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
 Does it work if you after having run generate types manually remove the generated file for the anchor type? Asking this to possibly narrow down what is wrong. Alternatively, remove all other generated files and keep only the one for anchor - does it error then?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Vadym Chepkov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9602  
 
 
  puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
Change By: 
 Vadym Chepkov  
 
 
Attachment: 
 debug-trace.log  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9602) puppet 6 apply fails if puppet types have been generated

2019-04-03 Thread Vadym Chepkov (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vadym Chepkov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9602  
 
 
  puppet 6 apply fails if puppet types have been generated   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 6.4.0  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/03 5:33 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Vadym Chepkov  
 

  
 
 
 
 

 
 Puppet Version: 6.4.0 Puppetserver Version 6.3.0 OS Name/Version: CentOS 7.5 Stumbled upon an unusual behavior in Puppet 6 (works as expected on Puppet 5) If command puppet generate types has been executed, puppet apply fails. Puppet agent works normally.  
 
 
 
 
 [root@master ~]# puppet apply -e 'include bootstrap::master'  
 
 
 Notice: Compiled catalog for master.localdomain in environment production in 0.81 seconds  
 
 
 Notice: Applied catalog in 0.89 seconds  
 
 
    
 
 
 [root@master ~]# puppet generate types  
   

Jira (PUP-9586) Failed refreshonly resources generate duplicate event

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9586  
 
 
  Failed refreshonly resources generate duplicate event   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Release Notes Summary: 
 this issue is a bug, as discussed in the retro last week there is no documentation needed  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9601) mount resource should trigger 'systemctl daemon-reload'

2019-04-03 Thread Adam Winberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Winberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9601  
 
 
  mount resource should trigger 'systemctl daemon-reload'   
 

  
 
 
 
 

 
Change By: 
 Adam Winberg  
 

  
 
 
 
 

 
 *Puppet Version: 5.5.3* *Puppet Server Version: 5.3.3* *OS Name/Version: RHEL7*On systemd distributions entries in /etc/fstab automatically generates systemd .mount files, resulting in systemd effectively managing the mount. When changes are made to /etc/fstab, 'systemctl daemon-reload' must be called in order to generate new systemd mount files. It seems natural to me that puppets mount resource automatically should trigger this reload on changes in fstab if systemd is present, which it does not do currently. *Desired Behavior:*Changes in mount resources should always trigger a reload of systemd configuration (systemctl daemon-reload)*Actual Behavior:*Changes in mount resource only updates fstab. Changes will not update corresponding systemd .mount files until reboot or issuing a 'systemctl daemon-reload' manually. This is particularly inconvinient when using systemd automounting.Following puppet mount:{code:java}  mount {"/temp": ensure => 'present', device => 'fs_server:/temp', fstype => 'nfs', options => 'noauto,x-systemd.automount,x-systemd.device-timeout=10,x-systemd.mount-timeout=30,x-systemd.idle-timeout=60,_netdev,vers=4.0,sec=krb5 , '  }{code}creates a line in fstab for this mount, but does not create any corresponding systemd mount files. So, in this case, 'mount /temp' will work but not 'systemctl start temp.mount'. On boot, however, systemd will generate mount files (one .mount and one .automount) for this mount automatically. On access the filesystem will be mounted automatically by systemd, and unmounted after 60s of inactivity. If I change mount options for this mount, the fstab will be updated but since the systemd files are not updated any automounting after the change will still use the old options.I can workaround this in my code by notifying a 'systemctl daemon-reload' in my mount definition, but if the mount fails for some reason (typically because of a failed remount) the reload command will not run leaving my system in an inconsistent state.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

Jira (PUP-9601) mount resource should trigger 'systemctl daemon-reload'

2019-04-03 Thread Adam Winberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adam Winberg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9601  
 
 
  mount resource should trigger 'systemctl daemon-reload'   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.3  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/03 4:01 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Adam Winberg  
 

  
 
 
 
 

 
 Puppet Version: 5.5.3 Puppet Server Version: 5.3.3 OS Name/Version: RHEL7 On systemd distributions entries in /etc/fstab automatically generates systemd .mount files, resulting in systemd effectively managing the mount. When changes are made to /etc/fstab, 'systemctl daemon-reload' must be called in order to generate new systemd mount files. It seems natural to me that puppets mount resource automatically should trigger this reload on changes in fstab if systemd is present, which it does not do currently.   Desired Behavior: Changes in mount resources should always trigger a reload of systemd configuration (systemctl daemon-reload) Actual Behavior: Changes in mount resource only updates fstab. Changes will not update corresponding systemd .mount files until reboot or issuing a 'systemctl daemon-reload' manually. This is particularly inconvinient when using systemd automounting. Following puppet mount:  
 
 
 
 
 mount {"/temp":  
 
 
  ensure => 'present',  
 
 
  device => 'fs_server:/temp',  
 

Jira (BOLT-833) JSON Output for Results is confusing for new users

2019-04-03 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  BOLT-833  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JSON Output for Results is confusing for new users   
 

  
 
 
 
 

 
 It is not as easy as adding a function `[]` like that since it is an operator in the Puppet Language and there is no automatic mapping of operators to methods.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9569) Crontab prefetch fails when the filename is not a valid user

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9569  
 
 
  Crontab prefetch fails when the filename is not a valid user   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9569) Crontab prefetch fails when the filename is not a valid user

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9569  
 
 
  Crontab prefetch fails when the filename is not a valid user   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To 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-9564) Puppet upgrades debian packages with pending updates when setting them on hold

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9564  
 
 
  Puppet upgrades debian packages with pending updates when setting them on hold   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To 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-9564) Puppet upgrades debian packages with pending updates when setting them on hold

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9564  
 
 
  Puppet upgrades debian packages with pending updates when setting them on hold   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9502) codesigning puppet executables on macOS 10.14

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9502  
 
 
  codesigning puppet executables on macOS 10.14   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 5  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To 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-9502) codesigning puppet executables on macOS 10.14

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9502  
 
 
  codesigning puppet executables on macOS 10.14   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9331) Puppet Runs fail if leftovers in /var/spool/cron are present

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9331  
 
 
  Puppet Runs fail if leftovers in /var/spool/cron are present   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 Platform OS Kanban, PR -  Triage  2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9331) Puppet Runs fail if leftovers in /var/spool/cron are present

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9331  
 
 
  Puppet Runs fail if leftovers in /var/spool/cron are present   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To 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-7876) Puppet Acceptance Suite Fails for Win-2012r2 Japanese

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7876  
 
 
  Puppet Acceptance Suite Fails for Win-2012r2 Japanese   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - Triage  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-6488) Gem provider should allow alternative gem command; should not rely on $PATH

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1082) pip provider should handle multiple pips/pythons

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1082  
 
 
  pip provider should handle multiple pips/pythons   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (FACT-1888) 'os.release' values not correct for VZ7

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1888  
 
 
  'os.release' values not correct for VZ7   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-03 , PR - 2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-8664) rpm package provider is too specific

2019-04-03 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-03 , PR - 2019-04-17  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9588) Unable to apply catalog successfully on nodes due to running iexplore process

2019-04-03 Thread Tanmeet Kaur (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tanmeet Kaur assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9588  
 
 
  Unable to apply catalog successfully on nodes due to running iexplore process   
 

  
 
 
 
 

 
Change By: 
 Tanmeet Kaur  
 
 
Assignee: 
 Tanmeet Kaur  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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.