Jira (FACT-1021) Custom facts that require 'facter' cannot be evaluated from command line facter

2015-06-04 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1021 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Custom facts that require 'facter' cannot be evaluated from command line facter  
 
 
 
 
 
 
 
 
 
 
Validated on redhat-7-x86_64, win2012r2-rubyx64 and ubuntu-1404-x86_64 with puppet-agent build SHA 473b953a4f1ff9504f7541dec4b2f008f8c4838c http://builds.puppetlabs.lan/puppet-agent/473b953a4f1ff9504f7541dec4b2f008f8c4838c/ 
 
 
 
 
 
 
 
 
 
 
 
root@asxwtzqcadayryf ~]# cat foo/foo.rb 
 
 
 
 
require 'facter' 
 
 
 
 
Facter.add(:foo) do 
 
 
 
 
  setcode do 
 
 
 
 
'bar' 
 
 
 
 
  end 
 
 
 
 
end 
 
 
 
 
 
 
 
 
 
[root@asxwtzqcadayryf ~]# facter --custom-dir ./foo foo 
 
 
 
   

Jira (FACT-1021) Custom facts that require 'facter' cannot be evaluated from command line facter

2015-06-03 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1021 
 
 
 
  Custom facts that require 'facter' cannot be evaluated from command line facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Medium 
 
 
 

QA Risk Severity Reason:
 
 Noworkaround 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Risk Probability Reason:
 
 Mediumusage 
 
 
 

QA Highest Test Level:
 
 Unit 
 
 
 

QA Risk Assessment Reason:
 
 Medium 
 
 
 

QA Contact:
 
 ShaigyNixon 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 

Jira (FACT-1021) Custom facts that require 'facter' cannot be evaluated from command line facter

2015-06-03 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1021 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Custom facts that require 'facter' cannot be evaluated from command line facter  
 
 
 
 
 
 
 
 
 
 
Validated on RedHat 7 on Puppet Agent SHA d7e14c3bdd255b15173c62176298a9f4882162ed 
 
 
 
 
 
 
[root@cx31v7oge8hftxp myfactor]# cat roles.rb 
 
 
 
 
require 'facter' 
 
 
 
 
Facter.add ('roles') do 
 
 
 
 
  setcode do 
 
 
 
 
'Admin' 
 
 
 
 
  end 
 
 
 
 
end 
 
 
 
 
[root@cx31v7oge8hftxp myfactor]# cfacter --custom-dir ./ roles 
 
 
 
 
Admin
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Jira (PUP-2638) Puppet apply fails to write the graph if puppet agent has never run

2015-06-08 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2638 
 
 
 
  Puppet apply fails to write the graph if puppet agent has never run  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 QA ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2638) Puppet apply fails to write the graph if puppet agent has never run

2015-06-08 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-2638 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet apply fails to write the graph if puppet agent has never run  
 
 
 
 
 
 
 
 
 
 
Validated in Puppet-agent at http://builds.puppetlabs.lan/puppet-agent/39dace1e049eaac7bf6c71e0792f60f688b2e63b/ Without the fix, puppet apply -e notice 'foo' --graph command failed if the $vardir/state/graphs did not exist. With the fix, the 'graphs' directory gets created if it does not exist and the command succeeds. 
On redhat-7-x86_64: 
 
 
 
 
 
 
[root@ivgninqjda847ry ~]# puppet config print vardir 
 
 
 
 
/opt/puppetlabs/puppet/cache 
 
 
 
 
[root@ivgninqjda847ry ~]# ls /opt/puppetlabs/puppet/cache/state 
 
 
 
 
state.yaml 
 
 
 
 
[root@ivgninqjda847ry ~]# puppet apply -e notice 'foo' --graph 
 
 
 
 
Notice: Scope(Class[main]): foo 
 
 
 
 
Notice: Compiled catalog for ivgninqjda847ry.delivery.puppetlabs.net in environment production in 0.33 seconds 
 
 
 
 
Notice: Applied catalog in 0.02 seconds 
 
 
 
 
[root@ivgninqjda847ry ~]# ls /opt/puppetlabs/puppet/cache/state 
 
   

Jira (PUP-4668) cannot create a define named something that starts with 'class'

2015-06-08 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4668 
 
 
 
  cannot create a define named something that starts with 'class'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 QA ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4668) cannot create a define named something that starts with 'class'

2015-06-08 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4668 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: cannot create a define named something that starts with 'class'  
 
 
 
 
 
 
 
 
 
 
Validated against 4.x on redhat-7-x86_64 at http://builds.puppetlabs.lan/puppet-agent/39dace1e049eaac7bf6c71e0792f60f688b2e63b/  
 
 
 
 
 
 
[root@ivgninqjda847ry modules]# cat classroom/manifests/boo.pp 
 
 
 
 
define classroom::boo{ 
 
 
 
 
  notify { $name: } 
 
 
 
 
} 
 
 
 
 
[root@ivgninqjda847ry modules]# cat classroom/tests/init.pp 
 
 
 
 
classroom::boo { 'Hi There' :} 
 
 
 
 
notify { 'test' : 
 
 
 
 
  require = Classroom::Boo[ 'Hi There'], 
 
 
 
 
} 
 
 
 
 
[root@ivgninqjda847ry modules]# puppet apply classroom/tests/init.pp 
 
 
 
  

Jira (PUP-4668) cannot create a define named something that starts with 'class'

2015-06-08 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4668 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: cannot create a define named something that starts with 'class'  
 
 
 
 
 
 
 
 
 
 
Verified in 4.x on redhat-7-x86_64 at http://builds.puppetlabs.lan/puppet-agent/39dace1e049eaac7bf6c71e0792f60f688b2e63b/ 
 
 
 
 
 
 
[root@ivgninqjda847ry modules]# cat classroom/manifests/boo.pp 
 
 
 
 
define classroom::boo{ 
 
 
 
 
  notify { $name: } 
 
 
 
 
} 
 
 
 
 
[root@ivgninqjda847ry modules]# cat classroom/tests/init.pp 
 
 
 
 
classroom::boo { 'Hi There' :} 
 
 
 
 
notify { 'test' : 
 
 
 
 
  require = Classroom::Boo[ 'Hi There'], 
 
 
 
 
} 
 
 
 
 
[root@ivgninqjda847ry modules]# puppet apply classroom/tests/init.pp 
 
 
 
 

Jira (PUP-4668) cannot create a define named something that starts with 'class'

2015-06-09 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4668 
 
 
 
  cannot create a define named something that starts with 'class'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2638) Puppet apply fails to write the graph if puppet agent has never run

2015-06-09 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-2638 
 
 
 
  Puppet apply fails to write the graph if puppet agent has never run  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Status:
 
 Reviewed 
 
 
 

Original Estimate:
 
 0minutes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1016) Repeated resolution of a facter fact causes never GC'd object references

2015-06-25 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1016 
 
 
 
  Repeated resolution of a facter fact causes never GC'd object references  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1016) Repeated resolution of a facter fact causes never GC'd object references

2015-06-25 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1016 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Repeated resolution of a facter fact causes never GC'd object references  
 
 
 
 
 
 
 
 
 
 
Validated in puppet-agent build SHA=51c29325d56cb50d2162fbf07fb010b4ced4deda on redhat-6-x86_64.yaml 
 
 
 
 
 
 
[root@abzxixf33ic30c8 ~]# cat foo/bar.rb 
 
 
 
 
(0..99).each do 
 
 
 
 
  Facter.add('bar') do 
 
 
 
 
setcode do 
 
 
 
 
  'Testing' 
 
 
 
 
end 
 
 
 
 
  end 
 
 
 
 
end 
 
 
 
 
 
 
 
 
 
[root@abzxixf33ic30c8 ~]# facter bar --custom-dir ./foo 
 
 
 
 
Testing 

Jira (PUP-4522) Provide Facts for a classifier to select whether to enable overriding the environment

2015-06-10 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4522 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide Facts for a classifier to select whether to enable overriding the environment  
 
 
 
 
 
 
 
 
 
 
Validated on ubuntu-1404-x86_64 at http://builds.puppetlabs.lan/puppet-agent/63b82667d8fc652f59a73d363fdf5f09eabececf/ No environment specified in puppet.conf or CLI: 
 
 
 
 
 
 
# cat /etc/puppetlabs/code/environments/production/manifests/site.pp 
 
 
 
 
notify{$environment:} 
 
 
 
 
notify { 'mymsg': message = agent_specified_environment=$agent_specified_environment} 
 
 
 
 
[root@vfxq8y0gzf0aftq manifests]# cat /etc/puppetlabs/puppet/puppet.conf 
 
 
 
 
# This file can be used to override the default puppet settings. 
 
 
 
 
# See the following links for more details on what settings are available: 
 
 
 
 
# - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html 
 
 
 
 
# - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html 
 
 
 
 
# - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html 
 
 

Jira (PUP-4709) Square braces in title confuse puppet 4 parser

2015-06-11 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4709 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Square braces in title confuse puppet 4 parser  
 
 
 
 
 
 
 
 
 
 
Validated on redhat-7-x86_64 on stable at http://builds.puppetlabs.lan/puppet-agent/ab115b9a582aedfec7f7f87bf737bd9d0db5f9df/ 
 
 
 
 
 
 
[root@b8aafaw162aadff ~]# puppet apply -e 'notify { [foo] bar: } ; notify { [foo] baz: }' 
 
 
 
 
Notice: Compiled catalog for b8aafaw162aadff.delivery.puppetlabs.net in environment production in 0.37 seconds 
 
 
 
 
Notice: [foo] bar 
 
 
 
 
Notice: /Stage[main]/Main/Notify[[foo] bar]/message: defined 'message' as '[foo] bar' 
 
 
 
 
Notice: [foo] baz 
 
 
 
 
Notice: /Stage[main]/Main/Notify[[foo] baz]/message: defined 'message' as '[foo] baz' 
 
 
 
 
Notice: Applied catalog in 0.04 seconds
 
 
 
 
 
 
 
Validated on redhat-7-x86_64 on http://builds.puppetlabs.lan/puppet-agent/df8786db8e1eb50e11cc0864c532ee7125d30fd6/ 
 
 
 
 
 
 
[root@ch5wm67af3t9fvm ~]# puppet apply -e notify {'[foo]bar':}; notify {'[foo]baz':} 
   

Jira (PUP-4709) Square braces in title confuse puppet 4 parser

2015-06-11 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4709 
 
 
 
  Square braces in title confuse puppet 4 parser  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-765) The gid fact is ill-constrained on Windows (ID.EXE is called if it exists)

2015-06-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-765 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: The gid fact is ill-constrained on Windows (ID.EXE is called if it exists)  
 
 
 
 
 
 
 
 
 
 
Validated on 2.x on win2012r2-rubyx64 using source https://github.com/puppetlabs/facter/tree/2.x 
 
 
 
 
 
 
$ cmd /c facter PATH 
 
 
 
 
C:\cygwin64\usr\local\bin;C:\cygwin64\bin;C:\Program Files (x86)\Puppet Labs\Puppet Enterprise\bin;C:\Program Files\Puppet Labs\Puppet Enterprise\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\pstools;C:\cygwin64\bin 
 
 
 
 
 
 
 
 
 
$ cat C:\cygwin64\usr\local\bin\id.exe 
 
 
 
 
echo Hello 
 
 
 
 
 
 
 
 
 
$ cmd /c facter gid 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Administrator@qsjevb7fe418ri9 ~
 
 
 
  

Jira (FACT-765) The gid fact is ill-constrained on Windows (ID.EXE is called if it exists)

2015-06-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-765 
 
 
 
  The gid fact is ill-constrained on Windows (ID.EXE is called if it exists)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 QA ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1044) kernelmajversion inconsistently reported in Debian 8

2015-06-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1044 
 
 
 
  kernelmajversion inconsistently reported in Debian 8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 BrananRiley ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1044) kernelmajversion inconsistently reported in Debian 8

2015-06-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1044 
 
 
 
  kernelmajversion inconsistently reported in Debian 8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon BrananRiley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4522) Provide Facts for a classifier to select whether to enable overriding the environment

2015-06-10 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4522 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide Facts for a classifier to select whether to enable overriding the environment  
 
 
 
 
 
 
 
 
 
 
Validated with agent on win2012r2-rubyx64 and master on redhat-7-x86_64 at http://builds.puppetlabs.lan/puppet-agent/63b82667d8fc652f59a73d363fdf5f09eabececf/ 1) No environment specified in puppet.conf or CLI: 
 
 
 
 
 
 
[root@xaul27wskviboa4 ~]# cat /etc/puppetlabs/code/environments/production/manifests/site.pp 
 
 
 
 
notify{$environment:} 
 
 
 
 
notify { 'mymsg': message = agent_specified_environment=$agent_specified_environment} 
 
 
 
 
 
 
 
 
 
$ cmd /c puppet agent -t --server xaul27wskviboa4.delivery.puppetlabs.net 
 
 
 
 
Info: Retrieving pluginfacts 
 
 
 
 
Info: Retrieving plugin 
 
 
 
 
Info: Caching catalog for dzb9cvtfu8plprx.delivery.puppetlabs.net 
 
 
 
 
Info: Applying configuration version '1433971421' 
 
 
 
 
  

Jira (FACT-982) Warnings about not being able to resolve custom facts with --no-custom-facts

2015-06-01 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-982 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Warnings about not being able to resolve custom facts with --no-custom-facts  
 
 
 
 
 
 
 
 
 
 
Michael Smith Sorry, my bad. Changed the status back. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1056) Operatingsystem major release not resolved in OSX

2015-07-01 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1056 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Operatingsystem major release not resolved in OSX  
 
 
 
 
 
 
 
 
 
 
Validated on puppet-agent SHA 3d67503e963f4f09b26fe2800fb13670b5f748a2: On osx-1010-x86_64: 
 
 
 
 
 
 
q3uw05sblidigy5:~ root# uname -a 
 
 
 
 
Darwin q3uw05sblidigy5 14.1.0 Darwin Kernel Version 14.1.0: Thu Feb 26 19:26:47 PST 2015; root:xnu-2782.10.73~1/RELEASE_X86_64 x86_64 
 
 
 
 
q3uw05sblidigy5:~ root# puppet --version 
 
 
 
 
4.2.0 
 
 
 
 
q3uw05sblidigy5:~ root# facter --version 
 
 
 
 
3.0.1 (commit 97fcfb6395f3aba974d7ea103d516621942889f4) 
 
 
 
 
q3uw05sblidigy5:~ root# facter os 
 
 
 
 
{ 
 
 
 
 
  architecture = x86_64, 
 
 
 
 
  family = Darwin, 
 
 

Jira (FACT-1073) Operatingsystem release facts not properly resolved in Arch Linux

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


 
 
 
 
 
 
 Facter /  FACT-1073 
 
 
 
  Operatingsystem release facts not properly resolved in Arch Linux  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1056) Operatingsystem major release not resolved in OSX

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


 
 
 
 
 
 
 Facter /  FACT-1056 
 
 
 
  Operatingsystem major release not resolved in OSX  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1073) Operatingsystem release facts not properly resolved in Arch Linux

2015-07-01 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1073 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Operatingsystem release facts not properly resolved in Arch Linux  
 
 
 
 
 
 
 
 
 
 
Since Arch Linux is not supported and the fix is already validated on OSX for 

FACT-1056
, resolving without validation. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4789) hiera_include does not have access to variables from node scope when future parser is enabled

2015-06-29 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4789 
 
 
 
  hiera_include does not have access to variables from node scope when future parser is enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1082) COM initialization prior to ruby COM initialization

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


 
 
 
 
 
 
 Facter /  FACT-1082 
 
 
 
  COM initialization prior to ruby COM initialization  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-31 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


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

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4602) 'bsd' service provider doesn't work with rcng

2015-08-11 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4602 
 
 
 
  'bsd' service provider doesn't work with rcng  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 Noplatformtovarify 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (FACT-1128) Intermittent failure attaching process to job object

2015-08-11 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1128 
 
 
 
  Intermittent failure attaching process to job object  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment:
 
 Medium Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1147) Interfaces with multiple IPs are not facted correctly

2015-08-12 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1147 
 
 
 
  Interfaces with multiple IPs are not facted correctly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-08-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Peter Huene 
 
 
 
 
 
 
 
 
 
 


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

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon PeterHuene 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-08-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1152 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: facter partitions don't work on Centos 4/5, sles10, fedora  
 
 
 
 
 
 
 
 
 
 
Validated on CentOS 5 and sles-10-x86_64 and facter partitions still doesn't seem to work. On CentOS 5: 
 
 
 
 
 
 
[root@xe9a8z5mtk07eil ~]# /opt/puppetlabs/puppet/bin/facter --version 
 
 
 
 
3.0.2 (commit a97fb7fe372449bb54457d6eebbfc32703afe0ba) 
 
 
 
 
 
 
 
 
 
[root@xe9a8z5mtk07eil ~]# /opt/puppetlabs/bin/facter partitions 
 
 
 
 
 
 
 
 
 
[root@xe9a8z5mtk07eil ~]# 
 
 
 
 
 
 
 
 
 
[root@xe9a8z5mtk07eil ~]# /opt/puppetlabs/bin/facter -d partitions 
 
 
 
 
2015-08-17 14:42:13.414068 INFO  puppetlabs.facter - executed with command line: -d partitions. 
 
 
 
 
2015-08-17 14:42:13.414886 INFO  leatherman.ruby:136 - ruby loaded from /opt/puppetlabs/puppet/lib/libruby.so.2.1.0. 
   

Jira (FACT-1155) Failing facter tests on solaris 10 i386

2015-08-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1155 
 
 
 
  Failing facter tests on solaris 10 i386  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 Settingtolowsincenobuildsareavailableforrunningacceptancetestrightnow.Willbecoveredinacceptancetesteventually. 
 
 
 

QA Highest Test Level:
 
 Acceptance 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Severity Reason:
 
 acceptancetestshouldpass. 
 
 
 

QA Risk Probability:
 
 Medium 
 
 
 

QA Risk Severity:
 
 High 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (FACT-1155) Failing facter tests on solaris 10 i386

2015-08-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1155 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Failing facter tests on solaris 10 i386  
 
 
 
 
 
 
 
 
 
 
No build to run acceptance test. Resolving now. Will be covered in acceptance test when the build becomes available. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-08-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


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

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4953) fails to create authorized_key file with puppet on sles-10-i386

2015-08-18 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4953 
 
 
 
  fails to create authorized_key file with puppet on sles-10-i386  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 Settingtolowsinceitisalreadygettestedinexistingacceptancetest 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1158) Facter::Util::Resolution.exec on Windows fails to exec paths with spaces

2015-08-24 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1158 
 
 
 
  Facter::Util::Resolution.exec on Windows fails to exec paths with spaces  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4605) With a systemd masked service: 'enable=true ensure=running' doesn't work

2015-08-18 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4605 
 
 
 
  With a systemd masked service: 'enable=true ensure=running' doesn't work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 Shouldbeabletostartamaskedservice 
 
 
 

QA Highest Test Level:
 
 Unit 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (FACT-1135) Port Manjaro Linux os facts to Facter 3

2015-08-18 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1135 
 
 
 
  Port Manjaro Linux os facts to Facter 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 unsupportedplatform 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4822) Regression PMT cannot connect to forge on OSX

2015-08-18 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4822 
 
 
 
  Regression PMT cannot connect to forge on OSX  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4489) Add data_provider to module metadata

2015-08-18 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4489 
 
 
 
  Add data_provider to module metadata  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1156) Solaris 10 builds throw warnings, core dump when built without Debug

2015-08-18 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1156 
 
 
 
  Solaris 10 builds throw warnings, core dump when built without Debug  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4777) Puppet gem dependencies are out of date

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


 
 
 
 
 
 
 Puppet /  PUP-4777 
 
 
 
  Puppet gem dependencies are out of date  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-4777) Puppet gem dependencies are out of date

2015-06-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4777 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet gem dependencies are out of date  
 
 
 
 
 
 
 
 
 
 
Validated on SHA:df66ab55dc9dff4fb0c69074485dd663aa2d4a20 
 
 
 
 
 
 
[shaigynixon@puppetlabs452 ~/jun30-puppet]# git clone https://github.com/puppetlabs/puppet.git 
 
 
 
 
Cloning into 'puppet'... 
 
 
 
 
remote: Counting objects: 192859, done. 
 
 
 
 
remote: Compressing objects: 100% (137/137), done. 
 
 
 
 
remote: Total 192859 (delta 88), reused 14 (delta 14), pack-reused 192706 
 
 
 
 
Receiving objects: 100% (192859/192859), 47.52 MiB | 1.80 MiB/s, done. 
 
 
 
 
Resolving deltas: 100% (139352/139352), done. 
 
 
 
 
Checking connectivity... done. 
 
 
 
 
[shaigynixon@puppetlabs452 ~/jun30-puppet]# cd puppet/ 
 
 
 
 
[shaigynixon@puppetlabs452 ~/jun30-puppet/puppet:master]# git checkout master 
  

Jira (PUP-4777) Puppet gem dependencies are out of date

2015-06-30 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4777 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet gem dependencies are out of date  
 
 
 
 
 
 
 
 
 
 
On win-2012r2-x86_64 SHA:df66ab55dc9dff4fb0c69074485dd663aa2d4a20: 
 
 
 
 
 
 
C:\Users\Administratorgem install puppet-4.2.0.55-x64-mingw32.gem 
 
 
 
 
Fetching: ffi-1.9.9-x64-mingw32.gem (100%) 
 
 
 
 
Successfully installed ffi-1.9.9-x64-mingw32 
 
 
 
 
Fetching: win32-dir-0.4.9.gem (100%) 
 
 
 
 
Successfully installed win32-dir-0.4.9 
 
 
 
 
Fetching: win32-security-0.2.5.gem (100%) 
 
 
 
 
Successfully installed win32-security-0.2.5 
 
 
 
 
Fetching: facter-2.4.4-x64-mingw32.gem (100%) 
 
 
 
 
Successfully installed facter-2.4.4-x64-mingw32 
 
 
 
 
Fetching: json_pure-1.8.2.gem (100%) 
 
 

Jira (FACT-1123) Facter explodes with invalid locales

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


 
 
 
 
 
 
 Facter /  FACT-1123 
 
 
 
  Facter explodes with invalid locales  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-29 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1123 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Facter explodes with invalid locales  
 
 
 
 
 
 
 
 
 
 
I can write the acceptance test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-29 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1123 
 
 
 
  Facter explodes with invalid locales  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Severity:
 
 High 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity Reason:
 
 puppetcoredumps,installationfailureforpuppetserver 
 
 
 

QA Risk Assessment:
 
 High 
 
 
 

QA Highest Test Level:
 
 Acceptance 
 
 
 

QA Risk Assessment Reason:
 
 Coredumpisugly,gracefulexitistheway 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 
   

Jira (FACT-1123) Facter explodes with invalid locales

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


 
 
 
 
 
 
  Re: Facter explodes with invalid locales  
 
 
 
 
 
 
 
 
 
 
Validated on puppet-agent SHA:8abae21edbcb02b9dc69be5bbb2b705782906416 on redhat-6-x86_64 
 
 
 
 
 
 
[root@d3050pybgrii6u7 ~]# LANG=ABC facter facterversion 
 
 
 
 
2015-07-29 16:41:20.412917 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C 
 
 
 
 
3.0.2 
 
 
 
 
[root@d3050pybgrii6u7 ~]# LANG=ABC puppet --version 
 
 
 
 
2015-07-29 16:41:30.708799 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C 
 
 
 
 
4.2.1
 
 
 
 
 
 
 
On ubuntu-1404-x86_64 
 
 
 
 
 
 
root@j4o02ukn4xwtozm:~# LANG=ABCD facter facterversion 
 
 
 
 
2015-07-29 16:38:50.606899 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C 
 
 
 
  

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 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (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:
 
 Validatedonpuppet-agentSHA:bfd1653c81d563ebdcc8ede3efb721a3a1dab50aonredhat-7-x86_64{code}[root@bbhygv90p9l957z~]#cattest.ppnotify{'1':}definemynotify(Type[Notify]$req){notify{$title:}$req-Mynotify[$title]}mynotify{'2':req=Notify['1']}[root@bbhygv90p9l957z~]#puppetapply--testtest.ppNotice:Compiledcatalogforbbhygv90p9l957z.delivery.puppetlabs.netinenvironmentproductionin0.33secondsInfo:Applyingconfigurationversion'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:Appliedcatalogin0.02seconds[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 (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-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 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-1140) Facter should translate invalid bytes in DMI data to something representable in UTF-8

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


 
 
 
 
 
 
 Facter /  FACT-1140 
 
 
 
  Facter should translate invalid bytes in DMI data to something representable in UTF-8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Probability Reason:
 
 OnlyonIntelNUC 
 
 
 

QA Risk Assessment Reason:
 
 hardwarespecific,noinfrastructuretotest,passingitthrough 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

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 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1144) Memory resolver for OpenBSD

2015-08-11 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1144 
 
 
 
  Memory resolver for OpenBSD  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 OpenBSD,notsupported 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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, 

Jira (FACT-1150) Don't pick scope:link over scope:global IP addresses

2015-08-13 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1150 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Don't pick scope:link over scope:global IP addresses  
 
 
 
 
 
 
 
 
 
 
Validated on sles-10-x86_64: 
 
 
 
 
 
 
 
 
 
 
 
evdmi0pnlt6w4fo:/etc/sysconfig/network # facter --version 
 
 
 
 
3.0.2 (commit 32b5cf62ed2e682f8d0e00d9a59eb7ccf44afdb0) 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
evdmi0pnlt6w4fo:/etc/sysconfig/network # ifconfig 
 
 
 
 
eth0  Link encap:Ethernet  HWaddr 00:50:56:8F:8F:59 
 
 
 
 
  inet addr:10.32.121.15  Bcast:10.32.127.255  Mask:255.255.240.0 
 
 
 
 
  inet6 addr: 2001:db8:0:f101::1/64 Scope:Global 
 
 
 
 
  inet6 addr: fe80::250:56ff:fe8f:8f59/64 Scope:Link 
 
 
 
  

Jira (FACT-1150) Don't pick scope:link over scope:global IP addresses

2015-08-13 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1150 
 
 
 
  Don't pick scope:link over scope:global IP addresses  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1147) Interfaces with multiple IPs are not facted correctly

2015-08-13 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Peter Huene 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1147 
 
 
 
  Interfaces with multiple IPs are not facted correctly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon PeterHuene 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1147) Interfaces with multiple IPs are not facted correctly

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1147 
 
 
 
  Interfaces with multiple IPs are not facted correctly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5014) Base class for JSON/msgpack indirection termini calls log_exception() wrong

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-5014 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Base class for JSON/msgpack indirection termini calls log_exception() wrong  
 
 
 
 
 
 
 
 
 
 
Low risk, resolving. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1046) Use augparse --version instead of augtool for wider platform compatibility

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1046 
 
 
 
  Use augparse --version instead of augtool for wider platform compatibility  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1147) Interfaces with multiple IPs are not facted correctly

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1147 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Interfaces with multiple IPs are not facted correctly  
 
 
 
 
 
 
 
 
 
 
Validated on sles-10-x86_64: 
 
 
 
 
 
 
 
 
 
 
 
d6pi828hstgvi84:~ # facter ipaddress_lo 
 
 
 
 
127.0.0.1 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
d6pi828hstgvi84:~ # ip addr show lo 
 
 
 
 
1: lo: LOOPBACK,UP mtu 16436 qdisc noqueue 
 
 
 
 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 
 
 
 
 
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 
 
 
 
 
inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo 
 
 
 
 

Jira (FACT-1137) facter productname fails on CentOS 5 (kernels before 2.6.23)

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1137 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: facter productname fails on CentOS 5 (kernels before 2.6.23)  
 
 
 
 
 
 
 
 
 
 
Validated on centos-5-x86_64: 
 
 
 
 
 
 
[root@fcoybq3det240fp ~]# dmidecode -s  system-product-name 
 
 
 
 
VMware Virtual Platform 
 
 
 
 
 
 
 
 
 
[root@fcoybq3det240fp ~]# facter productname 
 
 
 
 
VMware Virtual Platform 
 
 
 
 
 
 
 
 
 
[root@fcoybq3det240fp ~]# facter --version 
 
 
 
 
3.0.2 (commit a77fde3191b4e578dd92ec485216cddcf8fbfcc2)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 

Jira (FACT-1046) Use augparse --version instead of augtool for wider platform compatibility

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1046 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Use augparse --version instead of augtool for wider platform compatibility  
 
 
 
 
 
 
 
 
 
 
Validated on redhat-7-x86_64: 
 
 
 
 
 
 
[root@yr2zfzn03uiuvn2 ~]# facter --version 
 
 
 
 
3.0.2 (commit a77fde3191b4e578dd92ec485216cddcf8fbfcc2) 
 
 
 
 
 
 
 
 
 
[root@yr2zfzn03uiuvn2 ~]# facter augeasversion 
 
 
 
 
1.4.0
 
 
 
 
 
 
 
On ubuntu-1404-x86_64: 
 
 
 
 
 
 
root@pmite2pl4p57tun:~# facter --version 
 
 
 
 
3.0.2 (commit a77fde3191b4e578dd92ec485216cddcf8fbfcc2) 
 
 
 
 
 
 
 
 
 
root@pmite2pl4p57tun:~# facter augeasversion 
 
 

Jira (FACT-1137) facter productname fails on CentOS 5 (kernels before 2.6.23)

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1137 
 
 
 
  facter productname fails on CentOS 5 (kernels before 2.6.23)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1046) Use augparse --version instead of augtool for wider platform compatibility

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1046 
 
 
 
  Use augparse --version instead of augtool for wider platform compatibility  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1046) Use augparse --version instead of augtool for wider platform compatibility

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1046 
 
 
 
  Use augparse --version instead of augtool for wider platform compatibility  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 Needtomakesurefacterworkwiththenewutility 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (PUP-5014) Base class for JSON/msgpack indirection termini calls log_exception() wrong

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-5014 
 
 
 
  Base class for JSON/msgpack indirection termini calls log_exception() wrong  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5014) Base class for JSON/msgpack indirection termini calls log_exception() wrong

2015-08-14 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-5014 
 
 
 
  Base class for JSON/msgpack indirection termini calls log_exception() wrong  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-08-11 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


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

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 Trivialchange 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 

QA Risk Probability:
 
 Medium 
 
 
 

QA Risk Severity:
 
 Low 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

Jira (PUP-4622) Add a diff command in Puppet filebucket

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


 
 
 
 
 
 
 Puppet /  PUP-4622 
 
 
 
  Add a diff command in Puppet filebucket  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4622) Add a diff command in Puppet filebucket

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


 
 
 
 
 
 
 Puppet /  PUP-4622 
 
 
 
  Add a diff command in Puppet filebucket  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Severity:
 
 High 
 
 
 

QA Risk Probability:
 
 Medium 
 
 
 

QA Risk Assessment:
 
 High 
 
 
 

QA Highest Test Level:
 
 Acceptance 
 
 
 

QA Risk Assessment Reason:
 
 Newfeature 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section

2015-07-21 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4886 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: puppet_agent module doesn't touch puppet.conf settings outside an INI section  
 
 
 
 
 
 
 
 
 
 
Validated on centos-7 on puppet_agent module SHA:29e776a1b64867f5dcf42dc34a0fd56d9cc2a873 
Steps to reproduce: 1) Install 3.x on Master and Agent 2) Upgrade Master to 4.x 3) Install puppet_agent module on Master 4) On Agent, modify puppet.conf and add values for 'preview_outputdir' and 'modulepath' globally as well as inside 'main' section. 5) Classify the Agent node with puppet_agent module 6) After classification, 'preview_outputdir' and 'modulepath' values should be pruned from the new puppet.conf on Agent from both global and 'main' sections. (Before the fix, the global settings were left untouched and only settings under 'main' section were removed) 
puppet.conf on agent before applying puppet_agent module 
 
 
 
 
 
 
 
 
 
 
 
[root@a8bmd0kkpukbt4l ~]# cat /etc/puppet/puppet.conf 
 
 
 
 
preview_outputdir = /tmp/preview 
 
 
 
 
modulepath = /tmp/modules 
 
 
 
 
 
 
 
 
 
[main] 
 
 
 
 
server = xqh7ofj91ykp0yy.delivery.puppetlabs.net 
 
 
 
 
# The Puppet log directory. 
 
 
 

Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section

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


 
 
 
 
 
 
 Puppet /  PUP-4886 
 
 
 
  puppet_agent module doesn't touch puppet.conf settings outside an INI section  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Medium 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Highest Test Level:
 
 Acceptance 
 
 
 

QA Risk Assessment Reason:
 
 Affectsexistingconfigurationonupgrade 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (FACT-1126) Windows timezone fact uses strftime instead of wcsftime.

2015-07-16 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1126 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Windows timezone fact uses strftime instead of wcsftime.  
 
 
 
 
 
 
 
 
 
 
Steps to reproduce: 1) On win2012, goto Control Panel 2) From 'Clock, Language and Region' section choose 'Add a Language' option 3) 'Change your language preferences ' = 'Add a language' to get a list of available languages. 4) 'German = Open' and then 'German(Germany)=add' 5)From the Language window, Deutsch(Deutschland)=options=Download and Install language pack, to install the new language pack. 6) After successfully installing the new language pack, on the Language window, move up the Deutsch language to the top to make it the primary language. 7) From the Language window=Advanced settings=Override for default input method, choose English from the drop down list. 8) Now to change the time zone, click on the time displayed at the bottom = Change Date and Time settings=Change Time Zone, choose UTC+1 for Brussles, Copenhagen, Madrid, Paris and click OK. 8) Log out and log back in 9) From the command prompt run 'facter' and 'puppet agent -t' 
Validated on win-2012r2-x86_64 on SHA: 8a146ff6a0972c7eb81c40441eface329f628ad5 
 
 
 
 
 
 
C:\Users\Administratorfacter timezone 
 
 
 
 
Mitteleuropische Sommerzeit 
 
 
 
 
 
 
 
 
 
C:\Users\Administratorpuppet agent -t --server octlggp6qf2jk8m.delivery.puppetl 
 
 
 
 
abs.net 
 
 
 
 
Info: Retrieving pluginfacts 
 
 
 
 
Info: Retrieving plugin 
 
 
 
 
 

Jira (FACT-1126) Windows timezone fact uses strftime instead of wcsftime.

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


 
 
 
 
 
 
 Facter /  FACT-1126 
 
 
 
  Windows timezone fact uses strftime instead of wcsftime.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1126) Windows timezone fact uses strftime instead of wcsftime.

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


 
 
 
 
 
 
 Facter /  FACT-1126 
 
 
 
  Windows timezone fact uses strftime instead of wcsftime.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Highest Test Level:
 
 Unit 
 
 
 

QA Risk Assessment Reason:
 
 MaynotbeabletomanageanoderunningGerman 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (FACT-1126) Windows timezone fact uses strftime instead of wcsftime.

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


 
 
 
 
 
 
 Facter /  FACT-1126 
 
 
 
  Windows timezone fact uses strftime instead of wcsftime.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4629) Augeas onlyif does not work when using arrays to match against

2015-07-16 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4629 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Augeas onlyif does not work when using arrays to match against  
 
 
 
 
 
 
 
 
 
 
Validated on redhat-7-x86_64 on SHA:5db4ab78503f1d2117d93e35deb705d5a5ea7d03 
 
 
 
 
 
 
[root@pqvnkh5kywn34ul manifests]# puppet --version 
 
 
 
 
4.2.0 
 
 
 
 
 
 
 
 
 
[root@pqvnkh5kywn34ul manifests]# cat /etc/ssh/sshd_config | grep PermitRootLogin 
 
 
 
 
#PermitRootLogin yes 
 
 
 
 
# the setting of PermitRootLogin without-password. 
 
 
 
 
 
 
 
 
 
[root@pqvnkh5kywn34ul manifests]# cat /etc/ssh/sshd_config | grep HostKey 
 
 
 
 
# HostKey for protocol version 1 
 
 
 
 
#HostKey /etc/ssh/ssh_host_key 
 
 
 
 

Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error

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


 
 
 
 
 
 
 Puppet /  PUP-4848 
 
 
 
  Global parser = future with environment.conf parser = current gives an error  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1134) operatingsystem fact for OEL7 returning RedHat

2015-07-17 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1134 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: operatingsystem fact for OEL7 returning RedHat  
 
 
 
 
 
 
 
 
 
 
Validated on oracle-7-x86_64 on SHA: 46a07cfd5fe6ca2a463c2503768cb25fefe9f103: 
 
 
 
 
 
 
[root@fjpge1fpysge3lk ~]# facter osfamily 
 
 
 
 
RedHat 
 
 
 
 
[root@fjpge1fpysge3lk ~]# facter operatingsystem 
 
 
 
 
OracleLinux 
 
 
 
 
[root@fjpge1fpysge3lk ~]# facter --version 
 
 
 
 
3.0.1 (commit 2020702efb0c8ad235fb78bbb843cde8dc16bb97)
 
 
 
 
 
 
 
On oracle-6-x86_64: 
 
 
 
 
 
 
[root@bhutxfozxh0xptl ~]# facter osfamily 
 
 
 
 
RedHat 
 
 
 
 
[root@bhutxfozxh0xptl ~]# facter operatingsystem 
 
 

Jira (FACT-1134) operatingsystem fact for OEL7 returning RedHat

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


 
 
 
 
 
 
 Facter /  FACT-1134 
 
 
 
  operatingsystem fact for OEL7 returning RedHat  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Highest Test Level Reason:
 
 Manual? 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Risk Assessment Reason:
 
 Modulesdependingonthefactwillfailasmentionedintheoriginalticket 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (PUP-4847) Custom facts not loaded when using puppet resource command

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


 
 
 
 
 
 
 Puppet /  PUP-4847 
 
 
 
  Custom facts not loaded when using puppet resource command  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4847) Custom facts not loaded when using puppet resource command

2015-07-13 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4847 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Custom facts not loaded when using puppet resource command  
 
 
 
 
 
 
 
 
 
 
Validated on redhat-6-x86_64 SHA=a0f4030a10eb873538c25d105ec822dbab44840c. Installed puppetlabs-firewall module and created a firewall resource. 
 
 
 
 
 
 
#puppet module install puppetlabs-firewall 
 
 
 
 
[root@nnxiotspfan5q3a ~]# ls /etc/puppetlabs/code/environments/production/modules/ 
 
 
 
 
firewall 
 
 
 
 
[root@nnxiotspfan5q3a ~]# puppet resource firewall --trace --debug | grep iptables_version 
 
 
 
 
Debug: Facter: searching for custom fact iptables_version. 
 
 
 
 
Debug: Facter: searching for iptables_version.rb in /etc/puppetlabs/code/environments/production/modules/firewall/lib/facter. 
 
 
 
 
Info: Facter: loading custom facts from /etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rb. 
 
 
 
 
Debug: Facter: fact iptables_version has resolved to 1.4.7. 
 
 
 
 
 
 
 
 
   

Jira (PUP-4826) meaning of Integer[0] different in a ruby function

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


 
 
 
 
 
 
 Puppet /  PUP-4826 
 
 
 
  meaning of Integer[0] different in a ruby function  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4826) meaning of Integer[0] different in a ruby function

2015-07-13 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4826 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: meaning of Integer[0] different in a ruby function  
 
 
 
 
 
 
 
 
 
 
Validated on redhat-6-x86_64 on SHA=a0f4030a10eb873538c25d105ec822dbab44840c: Integer data type: 
 
 
 
 
 
 
 
 
 
 
 
[root@nnxiotspfan5q3a modules]# cat /etc/puppetlabs/code/environments/production/modules/test/lib/puppet/functions/test/f.rb 
 
 
 
 
class test { 
 
 
 
 
Puppet::Functions.create_function(:'test::f') do 
 
 
 
 
  dispatch :f do 
 
 
 
 
required_param 'Integer[5]', :n 
 
 
 
 
  end 
 
 
 
 
 
 
 
 
 
  def f(n) 
 
 
 
 
 puts n 
 
 
 
 
   

Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section

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


 
 
 
 
 
 
 Puppet /  PUP-4886 
 
 
 
  puppet_agent module doesn't touch puppet.conf settings outside an INI section  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4848) Global parser = future with environment.conf parser = current gives an error

2015-07-20 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4848 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Global parser = future with environment.conf parser = current gives an error  
 
 
 
 
 
 
 
 
 
 
Validated on redhat-7-x86_64 with the PE package http://enterprise.delivery.puppetlabs.net/3.8/ci-ready/puppet-enterprise-3.8.2-rc0-el-7-x86_64.tar 
Steps used to reproduce: 1) Install PE 2) Set 'parser = future' in the 'main' section of /etc/puppetlabs/puppet/puppet.conf 3) Create /etc/puppetlabs/puppet/environments/production/environment.conf and add line 'parser = current' 4) Modify the default node definition in /etc/puppetlabs/puppet/environments/production/manifests/site.pp 5) Restart pe-puppetserver service 6) Run puppet agent -t 
 
 
 
 
 
 
 
 
 
 
 
[root@fdo6062k8k4lxdg manifests]# cat /etc/puppetlabs/puppet/puppet.conf | grep parser 
 
 
 
 
parser = future 
 
 
 
 
[root@fdo6062k8k4lxdg manifests]# cat /etc/puppetlabs/puppet/environments/production/environment.conf 
 
 
 
 
#env.conf 
 
 
 
 
  parser = current 
 
 
 
 
 
 
 
 
 
[root@fdo6062k8k4lxdg manifests]# tail -13 /etc/puppetlabs/puppet/environments/production/manifests/site.pp 
 
 
 
 

Jira (FACT-1158) Facter::Util::Resolution.exec on Windows fails to exec paths with spaces

2015-08-24 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1158 
 
 
 
  Facter::Util::Resolution.exec on Windows fails to exec paths with spaces  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

QA Risk Assessment Reason:
 
 breakscustomfactsinmodule 
 
 
 

QA Highest Test Level:
 
 Unit 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

QA Risk Probability:
 
 Low 
 
 
 

QA Risk Severity:
 
 Medium 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

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

Jira (FACT-1158) Facter::Util::Resolution.exec on Windows fails to exec paths with spaces

2015-08-24 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  FACT-1158 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Facter::Util::Resolution.exec on Windows fails to exec paths with spaces  
 
 
 
 
 
 
 
 
 
 
Validated on Windows-2012r2-x86_64: 
Steps to reproduce: 1) On windows, install git using a browser 2) Install puppetlabs/git module puppet module install puppetlabs/git 3) copy C:\ProgramData\PuppetLabs\Puppet\code\environment\production\modules\git\lib\facter\git_version.rb C:\tmp 4) Check for custom fact git_version  facter --custom-dir=c:\tmp git_version 
 
 
 
 
 
 
c:\tmpfacter --version 
 
 
 
 
3.0.2 (commit 0e5cf30f6a565b08da9ef926302059aeb0b9e2b8) 
 
 
 
 
 
 
 
 
 
c:\tmpfacter --custom-dir=c:\tmp git_version 
 
 
 
 
2.5.0.windows.1 
 
 
 
 
 
 
 
 
 
c:\tmpfacter -p git_version 
 
 
 
 
2.5.0.windows.1 
 
 
 
 

 
 
 
 
 
 
  

Jira (FACT-1082) COM initialization prior to ruby COM initialization

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


 
 
 
 
 
 
  Re: COM initialization prior to ruby COM initialization  
 
 
 
 
 
 
 
 
 
 
Before fix: 
 
 
 
 
 
 
 
 
 
 
 
Administrator@qbtu7afcpcjsiom ~ 
 
 
 
 
$ cat foo.rb 
 
 
 
 
require 'win32ole' 
 
 
 
 
Facter.add('foo') do 
 
 
 
 
  setcode do 
 
 
 
 
'bar' 
 
 
 
 
  end 
 
 
 
 
end 
 
 
 
 
 
 
 
 
 
Administrator@qbtu7afcpcjsiom ~ 
 
 
 
  

Jira (PUP-4489) Add data_provider to module metadata

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


 
 
 
 
 
 
 Puppet /  PUP-4489 
 
 
 
  Add data_provider to module metadata  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2573) Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not

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


 
 
 
 
 
 
 Puppet /  PUP-2573 
 
 
 
  Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2573) Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not

2015-07-08 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-2573 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not  
 
 
 
 
 
 
 
 
 
 
This is mostly an internal change and is adequately covered by the unit test. Manually validated whether running two agents simultaneously causes one to error out. Validated on puppet-agent SHA:9b28aee3e99572f4d98973d683592dc11239f8d6 On redhat-7-x86_64, output from two simultaneous runs: 
 
 
 
 
 
 
[root@h8vih00e5qmj3h3 ~]# puppet agent --test --server h8vih00e5qmj3h3.delivery.puppetlabs.net 
 
 
 
 
Info: Retrieving pluginfacts 
 
 
 
 
Info: Retrieving plugin 
 
 
 
 
Info: Caching catalog for h8vih00e5qmj3h3.delivery.puppetlabs.net 
 
 
 
 
Info: Applying configuration version '1436387833' 
 
 
 
 
Notice: Applied catalog in 0.01 seconds 
 
 
 
 
 
 
 
 
 
[root@h8vih00e5qmj3h3 ~]# puppet agent --test --server h8vih00e5qmj3h3.delivery.puppetlabs.net 
 
 
 
 
Notice: Run of Puppet configuration client already in progress; skipping  (/opt/puppetlabs/puppet/cache/state/agent_catalog_run.lock exists)
 
 
   

  1   2   3   >