Jira (PUP-1940) Reveal client IP address to autosign script.

2015-07-30 Thread Robert (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert commented on  PUP-1940 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reveal client IP address to autosign script.  
 
 
 
 
 
 
 
 
 
 
This should be reopened. The arbitrary csr attributes are not helpful for this use case, as they are set by the client and not enforced in any way.  
Basically, what I would love to see is a second argument passed to the script with the IP address according to the server (as in, it's looking at the client ip address that is connecting to it). Otherwise the client could have an IP address of 10.32.4.83 but simply add an attribute of 10.73.2.2 and there would literally be no way for the autosign script to tell. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4935) $HOME directory of the Puppet user is writable

2015-07-30 Thread Julien Pivotto (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julien Pivotto commented on  PUP-4935 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: $HOME directory of the Puppet user is writable  
 
 
 
 
 
 
 
 
 
 
There is no immediate problem. But there will be security bugs in these products and putting those directories Read-Only will prevent attackers to create .ssh/* directories for example. It is all about mitigating future bugs that could happen. 
If you need to do advance debugging (su - puppet --shell=/bin/bash ) for example to test your ENC with the puppet user you do not want .bash_history file to be created. 
There is a lot of other services that take that approach. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4935) $HOME directory of the Puppet user is writable

2015-07-30 Thread Julien Pivotto (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julien Pivotto assigned an issue to Jeff McCune 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4935 
 
 
 
  $HOME directory of the Puppet user is writable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Julien Pivotto 
 
 
 

Assignee:
 
 Julien Pivotto Jeff McCune 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4959) Custom facts are missing when modules are shared using VirtualBox

2015-07-30 Thread Juha Vainikka (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Juha Vainikka created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4959 
 
 
 
  Custom facts are missing when modules are shared using VirtualBox  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 debug.txt 
 
 
 

Created:
 

 2015/07/30 3:47 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Juha Vainikka 
 
 
 
 
 
 
 
 
 
 
With following sample project: 
example ├── environments │   ├── local │   │   └── environment.conf │   └── vagrant │   └── environment.conf ├── manifests │   └── site.pp └── modules └── simplefact └── lib └── facter └── helloworld.rb 
$ cat example/environments/local/environment.conf modulepath = c:/example/modules manifest = c:/example/manifests/site.pp 
$ cat example/environments/vagrant/environment.conf modulepath = c:/vagrant/example/modules manifest = c:/vagrant/example/manifests/site.pp 
$ cat example/manifests/site.pp notify {$hello_world: } 
$ cat example/modules/simplefact/lib/facter/helloworld.rb Facter.add("hello_world") do setcode do "foo bar" end end 
Running Puppet 4 (puppet-agent-1.2.2-x64.msi) inside Windows guest gives following output: 
puppet apply --environmentpath environments --environment local manifests\site.pp Notice: Compiled catalog for win2008r2.fi.logica.com in environment local in 0.30 seconds Notice: foo bar Notice: /Stage[main]/Main/Notify[foo bar]/message: defined 'message' as 'foo bar' Notice: Applied catalog in 0.03 seconds 
   

Jira (PUP-4959) Custom facts are missing when modules are shared using VirtualBox

2015-07-30 Thread Juha Vainikka (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Juha Vainikka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4959 
 
 
 
  Custom facts are missing when modules are shared using VirtualBox  
 
 
 
 
 
 
 
 
 

Change By:
 
 Juha Vainikka 
 
 
 
 
 
 
 
 
 
 With following sample project: {noformat} example├── environments│   ├── local│   │   └── environment.conf│   └── vagrant│   └── environment.conf├── manifests│   └── site.pp└── modules└── simplefact└── lib└── facter└── helloworld.rb$ cat example/environments/local/environment.confmodulepath = c:/example/modulesmanifest   = c:/example/manifests/site.pp$ cat example/environments/vagrant/environment.confmodulepath = c:/vagrant/example/modulesmanifest   = c:/vagrant/example/manifests/site.pp$ cat example/manifests/site.ppnotify {$hello_world: }$ cat example/modules/simplefact/lib/facter/helloworld.rbFacter.add("hello_world") do  setcode do"foo bar"  endend {noformat} Running Puppet 4 (puppet-agent-1.2.2-x64.msi) inside Windows guest gives following output:puppet apply --environmentpath environments --environment local manifests\site.ppNotice: Compiled catalog for win2008r2.fi.logica.com in environment local in 0.30 secondsNotice: foo barNotice: /Stage[main]/Main/Notify[foo bar]/message: defined 'message' as 'foo bar'Notice: Applied catalog in 0.03 secondspuppet apply --environmentpath environments --environment vagrant manifests\site.ppError: Evaluation Error: Missing title. The title _expression_ resulted in undef at C:/example/manifests/site.pp:1:9 on node win2008r2.fi.demobox.comBoth environments work with puppet-3.8.1-x64.msi. Currently this prevents us to move to Puppet 4.Full debug output for failing run is provided in attachment. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
   

Jira (PUP-4959) Custom facts are missing when modules are shared using VirtualBox

2015-07-30 Thread Juha Vainikka (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Juha Vainikka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4959 
 
 
 
  Custom facts are missing when modules are shared using VirtualBox  
 
 
 
 
 
 
 
 
 

Change By:
 
 Juha Vainikka 
 
 
 
 
 
 
 
 
 
 With following sample project:{noformat}  example├── environments│   ├── local│   │   └── environment.conf│   └── vagrant│   └── environment.conf├── manifests│   └── site.pp└── modules└── simplefact└── lib└── facter└── helloworld.rb$ cat example/environments/local/environment.confmodulepath = c:/example/modulesmanifest   = c:/example/manifests/site.pp$ cat example/environments/vagrant/environment.confmodulepath = c:/vagrant/example/modulesmanifest   = c:/vagrant/example/manifests/site.pp$ cat example/manifests/site.ppnotify {$hello_world: }$ cat example/modules/simplefact/lib/facter/helloworld.rbFacter.add("hello_world") do  setcode do"foo bar"  endend{noformat}Running Puppet 4 (puppet-agent-1.2.2-x64.msi) inside Windows guest gives following output:puppet apply --environmentpath environments --environment local manifests\site.pp {noformat} Notice: Compiled catalog for win2008r2.fi.logica.com in environment local in 0.30 secondsNotice: foo barNotice: /Stage[main]/Main/Notify[foo bar]/message: defined 'message' as 'foo bar'Notice: Applied catalog in 0.03 seconds {noformat}   puppet apply --environmentpath environments --environment vagrant manifests\site.pp {noformat} Error: Evaluation Error: Missing title. The title _expression_ resulted in undef at C:/example/manifests/site.pp:1:9 on node win2008r2.fi.demobox.com {noformat}   Both environments work with puppet-3.8.1-x64.msi. Currently this prevents us to move to Puppet 4.Full debug output for failing run is provided in attachment. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
   

Jira (PUP-4960) Runtime type does not treat ruby Module correctly.

2015-07-30 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4960 
 
 
 
  Runtime type does not treat ruby Module correctly.  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/30 5:46 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
The Runtime type does not handle the case where the LHS is a ruby Module and RHS is implements that Module. This can be tested using following statement. It will print "Notice: nope" indicating that Array is not assignable to Enumerable. 
 
 
 
 
 
 
puppet apply -e 'if Runtime["ruby","Enumerable"] > Runtime["ruby", "Array"] { notify{yes:} } else { notify{nope:} }'
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
   

Jira (PUP-4961) Population of class parameters does not appear to work for JSON

2015-07-30 Thread Robert Mortimer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Mortimer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4961 
 
 
 
  Population of class parameters does not appear to work for JSON  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/30 6:25 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Robert Mortimer 
 
 
 
 
 
 
 
 
 
 
With the following hira.yaml file 
— :backends: 
 

yaml
 

json :yaml: :datadir: /etc/puppetlabs/code/hieradata :json: :datadir: /etc/puppetlabs/code/hieradata :hierarchy:
 

"% {clientcert} 
"
 

"% {datacenter} 
"
 

"% {osfamily} 
"
 

common
 

Jira (HI-184) Inconsistent handling of fully-qualified facts when called from the command line

2015-07-30 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  HI-184 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Inconsistent handling of fully-qualified facts when called from the command line  
 
 
 
 
 
 
 
 
 
 
PR283 submitted as part of #puppethack. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4490) Pick up bindings from module's Metadata.json

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4490 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pick up bindings from module's Metadata.json  
 
 
 
 
 
 
 
 
 
 
merged to master at: 5a48450 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4490) Pick up bindings from module's Metadata.json

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4490 
 
 
 
  Pick up bindings from module's Metadata.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2015-08- 19 05 
 
 
 

Scope Change Reason:
 
 Adopted because it was ready for merge and now blocking work in sprint 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 

Release Notes Summary:
 
 A module's {{metadata.json}} can now define the name of a 'data in modules' data provider directly without the need of specifying the same using the lower level bindings system which required ruby coding. 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
  

Jira (PUP-4960) Runtime type does not treat ruby Module correctly.

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4960 
 
 
 
  Runtime type does not treat ruby Module correctly.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4960) Runtime type does not treat ruby Module correctly.

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4960 
 
 
 
  Runtime type does not treat ruby Module correctly.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4941) Reserve keywords 'application', 'consumes', and 'produces'

2015-07-30 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4941 
 
 
 
  Reserve keywords 'application', 'consumes', and 'produces'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4941) Reserve keywords 'application', 'consumes', and 'produces'

2015-07-30 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-4941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reserve keywords 'application', 'consumes', and 'produces'  
 
 
 
 
 
 
 
 
 
 
Merged to 3.x at 9f1cc4e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4941) Reserve keywords 'application', 'consumes', and 'produces'

2015-07-30 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-4941 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reserve keywords 'application', 'consumes', and 'produces'  
 
 
 
 
 
 
 
 
 
 
Merged to stable at d42cd2c and master at a165a95. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4941) Reserve keywords 'application', 'consumes', and 'produces'

2015-07-30 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4941 
 
 
 
  Reserve keywords 'application', 'consumes', and 'produces'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2687) File Names with "?" cause failures with recursive copies

2015-07-30 Thread Charlie Sharpsteen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2687 
 
 
 
  File Names with "?" cause failures with recursive copies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Charlie Sharpsteen 
 
 
 

Affects Version/s:
 
 PUP 3.8.1 
 
 
 

Affects Version/s:
 
 PUP 4.2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4942) Puppet Agent - Add automated Windows acceptance tests

2015-07-30 Thread Ryan Gard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard commented on  PUP-4942 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet Agent - Add automated Windows acceptance tests  
 
 
 
 
 
 
 
 
 
 
Michael Smith https://github.com/puppetlabs/pe_acceptance_tests/blob/2015.2.x/setup/agent_upgrade.rb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4055) Support DNF package manager (yum successor)

2015-07-30 Thread JIRA
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gaël Chamoulaud assigned an issue to Gaël Chamoulaud 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4055 
 
 
 
  Support DNF package manager (yum successor)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Gaël Chamoulaud 
 
 
 

Assignee:
 
 Gaël Chamoulaud 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4055) Support DNF package manager (yum successor)

2015-07-30 Thread JIRA
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gaël Chamoulaud assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4055 
 
 
 
  Support DNF package manager (yum successor)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Gaël Chamoulaud 
 
 
 

Assignee:
 
 Gaël Chamoulaud 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Fabrice Bacchella (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Fabrice Bacchella created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.0.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/30 9:15 AM 
 
 
 

Environment:
 
 
 
 
 
 
 
 
# facter --version 
 
 
 
 
3.0.2 (commit 5dc120fa9db4c19150466b1bbd1d0cf42c87c6bd) 
 
 
 
 
# lsb_release -a 
 
 
 
 
LSB Version::core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch 
 
 
 
 
Distributor ID: CentOS 
 
 
 
 
  

Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 
 
Melissa Stone Matthaus Owens are we not building facter on linux platforms with libblkid support? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 
 
For el 5, we don't have blkid support. https://github.com/puppetlabs/puppet-agent/blob/aardwolf/configs/components/facter.rb#L69-L80 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 
 
blkid was added to util-linux in at least version 2.20, and el5 only has 2.13 available. I see three options here: 
 

Add util-linux to the agent. we could opt to just build blkid.
 

Devise an alternate means of getting partition info on older linux
 

Leave the partitions fact out of older linux
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1844) JSON encoding truncates fractional java.util.Date seconds

2015-07-30 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1844 
 
 
 
  JSON encoding truncates fractional java.util.Date seconds  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Rob Browning 
 
 
 

Created:
 

 2015/07/30 10:20 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Rob Browning 
 
 
 
 
 
 
 
 
 
 
Currently, PDB installs a custom encoder for Joda DateTimes, but not for java.util.Dates, and the default Cheshire encoder truncates fractional seconds. I noticed because it was causing PDB to store the truncated time during a node deactivation. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 

Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Fabrice Bacchella (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Fabrice Bacchella commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 
 
Options 3 would be a very bad solution. RHEL5 is still supported by Redhat, and the purpose of facts and puppet is to manage old or strange installation, so sysadmin don't have to fight with each corner case and expect consistent results in an heterogenous datacenter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 
 
Fabrice Bacchella Yea, it absolutely wouldn't be my first choice. I just listed it for completeness. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1807) PR (1547): (maint) Add access to packaging repo - melissa

2015-07-30 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1807 
 
 
 
  PR (1547): (maint) Add access to packaging repo - melissa  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Scope Change Reason:
 
 noncritical submission from releng 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-30 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1816 
 
 
 
  PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Scope Change Reason:
 
 required to make extensions work after patch in core 
 
 
 

Scope Change Category:
 
 Found 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1809) Slow response times to aggregate-event-counts endpoint queries

2015-07-30 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1809 
 
 
 
  Slow response times to aggregate-event-counts endpoint queries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Scope Change Reason:
 
 perf issues discovered in PE testing 
 
 
 

Scope Change Category:
 
 Found 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr

2015-07-30 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1817 
 
 
 
  PR (1552): (maint) rollup 2.3.x to stable - mullr  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Scope Change Reason:
 
 we do these routinely, we just don't usually use PRs for them 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 
 
It's this a regression from 2.x for this kernel? That is to say, is `/sys/block/` and `/dev/disk/by-uuid/` present? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4962) One test failour on IBM z Systems

2015-07-30 Thread Lei Zhang (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lei Zhang created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4962 
 
 
 
  One test failour on IBM z Systems  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Components:
 

 Platform, Test Infrastructure 
 
 
 

Created:
 

 2015/07/30 10:56 AM 
 
 
 

Environment:
 
 
Operation system: RHEL 6, RHEL7, SLES 11 and SLES 12 Platform: IBM z system 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Lei Zhang 
 
 
 
 
 
 
 
 
 
 
We have performed the test suite on IBM z platform. The one z platform specific failure is 
"rspec ./spec/unit/indirector/file_bucket_file/file_spec.rb:43 # Puppet::FileBucketFile::File non-stubbing tests when servicing a save request fails if the contents collide with existing contents" 
This is due to the difference of endianness, since z systems use big endianness. This test is used to test contents collision, where an MD5 collision is constructed in the test. However, in the test, the MD5 digest is represent in a little endian UINT type. So when ported to z systems, such MD5 collision is not valid. This caused the failure of this particular test.  
A quick workaround is to reconstruct the MD5 collision by converting the little endian to big endian _expression_ in the test file: " ./spec/unit/indirector/file_bucket_file/file_spec.rb". 
Original code: " first_contents = [0x61653

Jira (PUP-4962) One test failure on IBM z Systems

2015-07-30 Thread Lei Zhang (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lei Zhang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4962 
 
 
 
  One test failure on IBM z Systems  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lei Zhang 
 
 
 

Summary:
 
 One test  failour  failure  on IBM z Systems 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4490) Pick up bindings from module's Metadata.json

2015-07-30 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4490 
 
 
 
  Pick up bindings from module's Metadata.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4926) Relationship with a parameter does not work

2015-07-30 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4926 
 
 
 
  Relationship with a parameter does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4780) enhance versioncmp() error checking as it only accepts strings

2015-07-30 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4780 
 
 
 
  enhance versioncmp() error checking as it only accepts strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 
 
Ah. blkid is in a different package on el4/el5. This may be fixable by just linking against and building against e2fsprogs-devel on el5. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Scrum Team:
 
 Release Engineering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Scrum Team:
 
 Release Engineering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5  
 
 
 
 
 
 
 
 
 
 
I've linked a PR that adds a build dependency on e2fsprogs for el5. This gets the partition fact working. The output is still off however. 
 
 
 
 
 
 
[root@w4zx4x1v6z0t8a9 ~]# rpm -Uvh puppet-agent-1.2.1.136.g82c26c1-1.el5.i386.rpm  
 
 
 
 
Preparing...### [100%] 
 
 
 
 
   1:puppet-agent   ### [100%] 
 
 
 
 
[root@w4zx4x1v6z0t8a9 ~]# /opt/puppetlabs/bin/facter partitions 
 
 
 
 
{ 
 
 
 
 
  /dev/VolGroup00/LogVol00 => { 
 
 
 
 
filesystem => "ext3", 
 
 
 
 
size => "0 bytes", 
 
 
 
 
size_bytes => 0, 
 
 
 
 
uuid => "eff0db7e-020b-409f-94af-c758112f745b" 
 

Jira (FACT-1152) facter partitions don't work on Centos 5, sles10, fedora

2015-07-30 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 5, sles10, fedora  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Summary:
 
 facter partitions don't work on Centos 5 , sles10, fedora 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 5, sles10, fedora

2015-07-30 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 5, sles10, fedora  
 
 
 
 
 
 
 
 
 
 
I updated the summary to reflect the other affected distros. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Summary:
 
 facter partitions don't work on Centos  4/  5, sles10, fedora 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4926) Relationship with a parameter does not work

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4926 
 
 
 
  Relationship with a parameter does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3172) Config_version should be logged on master and agent

2015-07-30 Thread Charlie Sharpsteen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Charlie Sharpsteen commented on  PUP-3172 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Config_version should be logged on master and agent  
 
 
 
 
 
 
 
 
 
 
For the agent side of things, setting log_level to info will cause a message containing the catalog version to be printed to the system log: 
 
 
 
 
 
 
Jul 30 18:08:14 pe-201520-master puppet-agent[11787]: Applying configuration version '1438279674'
 
 
 
 
 
 
 
For the server side, things are much more complicated. Basically, the "Compiled catalog" message that gets printed is part of a benchmarking operation. This means that the text of the message is generated before the catalog, and thus the version number, is created. 
So, we can do only one of the following: 
 

Log the time it took to compile the catalog (the choice we're using today).
 
 
 

Log the catalog version.
 
 
 

Refactor a lot of the logging and benchmarking code so that it is possibly to log both the elapsed time and an attribute of the result.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
  

Jira (PUP-4196) agent command line options ignored running under systemd

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4196 
 
 
 
  agent command line options ignored running under systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4196) agent command line options ignored running under systemd

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens assigned an issue to Matthaus Owens 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4196 
 
 
 
  agent command line options ignored running under systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Assignee:
 
 Scott Garman Matthaus Owens 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4196) agent command line options ignored running under systemd

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4196 
 
 
 
  agent command line options ignored running under systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Story Points:
 
 5 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4196) agent command line options ignored running under systemd

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4196 
 
 
 
  agent command line options ignored running under systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Scope Change Reason:
 
 PuppetHack fun times 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4196) agent command line options ignored running under systemd

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4196 
 
 
 
  agent command line options ignored running under systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Sprint:
 
 RE 2015-08- 26 12 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4863) Add node definitions for Fedora 22 to the source repos

2015-07-30 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone commented on  PUP-4863 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add node definitions for Fedora 22 to the source repos  
 
 
 
 
 
 
 
 
 
 
Kylo Ginsberg who is the best person to add these in? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 
 
Looks like the 0 size and size_bytes is because /sys/class/block doesn't exist on these older linuxes. https://github.com/puppetlabs/facter/blob/0ed194909fbdfbca06ed8def10ddcce411ebbcea/lib/src/facts/linux/filesystem_resolver.cc#L156-L164 needs to be updated to do something smarter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 
 
Ruby facter used '/sys/block' instead of '/sys/class/block' here. That does exist on both older and newer linuxes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4926) Relationship with a parameter does not work

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Relationship with a parameter does not work  
 
 
 
 
 
 
 
 
 
 
Validated on puppet-agent SHA: bfd1653c81d563ebdcc8ede3efb721a3a1dab50a on redhat-7-x86_64 
 
 
 
 
 
 
[root@bbhygv90p9l957z ~]# cat test.pp 
 
 
 
 
notify { '1': 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
define mynotify(Type[Notify] $req) { 
 
 
 
 
  notify { 
 
 
 
 
$title: 
 
 
 
 
  } 
 
 
 
 
  $req -> Mynotify[$title] 
 
 
 
 
} 
 
 
 
 
  
 

Jira (PUP-4926) Relationship with a parameter does not work

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4926 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Relationship with a parameter does not work  
 
 
 
 
 
 
 
 
 
 
Validated on puppet-agent SHA: bfd1653c81d563ebdcc8ede3efb721a3a1dab50a on redhat-7-x86_64 
 
 
 
 
 
 
[root@bbhygv90p9l957z ~]# cat test.pp 
 
 
 
 
notify { '1': 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
define mynotify(Type[Notify] $req) { 
 
 
 
 
  notify { 
 
 
 
 
$title: 
 
 
 
 
  } 
 
 
 
 
  $req -> Mynotify[$title] 
 
 
 
 
} 
 
 
 
 
  
 

Jira (PUP-4926) Relationship with a parameter does not work

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4926 
 
 
 
  Relationship with a parameter does not work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Comment:
 
 Validated on puppet-agent SHA: bfd1653c81d563ebdcc8ede3efb721a3a1dab50a on  redhat-7-x86_64{code}[root@bbhygv90p9l957z ~]# cat test.ppnotify { '1':}define mynotify(Type[Notify] $req) {  notify {$title:  }  $req -> Mynotify[$title]}mynotify {'2':  req => Notify['1']}[root@bbhygv90p9l957z ~]# puppet apply --test test.ppNotice: Compiled catalog for bbhygv90p9l957z.delivery.puppetlabs.net in environment production in 0.33 secondsInfo: Applying configuration version '1438285031'Notice: 1Notice: /Stage[main]/Main/Notify[1]/message: defined 'message' as '1'Notice: 2Notice: /Stage[main]/Main/Mynotify[2]/Notify[2]/message: defined 'message' as '2'Notice: Applied catalog in 0.02 seconds[root@bbhygv90p9l957z ~]# puppet --version4.2.1{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Sprint:
 
 RE 2015-08-12 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Scrum Team:
 
 Release Engineering 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Scope Change Reason:
 
 PuppetHack ing 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthaus Owens 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1123) Facter explodes with invalid locales

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1123 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter explodes with invalid locales  
 
 
 
 
 
 
 
 
 
 
Acceptance test PR#4115 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1440) implement sum, avg, min, and max

2015-07-30 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1440 
 
 
 
  implement sum, avg, min, and max  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Sprint:
 
 PuppetDB 2015-08-12 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1440) implement sum, avg, min, and max

2015-07-30 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1440 
 
 
 
  implement sum, avg, min, and max  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-1440) implement sum, avg, min, and max

2015-07-30 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-1440 
 
 
 
  implement sum, avg, min, and max  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Scope Change Reason:
 
 hack day 
 
 
 

Scope Change Category:
 
 Adopted 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3432) More verbose logging on invalid parameters

2015-07-30 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  PUP-3432 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: More verbose logging on invalid parameters  
 
 
 
 
 
 
 
 
 
 
This appears to be working properly as of v3.7.4. 
 
 
 
 
 
 
[rnelson0@build01 ~]$ cat test.pp 
 
 
 
 
class docker ( 
 
 
 
 
  $tcp_bind = 'bind', 
 
 
 
 
) { 
 
 
 
 
  notify{'::docker':} 
 
 
 
 
  notify{"$tcp_bind":} 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
class profile { 
 
 
 
 
  notify{'profile':} 
 
 
 
 
  class {'docker': 
 
 
 

Jira (FACT-1123) Facter explodes with invalid locales

2015-07-30 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1123 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter explodes with invalid locales  
 
 
 
 
 
 
 
 
 
 
Shaigy Nixon That PR should be targetted at Facter, not Puppet. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4669) Varargs support for (defined) types (and possibly classes)

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4669 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Varargs support for (defined) types (and possibly classes)  
 
 
 
 
 
 
 
 
 
 
In any case, support for this should not be added before the refactored argument passing and type checking has been merged (PUP-4458, PUP-2315). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4862) Get pre-suites working for Ubuntu 15.04

2015-07-30 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone commented on  PUP-4862 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Get pre-suites working for Ubuntu 15.04  
 
 
 
 
 
 
 
 
 
 
Kylo Ginsberg is there a good person to bug about this ticket? Who normally takes this on? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4780) enhance versioncmp() error checking as it only accepts strings

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4780 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: enhance versioncmp() error checking as it only accepts strings  
 
 
 
 
 
 
 
 
 
 
Validated on puppet-agent SHA:bfd1653c81d563ebdcc8ede3efb721a3a1dab50a on redhat-7-x86_64 
 
 
 
 
 
 
[root@bbhygv90p9l957z ~]# puppet apply -e '$foo=5.43; versioncmp($foo, "5.43")' 
 
 
 
 
Error: Evaluation Error: Error while evaluating a Function Call, function 'versioncmp' called with mis-matched arguments 
 
 
 
 
expected: 
 
 
 
 
  versioncmp(String a, String b) - arg count {2} 
 
 
 
 
actual: 
 
 
 
 
  versioncmp(Float, String) - arg count {2}  at line 1:12 on node bbhygv90p9l957z.delivery.puppetlabs.net 
 
 
 
 
  
 
 
 
 
[root@bbhygv90p9l957z ~]# puppet apply -e '$foo=5.43; versioncmp( "5.43", $foo)' 
 
 
 
 
Error: Evaluation Error: Error while evaluating a Function Call, function 'versioncmp' called with mis-matched arguments 
 
 
 
 
   

Jira (PUP-4863) Add node definitions for Fedora 22 to the source repos

2015-07-30 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone commented on  PUP-4863 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add node definitions for Fedora 22 to the source repos  
 
 
 
 
 
 
 
 
 
 
And PUP-4864 as well 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4516) Agent does not stop with Ctrl-C

2015-07-30 Thread Andreas Ntaflos (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Ntaflos commented on  PUP-4516 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Agent does not stop with Ctrl-C  
 
 
 
 
 
 
 
 
 
 
FWIW: a workaround (if you can call it that) is to put the running Puppet agent process in the background with Ctrl-Z and then destroy it with pkill -9 -f 'puppet agent'. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4780) enhance versioncmp() error checking as it only accepts strings

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4780 
 
 
 
  enhance versioncmp() error checking as it only accepts strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4516) Agent does not stop with Ctrl-C

2015-07-30 Thread Alyssa (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alyssa commented on  PUP-4516 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Agent does not stop with Ctrl-C  
 
 
 
 
 
 
 
 
 
 
Well, SIGKILL will not let puppet perform any cleanup. I wound up rebuilding the rpm with a patch since I'm not using ruby 2.0. Not ideal, but I doubt I'll be upgrading to another 3.x release before I go on to 4.x. 
 
 
 
 
 
 
--- daemon.rb	2015-07-30 13:38:51.888321942 -0500 
 
 
 
 
+++ daemon.rb.new	2015-07-30 13:38:35.653308093 -0500 
 
 
 
 
@@ -112,8 +112,13 @@ 
 
 
 
 
 signals.update({:HUP => :restart, :USR1 => :reload, :USR2 => :reopen_logs }) unless Puppet.features.microsoft_windows? 
 
 
 
 
 signals.each do |signal, method| 
 
 
 
 
   Signal.trap(signal) do 
 
 
 
 
-Puppet.notice "Caught #{signal}; storing #{method}" 
 
 
 
 
-@signals << method 
 
 
 
 
+if method == :stop 
 
 
 
 
+  Puppet.notice "Caugh

Jira (PUP-3694) puppet cert fingerprint invalidhost returns zero instead of non-zero

2015-07-30 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  PUP-3694 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: puppet cert fingerprint invalidhost returns zero instead of non-zero  
 
 
 
 
 
 
 
 
 
 
PR submitted to address the non-zero exit code. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 
 
Matthaus Owens do you want me to make the patch to facter or will you submit the PR? Using /sys/block should be fine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene assigned an issue to Matthaus Owens 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1152 
 
 
 
  facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Assignee:
 
 Matthaus Owens 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4961) Population of class parameters does not appear to work for JSON

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4961 
 
 
 
  Population of class parameters does not appear to work for JSON  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 With the following hira.yaml file {code:yaml} ---:backends:  - yaml  - json:yaml:  :datadir: /etc/puppetlabs/code/hieradata:json:  :datadir: /etc/puppetlabs/code/hieradata:hierarchy:  - "%{clientcert}"  - "%{datacenter}"  - "%{osfamily}"  - common {code} This will aitomaticly populate ntp {code:yaml} ntp::servers:  - ntp1.corp.com  - ntp2.corp.comntp::restrict:  - 127.0.0.1ntp::service_manage: false {code} But this will not {code:yaml} "ntp":{ "servers" : [ "ntp1.corp.com", "ntp2.corp.com" ], "restrict" : ["127.0.0.1"], "service_manage" : "false"} {code} I love the auto loading of class variables but want to use JSON 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4961) Population of class parameters does not appear to work for JSON

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4961 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Population of class parameters does not appear to work for JSON  
 
 
 
 
 
 
 
 
 
 
That is correct, the example that does not work is wrong - that is not how it is designed to work. You need to specify the full keys, your "servers" key does not automatically become "ntp::servers" - yaml has no such magic. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4490) Pick up bindings from module's Metadata.json

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4490 
 
 
 
  Pick up bindings from module's Metadata.json  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4946) Contain, include functions should be rvalue, return class reference(s)

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4946 
 
 
 
  Contain, include functions should be rvalue, return class reference(s)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1152) facter partitions don't work on Centos 4/5, sles10, fedora

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 
 
Peter Huene I'm working on a PR. /sys/block is slightly more complicated than i initially thought. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4946) Contain, include functions should be rvalue, return class reference(s)

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4946 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Contain, include functions should be rvalue, return class reference(s)  
 
 
 
 
 
 
 
 
 
 
This should be simple to achieve by just dropping the :statement status and making sure it always returns a reference (or possibly nil). With future parser on 3.x and with 4.x the distinction between rvalue and statement functions is moot - the only difference is that statement functions automatically have their return value set to nil by the evaluator to ensure they do not unintentionally leak values. 
The function should return instances of types - e.g. use Puppet::Pops::Types::TypeFactory to create class or resource references. 
Some thought needs to go into what to do wrt one versus multiple value returns - should it always be an array? If so, is an empty array acceptable? (It can cause strange effects if placed in the middle of a dependency chain). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4939) Error message for lowercase type in require param is not meaningful.

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4939 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error message for lowercase type in require param is not meaningful.   
 
 
 
 
 
 
 
 
 
 
this _expression_: 
 
 
 
 
 
 
sqlserver_instance['MSSQLSERVER']
 
 
 
 
 
 
 
Does not look right - it is basically the same as trying to take a substring out of a string - e.g. this: 
 
 
 
 
 
 
'sqlserver_instance'['MSSQLSERVER']
 
 
 
 
 
 
 
which fails because 'MSSQLSERVER' is not an integer. 
You probably wanted: 
 
 
 
 
 
 
Sqlserver_instance['MSSQLSERVER']
 
 
 
 
 
 
 
(Note the capital S). That is a reference to a resource of Sqlserver_instance type. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
   

Jira (PUP-4939) Error message for lowercase type in require param is not meaningful.

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4939 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error message for lowercase type in require param is not meaningful.   
 
 
 
 
 
 
 
 
 
 
Closed with won't fix, because there is no difference between bare words and strings, and it is a legit operation to take a substring of a string - the error is meaningful in that context - e.g: 
 
 
 
 
 
 
notice "hello world"[6,2]
 
 
 
 
 
 
 
would notice 'wo' 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4963) "puppet module build" fails on FIPS-enabled system

2015-07-30 Thread Jared Jennings (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jared Jennings created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4963 
 
 
 
  "puppet module build" fails on FIPS-enabled system  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.7.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Modules 
 
 
 

Created:
 

 2015/07/30 3:39 PM 
 
 
 

Environment:
 
 
RHEL Workstation 6.6, configured for FIPS compliance. 
It appears you can trip this bug without the toil of complete compliance by setting OPENSSL_FORCE_FIPS_MODE=foo in your environment. Any value set for this variable turns on the behavior; to turn it off you must unset the variable. You should also be able to replicate the behavior on CentOS or Fedora. 
 
 
 

Labels:
 

 fips 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Jared Jennings 
 
 
 
 
 
 
 
 
 
 

Jira (PUP-4485) Add a 'hiera' data provider

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4485 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a 'hiera' data provider  
 
 
 
 
 
 
 
 
 
 
After lots of discussions and back and forth on this. I think this is the best: 
 
 
 
 
 
 
--- 
 
 
 
 
:version: 4 
 
 
 
 
:hierarchy: 
 
 
 
 
  - { name: 'yaml1' 
 
 
 
 
  backend: yaml, 
 
 
 
 
  datadir: 'some path',  
 
 
 
 
  paths: 
 
 
 
 
  - "path" 
 
 
 
 
  - "path" 
 
 
 
 
 } 
 
 
 
 
  - { name: 'yaml2' 
 
 
 

Jira (PUP-4905) Add feature switch for appmgmt

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4905 
 
 
 
  Add feature switch for appmgmt  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Sprint:
 
 Language 2015-08- 19 05 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4905) Add feature switch for appmgmt

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4905 
 
 
 
  Add feature switch for appmgmt  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4196) agent command line options ignored running under systemd

2015-07-30 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens commented on  PUP-4196 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: agent command line options ignored running under systemd  
 
 
 
 
 
 
 
 
 
 
Merged into 3.x in https://github.com/puppetlabs/puppet/commit/b7bf08905eaef20a5a4b4e1901b779456582d0e7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4928) PMT calculates puppetlabs/concat dependencies incorrectly

2015-07-30 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4928 
 
 
 
  PMT calculates puppetlabs/concat dependencies incorrectly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Anderson Mills 
 
 
 

Scrum Team:
 
 Code Management 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1123) Facter explodes with invalid locales

2015-07-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1123 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter explodes with invalid locales  
 
 
 
 
 
 
 
 
 
 
Thanks Michael Smith. Moved the PR to Facter PR#1086 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4905) Add feature switch for appmgmt

2015-07-30 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4905 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add feature switch for appmgmt  
 
 
 
 
 
 
 
 
 
 
A PR is now up with the following: 
 

A feature switch app_management (and yes, a feature switch is very much needed)
 

When the switch is on the lexer delivers the tokens APPLICATION, CONSUMES, and PRODUCES to the parser
 

When the switch is off the lexer delivers the tokens APPLICATION_R, CONSUMES_R, and PRODUCES_R to the parser
 
 
Earlier the tokens XXX_R were added with the functionality that they trigger a warning, but otherwise behave as bare words (strings). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4862) Get pre-suites working for Ubuntu 15.04

2015-07-30 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4862 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Get pre-suites working for Ubuntu 15.04  
 
 
 
 
 
 
 
 
 
 
Melissa Stone per https://confluence.puppetlabs.com/display/RE/New+Platform+Process this is a QENG ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4864) Get pre-suites working for Fedora 22

2015-07-30 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4864 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Get pre-suites working for Fedora 22  
 
 
 
 
 
 
 
 
 
 
Melissa Stone per https://confluence.puppetlabs.com/display/RE/New+Platform+Process this is a QENG ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4863) Add node definitions for Fedora 22 to the source repos

2015-07-30 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4863 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add node definitions for Fedora 22 to the source repos  
 
 
 
 
 
 
 
 
 
 
Melissa Stone pre https://confluence.puppetlabs.com/display/RE/New+Platform+Process this is a QENG ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


  1   2   >