Jira (PUP-6988) Variable Scope of defined Types in Puppet4 changed (undocumented)

2016-12-07 Thread Robert Heinzmann (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Heinzmann created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6988 
 
 
 
  Variable Scope of defined Types in Puppet4 changed (undocumented)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.8.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 11:25 PM 
 
 
 

Environment:
 
 
 

Puppet AIO
 

puppet-agent-1.8.1-1.el7.x86_64
 

Centos7
 
 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Robert Heinzmann 
 
 
 
 
 
 
 
 
 
 
It seems the variable scope for erb templates within defined types has changed in Puppet 4. This seems to be undocumented.  
Example Code test.pp:  
 
 
 
 
 
 
   

Jira (PUP-6967) Reload puppetserver in puppet acceptance tests

2016-12-07 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-6967 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reload puppetserver in puppet acceptance tests  
 
 
 
 
 
 
 
 
 
 
Josh Cooper that makes sense, yes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6850) Make commit formatting check robust

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-6850 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make commit formatting check robust  
 
 
 
 
 
 
 
 
 
 
Merged in https://github.com/puppetlabs/puppet/commit/50c0d51065126f242f984c8060b126c46e2f3af2 
Merged up to stable in https://github.com/puppetlabs/puppet/commit/ffabfc3d3019b1a4653c3015182a8996c8a86cde Merged up to master in https://github.com/puppetlabs/puppet/commit/9dda0a424b5067cabdfd70f72b286fa7f29f604a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3218) extensions end-to-end tests hanging frequently

2016-12-07 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-3218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: extensions end-to-end tests hanging frequently  
 
 
 
 
 
 
 
 
 
 
the deref is blocked by a hang on this blocking take: https://github.com/puppetlabs/pe-puppetdb-extensions/blob/master/src/puppetlabs/pe_puppetdb_extensions/sync/services.clj#L269 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1441) --show_diff causes crashes on files with UTF-8 content

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-1441 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: --show_diff causes crashes on files with UTF-8 content  
 
 
 
 
 
 
 
 
 
 
Jeremy Grant - no ETA just yet, but it's in our high priority Unicode hit list, which we're actively working through. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6986 
 
 
 
  Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Sprint:
 
 AP Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6986 
 
 
 
  Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Labels:
 
 i18n utf-8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-6986 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars   
 
 
 
 
 
 
 
 
 
 
This looks pretty similar to the Puppet::Util::Execution.execute issue in PUP-6432 except that the base service provider goes directly through IO.popen at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/base.rb#L36. The spirit is pretty similar though - pull in some output, don't explicitly specify encoding, watch bad things happen. 
Moses Mendoza and I have done some auditing in the past and are aware of some other calls that use IO directly / indirectly and don't specify encoding that are problematic. A number of them are going to be resolved in PUP-6925, but the trickier issues are going to be isolated / fixed independently. 
I'm pulling this into the Phase 1 blockers epic because we need to ensure that this case is properly tested / fixed. 
Thanks for the report. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3218) extensions end-to-end tests hanging frequently

2016-12-07 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-3218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: extensions end-to-end tests hanging frequently  
 
 
 
 
 
 
 
 
 
 
seems to be happening in that test consistently. I think the hang is caused by this deref: https://github.com/puppetlabs/trapperkeeper/blob/master/src/puppetlabs/trapperkeeper/internal.clj#L621 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3483) Systemd provider doesn't scan for changed units

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3483 
 
 
 
  Systemd provider doesn't scan for changed units  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3218) extensions end-to-end tests hanging frequently

2016-12-07 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-3218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: extensions end-to-end tests hanging frequently  
 
 
 
 
 
 
 
 
 
 
based on this thread dump it seems to be hanging in the three node end to end test. I'm not sure if that's consistently the case. 
https://gist.github.com/anonymous/8b238bf1ef78838a4a931dd395a352f2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6983 
 
 
 
  File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Labels:
 
 i18n utf-8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6983 
 
 
 
  File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Team:
 
 Agent & Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6983 
 
 
 
  File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Sprint:
 
 AP Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-6983 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.  
 
 
 
 
 
 
 
 
 
 
The current codepage shouldn't be relevant in Windows when creating / updating a file resource. The manifest is in UTF-8, and the file system APIs in use are wide string. 
It looks like the error message is propagating during the backup attempt from https://github.com/puppetlabs/puppet/blob/ebd96213cab43bb2a8071b7ac0206c3ed0be8e58/lib/puppet/file_bucket/dipper.rb#L55 
Might need to take a closer look at that code to see if something in there is wrong. I don't see any UTF-8 related tests in https://github.com/puppetlabs/puppet/blob/ebd96213cab43bb2a8071b7ac0206c3ed0be8e58/spec/unit/file_bucket/dipper_spec.rb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3218) extensions end-to-end tests hanging frequently

2016-12-07 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3218 
 
 
 
  extensions end-to-end tests hanging frequently  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 4:25 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
Running locally on master, I see hangs in the end-to-end test pretty consistently. Jeremy Barlow says it doesn't happen every time but it's happened every time so far for me. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
   

Jira (PUP-6987) ENV behaviour has changed on Japanese Windows with ruby 2.3.x

2016-12-07 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6987 
 
 
 
  ENV behaviour has changed on Japanese Windows with ruby 2.3.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Summary:
 
 ENV behaviour has changed on Japanese Windows with ruby 2.3. 0 x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.

2016-12-07 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-6983 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.  
 
 
 
 
 
 
 
 
 
 
Sean Griffin I can't repro on the same ubuntu vm you were using: 
 
 
 
 
 
 
root@qj5xhpzxp03l1d1:/tmp# rm file_utf8_title_€ 
 
 
 
 
root@qj5xhpzxp03l1d1:/tmp# vi foo.pp 
 
 
 
 
root@qj5xhpzxp03l1d1:/tmp# cat foo.pp 
 
 
 
 
file { "/tmp/file_utf8_title_€" : 
 
 
 
 
  ensure => file, 
 
 
 
 
  mode => "0644", 
 
 
 
 
  content => "This is the file content. 
 
 
 
 
", 
 
 
 
 
} 
 
 
 
 
root@qj5xhpzxp03l1d1:/tmp# puppet apply foo.pp 
 
 
 
 

Jira (PUP-6987) ENV behaviour has changed on Japanese Windows with ruby 2.3.0

2016-12-07 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6987 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ENV behaviour has changed on Japanese Windows with ruby 2.3.0  
 
 
 
 
 
 
 
 
 
 
Also failed in ruby 2.3.1 
 
 
 
 
 
 
$ bundle exec rspec ./spec/unit/util_spec.rb:185 
 
 
 
 
Run options: 
 
 
 
 
  include {:locations=>{"./spec/unit/util_spec.rb"=>[185]}} 
 
 
 
 
  exclude {:broken=>true, :benchmark=>true} 
 
 
 
 
F 
 
 
 
 
  
 
 
 
 
Failures: 
 
 
 
 
  
 
 
 
 
  1) Puppet::Util#withenv on Windows works around Ruby bug 8822 (which fails to preserve UTF-8 properly when accessing ENV) (Ruby >= 2.3.x) 
 
 
 
 
 Failure/Error: expect(ENV.key?(codepage_key)).to eq(false) 
 
 
 
  

Jira (PUP-6987) ENV behaviour has changed on Japanese Windows with ruby 2.3.0

2016-12-07 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6987 
 
 
 
  ENV behaviour has changed on Japanese Windows with ruby 2.3.0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 4:02 PM 
 
 
 

Environment:
 
 
Puppet 4.8.2 (stable branch on puppet, post 4.8.2 release) Windows Server 2012 R2 Japanese (VMPooler) Ruby x64 2.3.0 with devkit 
 
 
 

Labels:
 

 maintenance windows 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Glenn Sarti 
 
 
 
 
 
 
 
 
 
 
We have a few tests about the strange ENV behaviour with UTF8 keys and values on Windows. I was testing on the Windows 2012 R2 Japanese edition and came across a strange spec failure; 
 
 
 
 
 
 
Administrator@WRXQLJ627XIYM5K c:\source\puppet 
 
 
 
 
$ bundle exec rspec 

Jira (PUP-6984) alias on Package/Exec resources produces misleading warning

2016-12-07 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6984 
 
 
 
  alias on Package/Exec resources produces misleading warning  
 
 
 
 
 
 
 
 
 
 
I can reproduce the warning using a smaller manifest: 
 
 
 
 
 
 
exec { '/usr/bin/false': 
 
 
 
 
  alias => 'something', 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
notify {'depends on exec': 
 
 
 
 
  require => [Exec['something']] 
 
 
 
 
}
 
 
 
 
 
 
 
The warning was introduced in commit ecaa18b724587a9ebf86a8efcf99dcc2265b0165. 
Using check_commits.sh: 
 
 
 
 
 
 
#!/bin/bash 
 
 
 
 
bundle update 

Jira (PUP-6984) alias on Package/Exec resources produces misleading warning

2016-12-07 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6984 
 
 
 
  alias on Package/Exec resources produces misleading warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 
 
 
 
 
 
 
 An alias on (at least) package and exec resources that worked fine to resolve a dependency at least in Puppet 3.4 doesn't work anymore in Puppet 4.8.0.I would expect that the manifest below would not create the Warning it gives. (I'm surprised by a warning that the dependency isn't found, but then getting a "dependency failed" on just that resource, though referenced by the title, not the alias, which in turn is OK)Almost minimal reproduction case: {noformat} $ cat /tmp/t.pp; sudo puppet apply --detailed-exitcodes /tmp/t.pp; echo $?# $Id$package{'postfix':  alias  => 'mta',  ensure => latest,}exec{'/bin/false':  alias => 'something',}notify{'Depended on mta':  require => [Exec['something'], Package['mta']],} {noformat}{noformat} Warning: Could not find resource 'Exec[something]' in parameter 'require'   (at /tmp/t.pp:12)Warning: Could not find resource 'Package[mta]' in parameter 'require'   (at /tmp/t.pp:12)Notice: Compiled catalog for 90cdc197-bd0d-4ee2-8e22-cf4962548eb1 in environment standalone_puppet in 0.49 secondsError: /bin/false returned 1 instead of one of [0]Error: /Stage[main]/Main/Exec[/bin/false]/returns: change from notrun to 0 failed: /bin/false returned 1 instead of one of [0]Notice: /Stage[main]/Main/Notify[Depended on mta]: Dependency Exec[/bin/false] has failures: trueWarning: /Stage[main]/Main/Notify[Depended on mta]: Skipping because of failed dependenciesNotice: Applied catalog in 0.62 seconds 4 {noformat}   
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
  

Jira (PUP-6986) Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars

2016-12-07 Thread Erik Hansen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Hansen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6986 
 
 
 
  Service provider fails when hasstatus => false and the output of 'ps -ef' happens to contains non-ASCII chars   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 3:37 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Erik Hansen 
 
 
 
 
 
 
 
 
 
 
When a service resource uses the parameter `hasstatus => false`, puppet will search the output of `ps -ef` to determine the status of the service.  
If the output of `ps -ef` happens to contain non-ASCII characters, we see the following stack trace: 
 
 
 
 
 
 
Error: /Stage[main]/Automic/Service[automic]: Could not evaluate: invalid byte sequence in US-ASCII  
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/base.rb:38:in `match'  
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/service/base.rb:38:in `block (2 levels) in getpid'  
 
 

Jira (FACT-1534) Acceptance: Facter seg faults on Cisco XR during some config file tests

2016-12-07 Thread Stan Duffy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy commented on  FACT-1534 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Acceptance: Facter seg faults on Cisco XR during some config file tests  
 
 
 
 
 
 
 
 
 
 
Forgot to add new pre-suite to the acceptance/config/aio/options.rb fle 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6985) False test failures on Windows due to case-sensitive paths

2016-12-07 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6985 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: False test failures on Windows due to case-sensitive paths  
 
 
 
 
 
 
 
 
 
 
in spec/integration 
 
 
 
 
 
 
Failures: 
 
 
 
 
  
 
 
 
 
  1) interpolating $environment config_version interpolates $environment 
 
 
 
 
 Failure/Error: expect(environment.config_version).to eq(expected) 
 
 
 
 
  
 
 
 
 
   expected: "c:/some/script testing" 
 
 
 
 
got: "C:/some/script testing" 
 
 
 
 
  
 
 
 
 
   (compared using ==) 
 
 
 
 
 # ./spec/integration/environments/settings_interpolation_spec.rb:57:in `block (3 levels) in ' 
 
 
 
 
 

Jira (PUP-6985) False test failures on Windows due to case-sensitive paths

2016-12-07 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6985 
 
 
 
  False test failures on Windows due to case-sensitive paths  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 
 
 
 
 
 
 
 Windows paths are not case sensitive, however some tests are failing to due to case sensitive paths, e.g.{code}...  1) Puppet::FileSystem symlink expand_path on Windows should return the absolute path including system drive letter when given /, like Ruby File.expand_path Failure/Error: expect(expanded).to eq(ENV['SystemDrive'] + File::SEPARATOR)   expected: "C:/"got: "c:/"   (compared using ==) # ./spec/unit/file_system_spec.rb:692:in `block (6 levels) in '{code} h3.repro.* On a vanilla Windows VM (2012 R2), install git, ruby etc,* clone puppet, bundle install etc.* Open command prompt* Change directory , making sure the drive letter is lowercase  e.g. cd c:/puppet* run tests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6985) False test failures on Windows due to case-sensitive paths

2016-12-07 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6985 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: False test failures on Windows due to case-sensitive paths  
 
 
 
 
 
 
 
 
 
 
in spec/unit 
 
 
 
 
 
 
Failures: 
 
 
 
 
  
 
 
 
 
  1) Puppet::FileSystem symlink expand_path on Windows should return the absolute path including system drive letter when given /, like Ruby File.expand_path 
 
 
 
 
 Failure/Error: expect(expanded).to eq(ENV['SystemDrive'] + File::SEPARATOR) 
 
 
 
 
  
 
 
 
 
   expected: "C:/" 
 
 
 
 
got: "c:/" 
 
 
 
 
  
 
 
 
 
   (compared using ==) 
 
 
 
 
 # ./spec/unit/file_system_spec.rb:692:in `block (6 levels) in ' 
 
 
 
   

Jira (PUP-6985) False test failures on Windows due to case-sensitive paths

2016-12-07 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6985 
 
 
 
  False test failures on Windows due to case-sensitive paths  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 2:38 PM 
 
 
 

Labels:
 

 maintenance puppethack Windows 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Glenn Sarti 
 
 
 
 
 
 
 
 
 
 
Windows paths are not case sensitive, however some tests are failing to due to case sensitive paths, e.g. 
 
 
 
 
 
 
... 
 
 
 
 
  1) Puppet::FileSystem symlink expand_path on Windows should return the absolute path including system drive letter when given /, like Ruby File.expand_path 
 
 
 
 
 Failure/Error: expect(expanded).to eq(ENV['SystemDrive'] + File::SEPARATOR) 
 

Jira (PUP-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.

2016-12-07 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6983 
 
 
 
  File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 
 
 
 
 
 
 
 If the file name contains a utf8 character, then drift correctionfails on ubuntu 1604 and windows (2012r2 and 2016).To see for yourself:Run puppet apply with this manifest to create a file witha utf8 non ascii character in its name.manifest_file_utf8_title.pp:{code}file { "/tmp/file_utf8_title_€" :  ensure => file,  mode => "0644",  content => "This is the file content.",}{code}(The windows version of this manifest names the file"C:/cygwin64/tmp/file_utf8_title_€")Change the file (drift).Run puppet apply again to correct the drift.See this error.{code}Notice: Compiled catalog for qj5xhpzxp03l1d1.delivery.puppetlabs.net in environment production in 0.08 secondsError: Could not back up /tmp/file_utf8_title_€: U+20AC from UTF-8 to ISO-8859-1Error: Could not back up /tmp/file_utf8_title_€: U+20AC from UTF-8 to ISO-8859-1Error: /Stage[main]/Main/File[/tmp/file_utf8_title_€]/content: change from {md5}d41d8cd98f00b204e9800998ecf8427e to {md5}12c5472e7479836c84093162660f2a7b failed: Could not back up /tmp/file_utf8_title_€: U+20AC from UTF-8 to ISO-8859-1Notice: Applied catalog in 0.04 seconds{code}{code}root@qj5xhpzxp03l1d1:/tmp# puppet apply manifest_file_utf8_title.ppNotice: Compiled catalog for qj5xhpzxp03l1d1.delivery.puppetlabs.net in environment production in 0.08 secondsNotice: /Stage[main]/Main/File[/tmp/file_utf8_title_€]/ensure: defined content as '{md5}12c5472e7479836c84093162660f2a7b'Notice: Applied catalog in 0.20 secondsroot@qj5xhpzxp03l1d1:/tmp# cat file_utf8_title_€This is the file content.root@qj5xhpzxp03l1d1:/tmp# > file_utf8_title_€root@qj5xhpzxp03l1d1:/tmp# cat file_utf8_title_€root@qj5xhpzxp03l1d1:/tmp# puppet apply manifest_file_utf8_title.ppNotice: Compiled catalog for qj5xhpzxp03l1d1.delivery.puppetlabs.net in environment production in 0.08 secondsError: Could not back up /tmp/file_utf8_title_€: U+20AC from UTF-8 to ISO-8859-1Error: Could not back up /tmp/file_utf8_title_€: U+20AC from UTF-8 to ISO-8859-1Error: /Stage[main]/Main/File[/tmp/file_utf8_title_€]/content: change from {md5}d41d8cd98f00b204e9800998ecf8427e to {md5}12c5472e7479836c84093162660f2a7b failed: Could not back up /tmp/file_utf8_title_€: U+20AC from UTF-8 to ISO-8859-1Notice: Applied catalog in 0.04 secondsroot@qj5xhpzxp03l1d1:/tmp# echo $?0root@qj5xhpzxp03l1d1:/tmp# cat file_utf8_title_€root@qj5xhpzxp03l1d1:/tmp#{code}puppet apply exited with exit status 0, and the file is not corrected.This error does not occur when we do this on any of the following platforms:  ubuntu1404-64  centos6-64  centos7-64  redhat6-64  redhat7-64Puppet agent  suie  suite  version: 1.8.1.252.gbdcd028{code}root@qj5xhpzxp03l1d1:~# puppet --version4.8.2root@qj5xhpzxp03l1d1:~#{code} 
 
 
 
 
 
 
 
 
 
 
 
  

Jira (PDOC-150) README links broken after being HTMLfied

2016-12-07 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PDOC-150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: README links broken after being HTMLfied  
 
 
 
 
 
 
 
 
 
 
David Hollinger III it sounds like you may be talking about this issue which I raised against YARD: https://github.com/lsegal/yard/issues/1032. Does that look right? 
It may be an issue with redcarpet, our markdown processing library. YARD delegates rendering markup to HTML to the markdown library. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3216) (docs) Convert nav sidebar to Markdown

2016-12-07 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3216 
 
 
 
  (docs) Convert nav sidebar to Markdown  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 12:45 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
We just did this for the newest versions of our other docs, because nested list elements in HTML are the illegible worst. This way you can easily see the tree structure without having to go crosseyed looking for that last missing ``. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
   

Jira (PDB-3215) transient test failure in command test

2016-12-07 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-3215 
 
 
 
  transient test failure in command test  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 12:39 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
I'm able to reproduce this reliably with 
 
 
 
 
 
 
lein test puppetlabs.puppetdb.command-test
 
 
 
 
 
 
 
but not yet with a full test run. The result is russ's stacktrace here: https://gist.github.com/mullr/bacc19bf3b7e45d73cd706988b4c6b1e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 

Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version

2016-12-07 Thread Christopher Wood (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Wood commented on  PUP-6518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet resource package kernel reports the wrong rpm version  
 
 
 
 
 
 
 
 
 
 
For posterity, the output of the "yum install" command puppet is using, with some debug: 
 
 
 
 
 
 
[root@mail10c2 ~]# /usr/bin/yum -d 1 -e 1 -y install kernel 
 
 
 
 
Package kernel-2.6.32-642.6.2.el6.x86_64 already installed and latest version
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6518) puppet resource package kernel reports the wrong rpm version

2016-12-07 Thread Christopher Wood (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Wood commented on  PUP-6518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet resource package kernel reports the wrong rpm version  
 
 
 
 
 
 
 
 
 
 
And oddly enough, now this is reporting the correct kernel version. 
 
 
 
 
 
 
[root@mail10c2 rpm]# puppet resource package kernel 
 
 
 
 
package { 'kernel': 
 
 
 
 
  ensure => '2.6.32-642.6.2.el6', 
 
 
 
 
}
 
 
 
 
 
 
 
Still puppet 4.4.2 and so on. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To 

Jira (PUP-6518) puppet resource package kernel reports the wrong rpm version

2016-12-07 Thread Christopher Wood (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christopher Wood commented on  PUP-6518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet resource package kernel reports the wrong rpm version  
 
 
 
 
 
 
 
 
 
 
Last question answered first: this is not causing a real problem. I noticed the oddity and filed the bug, little realizing the can of worms that packaging can be. 
At first glance I would expect puppet to report the same as the underlying utilities reported. In my case right now that would be: 
 
 
 
 
 
 
[root@mail10c2 ~]# rpm -q kernel 
 
 
 
 
kernel-2.6.32-220.23.1.el6.x86_64 
 
 
 
 
kernel-2.6.32-642.1.1.el6.x86_64 
 
 
 
 
kernel-2.6.32-642.3.1.el6.x86_64 
 
 
 
 
kernel-2.6.32-642.6.2.el6.x86_64
 
 
 
 
 
 
 
Running "yum info kernel" or "yum info kernel-2.6.32" both provide the same output as each other, namely that there are four packages with "Name: kernel" installed. 
(It does seem like the kernel rpm is the odd one out, in that I can have only one rpm named "puppet-agent" but I can have multiple rpms named "kernel". Perhaps the underlying issue here is the assumption that in an rpm-based system there is only ever one package of a single "name"? Or maybe this is a special-case for kernel rpms on RH-family systems? My Debian laptop here has a kernel package named linux-image-3.16.0-4-amd64 and no other packages have that name.) 
(Mildly off topic: What happens in a multiarch situation? When I say "zlib1g" on a dpkg-based system, how does puppet know if I'm referring to "zlib1g:amd64" or "zlib1g:i386"? Separate bug though if that even ever hits me.) 
The updating comment refers to how 
 
 
 
 
 
 

Jira (PUP-6979) Puppet Module List fails in code page 65001 on ja-JP windows

2016-12-07 Thread Erick Banks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erick Banks commented on  PUP-6979 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Module List fails in code page 65001 on ja-JP windows  
 
 
 
 
 
 
 
 
 
 
Thanks for looking at this Ethan Brown. I'm not familiar with terminal behavior and fonts, is there a confluence page or some other resource I can look at to come up to speed here? After which I can provide more context and the full stack trace if the problem is still reproducible while using the terminal with the correct font/setting. 
Using the default code page of 932 I get the expected results, it lists the modules correctly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6979) Puppet Module List fails in code page 65001 on ja-JP windows

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6979 
 
 
 
  Puppet Module List fails in code page 65001 on ja-JP windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Sprint:
 
 AP Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6850) Make commit formatting check robust

2016-12-07 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to Josh Cooper 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6850 
 
 
 
  Make commit formatting check robust  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 Josh Cooper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6979) Puppet Module List fails in code page 65001 on ja-JP windows

2016-12-07 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown commented on  PUP-6979 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Module List fails in code page 65001 on ja-JP windows  
 
 
 
 
 
 
 
 
 
 
Could you include a full stack trace? 
There are a number of things that you have to do on Windows to get terminals to behave properly (including setting fonts, etc). So I want to make sure we're seeing bad Ruby / Puppet behavior, and not bad Windows behavior. 
Also, what happens in the normal codepage chcp 932? 
If this is deemed a critical issue, it should be added to PUP-6718. Otherwise, it probably belongs in PUP-6719 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6967) Reload puppetserver in puppet acceptance tests

2016-12-07 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-6967 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reload puppetserver in puppet acceptance tests  
 
 
 
 
 
 
 
 
 
 
Kenn Hussey Idk. I'm puppet CI goalie, so spent my puppet-maint time on this. Could be SE I guess? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6944) Reduce the windows spec matrix

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6944 
 
 
 
  Reduce the windows spec matrix  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Grooming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1728) OS X Lion group membership not updated

2016-12-07 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-1728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: OS X Lion group membership not updated  
 
 
 
 
 
 
 
 
 
 
also 
 
 
 
 
 
 
☂ : sudo bundle exec puppet resource user bar ensure=present 
 
 
 
 
Notice: /User[bar]/ensure: created 
 
 
 
 
user { 'bar': 
 
 
 
 
  ensure => 'present', 
 
 
 
 
} 
 
 
 
 
☂ : dscl . read /groups/wheel | grep GroupMembership 
 
 
 
 
GroupMembership: root moses foo 
 
 
 
 
☂ : sudo bundle exec puppet apply -e " group { 'wheel' : ensure => present, members => ['bar', 'moses', 'root'],} " 
 
 
 
 
Notice: Compiled catalog for macbook-pro.local in environment production in 0.06 seconds 
 
 
 
 
Notice: /Stage[main]/Main/Group[wheel]/members: members changed 'root,moses,foo' to 'bar,moses,root' 
 
 
  

Jira (PUP-6944) Reduce the windows spec matrix

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6944 
 
 
 
  Reduce the windows spec matrix  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 Jenkins CI jobs updated to reduce Windows matrix cells 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1536) Add top-level facts to output from `--list-X-groups` commands

2016-12-07 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1536 
 
 
 
  Add top-level facts to output from `--list-X-groups` commands  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Release Notes Summary:
 
 Facter will now output the names of facts that belong to each blockable and cacheable group of facts when using the `--list-block-groups` and `--list-cache-groups` command line options. The group name headers are still the only valid values to add to the `blocklist` and `ttls` fields in the config file, but this change makes it more apparent which facts will be blocked or cached. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6885) Remove warning about server_list and server conflicting

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6885 
 
 
 
  Remove warning about server_list and server conflicting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Team:
 
 Agent & Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1728) OS X Lion group membership not updated

2016-12-07 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-1728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: OS X Lion group membership not updated  
 
 
 
 
 
 
 
 
 
 
I could not repro this on puppet latest / El Capitan: 
 
 
 
 
 
 
☂ : sudo bundle exec puppet apply -e " user { 'foo' : ensure => present, groups => 'wheel' } " 
 
 
 
 
Notice: Compiled catalog for macbook-pro.local in environment production in 0.06 seconds 
 
 
 
 
Notice: /Stage[main]/Main/User[foo]/groups: groups changed 'admin' to ['admin', 'wheel'] 
 
 
 
 
Notice: Applied catalog in 0.90 seconds 
 
 
 
 
  
 
 
 
 
☂ : dscl . read /groups/wheel | grep GroupMembership 
 
 
 
 
GroupMembership: root moses foo
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 

Jira (PUP-6967) Reload puppetserver in puppet acceptance tests

2016-12-07 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-6967 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reload puppetserver in puppet acceptance tests  
 
 
 
 
 
 
 
 
 
 
Josh Cooper which team and sprint should this be assigned to? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6885) Remove warning about server_list and server conflicting

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6885 
 
 
 
  Remove warning about server_list and server conflicting  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Labels:
 
 maintenance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1537) Facter 3.5.0 tarball is broken

2016-12-07 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  FACT-1537 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter 3.5.0 tarball is broken  
 
 
 
 
 
 
 
 
 
 
Ryan McKern can you please provide release notes for this issue? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1728) OS X Lion group membership not updated

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1728 
 
 
 
  OS X Lion group membership not updated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1728) OS X Lion group membership not updated

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1728 
 
 
 
  OS X Lion group membership not updated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 Puppet  successfully  adds members to groups on macOS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1728) OS X Lion group membership not updated

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1728 
 
 
 
  OS X Lion group membership not updated  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 Puppet adds members to groups on macOS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1536) Add top-level facts to output from `--list-X-groups` commands

2016-12-07 Thread Kenn Hussey (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  FACT-1536 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add top-level facts to output from `--list-X-groups` commands  
 
 
 
 
 
 
 
 
 
 
Maggie Dreyer can you please provide release notes for this issue? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1401) Puppet package providers use execpipe, which does not set LC_ALL or LANG

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1401 
 
 
 
  Puppet package providers use execpipe, which does not set LC_ALL or LANG  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Grooming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-5993) Possible intermittent test failure in registry_spec.rb

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5993 
 
 
 
  Possible intermittent test failure in registry_spec.rb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  Grooming  2017-01-25 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-5993) Possible intermittent test failure in registry_spec.rb

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5993 
 
 
 
  Possible intermittent test failure in registry_spec.rb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-5993) Possible intermittent test failure in registry_spec.rb

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5993 
 
 
 
  Possible intermittent test failure in registry_spec.rb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 - If possible, create reproduction case- Find and fix issue- If possible, add acceptance test- Puppet consistently passes CI 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1508) End-to-end POC for string externalization in Facter

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1508 
 
 
 
  End-to-end POC for string externalization in Facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Team:
 
 Agent & Platform 
 
 
 

Team/s:
 
 Agent & Platform 
 
 
 

Epic Status:
 
 To Do 
 
 
 

Epic Name:
 
 End-to-end POC for string externalization in Facter 
 
 
 

Status:
 
 Accepted Open 
 
 
 

Workflow:
 
 Scrum Team Engineering Epic  Workflow 
 
 
 

Issue Type:
 
 Task Epic 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

   

Jira (PUP-4933) Remove cfacter setting

2016-12-07 Thread William Hopper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper commented on  PUP-4933 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Remove cfacter setting  
 
 
 
 
 
 
 
 
 
 
PR is up against master at https://github.com/puppetlabs/puppet/pull/5412 but we can't merge it until we're ready for master to become 5.0. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1525) Swap facts are incorrect on AIX in Facter 3

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1525 
 
 
 
  Swap facts are incorrect on AIX in Facter 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  Grooming  2017-01-11 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1525) Swap facts are incorrect on AIX in Facter 3

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1525 
 
 
 
  Swap facts are incorrect on AIX in Facter 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Labels:
 
 aix-parity 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1525) Swap facts are incorrect on AIX in Facter 3

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1525 
 
 
 
  Swap facts are incorrect on AIX in Facter 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1525) Swap facts are incorrect on AIX in Facter 3

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1525 
 
 
 
  Swap facts are incorrect on AIX in Facter 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 On AIX, 'facter -p swapsize' returns the correct results. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1626) dpkg provider works incorrect on non english locales

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1626 
 
 
 
  dpkg provider works incorrect on non english locales  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1626) dpkg provider works incorrect on non english locales

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1626 
 
 
 
  dpkg provider works incorrect on non english locales  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 - dpkg provider works correctly on non-US locales 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1626) dpkg provider works incorrect on non english locales

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1626 
 
 
 
  dpkg provider works incorrect on non english locales  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Labels:
 
 i18n  needs_repro  utf-8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1626) dpkg provider works incorrect on non english locales

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1626 
 
 
 
  dpkg provider works incorrect on non english locales  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Grooming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1441) --show_diff causes crashes on files with UTF-8 content

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1441 
 
 
 
  --show_diff causes crashes on files with UTF-8 content  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1441) --show_diff causes crashes on files with UTF-8 content

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1441 
 
 
 
  --show_diff causes crashes on files with UTF-8 content  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  Grooming  2017-01-11 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1441) --show_diff causes crashes on files with UTF-8 content

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1441 
 
 
 
  --show_diff causes crashes on files with UTF-8 content  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 - "--show_diff" does not error on files with UTF-8 content- acceptance test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1441) --show_diff causes crashes on files with UTF-8 content

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-1441 
 
 
 
  --show_diff causes crashes on files with UTF-8 content  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 - "--show_diff" does not error on files with UTF-8 content - acceptance test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1728) OS X Lion group membership not updated

2016-12-07 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-1728 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: OS X Lion group membership not updated  
 
 
 
 
 
 
 
 
 
 
See the original Redmine ticket for more context: https://projects.puppetlabs.com/issues/9337 
It's hard to tell whether anything's changed for the better in the intervening years of Puppet and Mac OS releases.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6518) puppet resource package kernel reports the wrong rpm version

2016-12-07 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  PUP-6518 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet resource package kernel reports the wrong rpm version  
 
 
 
 
 
 
 
 
 
 
Christopher Wood what would you expect/want this behavior to be? It seems like the options would be: 1) report all installed versions 2) report latest version 3) report the same version detected with `uname` 
Also, did the comment about updating mean you DO expect puppet to attempt to update, and it does not? Or that its failure to update is what you would expect? 
All of these cases would require adding a special case to the kernel package, which we generally try to avoid. Is there a use case where this is causing a real problem? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6518) puppet resource package kernel reports the wrong rpm version

2016-12-07 Thread Maggie Dreyer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer assigned an issue to Christopher Wood 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6518 
 
 
 
  puppet resource package kernel reports the wrong rpm version  
 
 
 
 
 
 
 
 
 

Change By:
 
 Maggie Dreyer 
 
 
 

Assignee:
 
 Christopher Wood 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6984) alias on Package/Exec resources produces misleading warning

2016-12-07 Thread Sven Mueller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sven Mueller created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6984 
 
 
 
  alias on Package/Exec resources produces misleading warning  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.8.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 10:24 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sven Mueller 
 
 
 
 
 
 
 
 
 
 
An alias on (at least) package and exec resources that worked fine to resolve a dependency at least in Puppet 3.4 doesn't work anymore in Puppet 4.8.0. I would expect that the manifest below would not create the Warning it gives.  (I'm surprised by a warning that the dependency isn't found, but then getting a "dependency failed" on just that resource, though referenced by the title, not the alias, which in turn is OK) 
Almost minimal reproduction case: 
$ cat /tmp/t.pp; sudo puppet apply --detailed-exitcodes /tmp/t.pp; echo $? 
 

$Id$ package {'postfix': alias => 'mta', ensure => latest, }
 
 
exec {'/bin/false': alias => 'something', } 
notify {'Depended on mta': require => [Exec['something'], Package['mta']], } 
Warning: Could not find resource 'Exec[something]' in parameter 'require' (at /tmp/t.pp:12) Warning: Could not find resource 'Package[mta]' in parameter 'require' (at /tmp/t.pp:12) Notice: Compiled catalog for 90cdc197-bd0d-4ee2-8e22-cf4962548eb1 

Jira (PUP-6962) Create Jenkins jobs for running puppet test tiers

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6962 
 
 
 
  Create Jenkins jobs for running puppet test tiers  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Grooming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6963) Puppet doesn't detect systemd as default service provider on CoreOS

2016-12-07 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6963 
 
 
 
  Puppet doesn't detect systemd as default service provider on CoreOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment Reason:
 
 no coreOS test infrastructure available , covered by unit tests 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6963) Puppet doesn't detect systemd as default service provider on CoreOS

2016-12-07 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6963 
 
 
 
  Puppet doesn't detect systemd as default service provider on CoreOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment Reason:
 
 no coreOS test infrastructure available 
 
 
 

QA Risk Assessment:
 
 Needs Assessment No Action 
 
 
 

QA Contact:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6958) Ship locale files as part of the Puppet gem

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6958 
 
 
 
  Ship locale files as part of the Puppet gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP  Grooming  2017-01-25 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6958) Ship locale files as part of the Puppet gem

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6958 
 
 
 
  Ship locale files as part of the Puppet gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6958) Ship locale files as part of the Puppet gem

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6958 
 
 
 
  Ship locale files as part of the Puppet gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Acceptance Criteria:
 
 - MO files for each available locale are shipped as part of the Puppet gem - Documentation specifying load order for files depending on how Puppet is packaged (git vs gem vs AIO vs distro packaging) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3021) User resource on AIX returns a non-working structure or 'attributes'

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3021 
 
 
 
  User resource on AIX returns a non-working structure or 'attributes'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Labels:
 
 AIX aix-parity maintenance  puppethack 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6663) Large volumes of RPM queries leave stale locks on the rpm database

2016-12-07 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6663 
 
 
 
  Large volumes of RPM queries leave stale locks on the rpm database  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment Reason:
 
 low risk, covered decently by unit tests 
 
 
 

QA Risk Assessment:
 
 No Action 
 
 
 

QA Contact:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3021) User resource on AIX returns a non-working structure or 'attributes'

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3021 
 
 
 
  User resource on AIX returns a non-working structure or 'attributes'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Labels:
 
 aix-parity  maintenance 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3021) User resource on AIX returns a non-working structure or 'attributes'

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3021 
 
 
 
  User resource on AIX returns a non-working structure or 'attributes'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Grooming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-3021) User resource on AIX returns a non-working structure or 'attributes'

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3021 
 
 
 
  User resource on AIX returns a non-working structure or 'attributes'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Team:
 
 Agent & Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.

2016-12-07 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6983 
 
 
 
  File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 10:00 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Sean Griffin 
 
 
 
 
 
 
 
 
 
 
If the file name contains a utf8 character, then drift correction fails on ubuntu 1604 and windows (2012r2 and 2016). 
To see for yourself: 
Run puppet apply with this manifest to create a file with a utf8 non ascii character in its name. 
manifest_file_utf8_title.pp: 
 
 
 
 
 
 
file { "/tmp/file_utf8_title_€" : 
 
 
 
 
  ensure => file, 
 
 
 
 
  mode => "0644", 
 
 
 
 
   

Jira (PUP-6945) acceptance: lookup rich data values

2016-12-07 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6945 
 
 
 
  acceptance: lookup rich data values  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6958) Ship locale files as part of the Puppet gem

2016-12-07 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6958 
 
 
 
  Ship locale files as part of the Puppet gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 AP Grooming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1542) Install Facter 3 as a gem

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1542 
 
 
 
  Install Facter 3 as a gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 This epic supports moving the prototype of a facter gem into a reproducible, shippable product.The prototype is available at https://github.com/branan/facter.gem. It is a hand-rolled source gem, with instructions on how to create the binary gem.  This epic covers the creation  of automation to build the source and binary gems, as well as integration of that automation with RE tooling and our normal CI pipelines. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1542) Install Facter 3 as a gem

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1542 
 
 
 
  Install Facter 3 as a gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 This epic supports moving the prototype of a facter gem into a reproducible, shippable product.The prototype is available at https://github.com/branan/facter.gem. It is a hand-rolled source gem, with instructions on how to create the binary gem. This epic covers the creation of automation to build the source and binary gems, as well as integration of that automation with RE tooling and our normal CI pipelines. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1549) Build CFacter gems in Jenkins

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1549 
 
 
 
  Build CFacter gems in Jenkins  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 8:37 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
A Jenkins job (or pipeline) which ties together the following: 
1) Creation of the source gem 2) compilation of the binary gems 3) Publishing of source + binary gems 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 

Jira (PUP-6982) Allow keys to be specified by pattern in lookup_options

2016-12-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6982 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow keys to be specified by pattern in lookup_options  
 
 
 
 
 
 
 
 
 
 
An alternative, and possibly simpler implementation would be to place all patterns under a special key (for example '*') as that would make it easier to differentiate between verbatim and pattern based keys. (The main problem is that keys and special things need to be in the same lookup_options hash). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1548) Create a MacOS binary facter gem

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1548 
 
 
 
  Create a MacOS binary facter gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Acceptance Criteria:
 
 Creation of  32- and  64-bit  Windows  MacOS  facter gems can be run automatically when we release Facter.This gem can be automatically signed/published using existing RE tooling (packaging repo?) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-1548) Create a MacOS binary facter gem

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1548 
 
 
 
  Create a MacOS binary facter gem  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 8:28 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
The general process I found for doing this in the prototype was: 1) Install pl-build-tools and puppet-agent 2) Install the gem-compiler gem into the puppet-agent ruby 3) Grab the source gem 4) run the gem compile command to build the gem 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  

Jira (FACT-1547) Create a Windows binary facter gem

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1547 
 
 
 
  Create a Windows binary facter gem  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 8:27 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
The general process I found for doing this in the prototype was: 1) Install pl-build-tools and puppet-agent 2) Install the gem-compiler gem into the puppet-agent ruby 3) Grab the source gem 4) run the gem compile command to build the gem 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
  

Jira (FACT-1546) Create a binary Linux facter gem

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1546 
 
 
 
  Create a binary Linux facter gem  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 8:23 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
This should be done on an older Linux for maximum compatibility. In the prototype I used Centos 5 as a builder, and ran into no problems copying the gem around elsewhere. 
In the prototype, the build was done with the gem compiler gem. It seemed to work just fine. 
The general process I found for doing this in the prototype was: 1) Install pl-build-tools and puppet-agent 2) Install the gem-compiler gem into the puppet-agent ruby 3) Grab the source gem 4) run the gem compile command to build the gem 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
   

Jira (FACT-1543) Automatically create a facter source gem

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1543 
 
 
 
  Automatically create a facter source gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Acceptance Criteria:
 
 A .gem package can be created automatically from our existing sources when it is time to release a Facter version. This gem can be automatically signed/published using existing RE tooling (packaging repo?) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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-6982) Allow keys to be specified by pattern in lookup_options

2016-12-07 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6982 
 
 
 
  Allow keys to be specified by pattern in lookup_options  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/07 8:15 AM 
 
 
 

Fix Versions:
 

 PUP 4.9.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
Allow keys to be specified by pattern in lookup_options. The reason for wanting this feature is that can become very tedious to specify all keys. While not a big deal when constructing new logic, it becomes a real chore when moving from a hiera.yaml with global merge behavior specified as that potentially could mean adding thousands of entries if moving the hierarchy to an environment hiera 5 hiera.yaml. 
It is also a chore having to list a large number of parameters for classes such as apache where it would be beneficial to state one pattern that applies to the majority and then single out those that are different. 
The rules for the pattern based entries are as follows: 
 

if a key is specified with an exact match it wins over one specified with a pattern in the same layer - this makes it easier to handle exclusions
 

if a key is specified with a pattern, the first pattern that matches in a layer wins (subsequent patterns in the same layer are ignored).
 
   

Jira (FACT-1543) Automatically create a facter source gem

2016-12-07 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1543 
 
 
 
  Automatically create a facter source gem  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Acceptance Criteria:
 
 A .gem package can be created automatically from our existing sources when it is time to release a Facter version. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


  1   2   >