Jira (PDB-4332) Unknown variable: 'postgresql::server::encoding' when puppetdb::manage_dbserver: false

2019-04-05 Thread Tom Parker (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PDB-4332  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unknown variable: 'postgresql::server::encoding' when puppetdb::manage_dbserver: false   
 

  
 
 
 
 

 
 I figured out what I was doing wrong.  It's not a bug if you RTFM and include the correct submodules for the servers that will be puppetdb::servers.  I had the entire puppetdb class loaded with manage_dbserver: false which doesn't work.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDB-4332) Unknown variable: 'postgresql::server::encoding' when puppetdb::manage_dbserver: false

2019-04-05 Thread Tom Parker (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4332  
 
 
  Unknown variable: 'postgresql::server::encoding' when puppetdb::manage_dbserver: false   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/05 5:32 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 If you set: puppetdb::manage_dbserver: false (for example when the puppetdb is on different server) the postgresql::server class never gets called so the postgresql::server:: variables are not set.  With strict_variables= true this causes a fatal error that currently can't be worked around without editing either the postgreql module code or the puppetdb module code.   Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Unknown variable: 'postgresql::server::encoding'. (file: /etc/puppetlabs/code/environments/testing/modules/postgresql/manifests/server/db.pp, line: 8, column: 17) (file: /etc/puppetlabs/code/environments/testing/modules/puppetdb/manifests/database/postgresql.pp, line: 34)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
   

Jira (PDOC-265) @example doesn't work with 4.x functions

2019-04-05 Thread Michelle Fredette (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michelle Fredette commented on  PDOC-265  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: @example doesn't work with 4.x functions   
 

  
 
 
 
 

 
 Jean Bond do you have any status on the strings work?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PDOC-265) @example doesn't work with 4.x functions

2019-04-05 Thread Ben Ford (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Ford commented on  PDOC-265  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: @example doesn't work with 4.x functions   
 

  
 
 
 
 

 
 Yes, the regsubst docs on the docs site are in pretty poor state. What do we need to do to prioritize fixing 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-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore

2019-04-05 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig commented on  PUP-9565  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not possible to set Mutliple Logging Destination with puppet agent anymore   
 

  
 
 
 
 

 
 Nirupama Mantha, no this won't be in 6.0.8. I've bumped it to the 6.0.z release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore

2019-04-05 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9565  
 
 
  Not possible to set Mutliple Logging Destination with puppet agent anymore   
 

  
 
 
 
 

 
Change By: 
 Jacob Helwig  
 
 
Fix Version/s: 
 PUP 6.0.8  
 
 
Fix Version/s: 
 PUP 6.0.z  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

2019-04-05 Thread Adrian Parreiras Horta (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrian Parreiras Horta commented on  BOLT-1158  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Publish bash helper library   
 

  
 
 
 
 

 
 Here's the `common.sh` I find myself using in tasks at the moment.  Attaching since Jira likes to ruin formatting. The `fail` function is a bit different from the one going into puppetlabs-service.  It makes $1 the key of the object, the idea being the step that failed can be identified.  Something like    
 
 
 
 
 fail "install_foo" "it no work" 1   
 
 
 
  Produces:      
 
 
 
 
 "install_foo": {  
 
 
   "status": "error",  
 
 
   "message": "it no work"  
 
 
 }  
 
 
 
  With an exit code of 1. I really like the indirection since you don't have to keep doing things like name=$PT_name, it just makes them available to you by sourcing the script. The trap and cleanup function would be nice, but I don't think it works as is.        
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

Jira (BOLT-1158) Publish bash helper library

2019-04-05 Thread Adrian Parreiras Horta (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrian Parreiras Horta updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1158  
 
 
  Publish bash helper library   
 

  
 
 
 
 

 
Change By: 
 Adrian Parreiras Horta  
 
 
Attachment: 
 common.sh  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore

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


 
 
 
 

 
 
 

 
   
 Nirupama Mantha commented on  PUP-9565  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not possible to set Mutliple Logging Destination with puppet agent anymore   
 

  
 
 
 
 

 
 Jacob Helwig is this ticket on track to be done by stop ship?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1158) Publish bash helper library

2019-04-05 Thread Adrian Parreiras Horta (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrian Parreiras Horta updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1158  
 
 
  Publish bash helper library   
 

  
 
 
 
 

 
Change By: 
 Adrian Parreiras Horta  
 
 
Attachment: 
 common.sh  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-1205) Only configure tasks to use Bolt's ruby interpreter for localhost

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


 
 
 
 

 
 
 

 
   
 Lucy Wyman assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1205  
 
 
  Only configure tasks to use Bolt's ruby interpreter for localhost   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Assignee: 
 Lucy Wyman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


Jira (PUP-9587) Serial execution with puppet device and ciscopuppet fails

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


 
 
 
 

 
 
 

 
   
 Nirupama Mantha commented on  PUP-9587  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Serial execution with puppet device and ciscopuppet fails   
 

  
 
 
 
 

 
 David Schmitt can you add release notes or update if 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 (BOLT-1158) Publish bash helper library

2019-04-05 Thread Adrian Parreiras Horta (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrian Parreiras Horta updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1158  
 
 
  Publish bash helper library   
 

  
 
 
 
 

 
Change By: 
 Adrian Parreiras Horta  
 
 
Attachment: 
 common.sh  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-4311) Build and test pe-puppetdb for el-8

2019-04-05 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt assigned an issue to Austin Blatt  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4311  
 
 
  Build and test pe-puppetdb for el-8   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Assignee: 
 Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9587) Serial execution with puppet device and ciscopuppet fails

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9587  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Serial execution with puppet device and ciscopuppet fails   
 

  
 
 
 
 

 
 Passed 6.4.x CI in 90841f4e9f  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9047) puppet device --apply fails to apply catalog to unregistered targets pt. 2

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9047  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: puppet device --apply fails to apply catalog to unregistered targets pt. 2   
 

  
 
 
 
 

 
 Passed 6.4.x CI in 90841f4e9f  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9584) Puppet Device plugin sync slow

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


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-9584  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet Device plugin sync slow   
 

  
 
 
 
 

 
 Passed 6.4.x CI in 90841f4e9f  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-4331) Cherry pick query support to 6.3.x

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


 
 
 
 

 
 
 

 
   
 gepetto-bot created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4331  
 
 
  Cherry pick query support to 6.3.x   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/05 11:12 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 gepetto-bot  
 

  
 
 
 
 

 
 #2871 was merged to master when it is needed on 6.3.x, this cherry picks the commits back to 6.3.x  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
   

Jira (BOLT-1229) Support temporary directory on Windows over SSH

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


 
 
 
 

 
 
 

 
   
 Lucy Wyman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1229  
 
 
  Support temporary directory on Windows over SSH   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/05 10:50 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Lucy Wyman  
 

  
 
 
 
 

 
 We currently use manual `execute` commands (ie. `mkdir -m 700 path`) to manage remote tempdirs for the SSH transport. This is to support `run-as` so we can massage the command to prepend `sudo`. However, this breaks when running on Windows over ssh, which raises `mdkir not found`. Proposed solution: separate `tmpdir` from the transport running it and determine which commands to run based on what's available on the target system. This will most likely involve breaking Sudoable::Tmpdir into 2 subclasses for windows and unix, and then determining which to use from the connection itself.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 

Jira (PUP-9579) device application is broken in 6.4

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


 
 
 
 

 
 
 

 
   
 Melissa Stone commented on  PUP-9579  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: device application is broken in 6.4   
 

  
 
 
 
 

 
 This has passed the 6.0.x pipeline with puppet-agent 6.0.7.88.g8c57e83  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-6743) Classes should propagate schedule metaparameter to its contained resources

2019-04-05 Thread Kevin Reeuwijk (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Reeuwijk commented on  PUP-6743  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Classes should propagate schedule metaparameter to its contained resources   
 

  
 
 
 
 

 
 I just ran into this issue as well, where the following code didn't behave as expected:  
 
 
 
 
 windows_updates::kb { $kb :  
 
 
   ensure   => 'present',  
 
 
   kb   => $kb,  
 
 
   notify   => Reboot['patch_window_reboot'],  
 
 
   schedule => 'patch_window'  
 
 
 }  
 
 
    
 
 
 schedule { 'maintenance_window':  
 
 
   range   => '22:00 - 04:00',  
 
 
   weekday => 'Saturday',  
 
 
 }  
 
 
    
 
 
 reboot { 'patch_window_reboot':  
 
 
   apply=> 'finished',  
  

Jira (PUP-9047) puppet device --apply fails to apply catalog to unregistered targets pt. 2

2019-04-05 Thread David Schmitt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Schmitt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9047  
 
 
  puppet device --apply fails to apply catalog to unregistered targets pt. 2   
 

  
 
 
 
 

 
Change By: 
 David Schmitt  
 
 
Release Notes Summary: 
 With these changes `puppet device` properly initialises private directories required for compiling and running catalogs.  
 
 
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 (PUP-9584) Puppet Device plugin sync slow

2019-04-05 Thread David Schmitt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Schmitt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9584  
 
 
  Puppet Device plugin sync slow   
 

  
 
 
 
 

 
Change By: 
 David Schmitt  
 
 
Release Notes Summary: 
 This release improves performance of `puppet device` by removing redundant work during initialisation.  
 
 
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 (PUP-9603) Documentation and/or spec for syntax checkers in heredocs out of date

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


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9603  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Documentation and/or spec for syntax checkers in heredocs out of date   
 

  
 
 
 
 

 
 I made a PR for the specifications repo - https://github.com/puppetlabs/puppet-specifications/pull/138 - see detailed commit comment there.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "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-9603) Documentation and/or spec for syntax checkers in heredocs out of date

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


 
 
 
 

 
 
 

 
   
 Henrik Lindberg commented on  PUP-9603  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Documentation and/or spec for syntax checkers in heredocs out of date   
 

  
 
 
 
 

 
 Thanks for logging this LeLutin. It seems the language specification is out of date as it talks about the now long gone "binder" - that should be corrected. Earlier this feature was of questionable value, but with the added possibility to evaluate functions on the agent it is of value to validate EPP while compiling the instructions to the agent rather than having to wait until the agent evaluates a deferred epp() call. For that reason I think this should be documented for general use. Note, we do not support extension of the syntax checkers in modules even if the logic internally is prepared to handle this. At the moment we support base64, epp, pp, and json. Notably missing is a yaml checker. I will put up a PR for the required specification change.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

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


 
 
 
 

 
 
 

 
   
 Halim Wijaya updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Halim Wijaya  
 
 
Priority: 
 Normal Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

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


 
 
 
 

 
 
 

 
   
 Halim Wijaya updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Halim Wijaya  
 
 
CS Priority: 
 Needs Priority  
 

  
 
 
 
 

 
 **This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below!image- 2019-04-05-10-41- 13-985.png|thumbnail!Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

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


 
 
 
 

 
 
 

 
   
 Halim Wijaya updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
Change By: 
 Halim Wijaya  
 

  
 
 
 
 

 
 **This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below!image- 2019-04-05-10-41- 13-985.png|thumbnail!Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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