Jira (PUP-4809) Mismatch in Error Message and Actual Behavior

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

 
 
 
 
 
 
 
 Puppet /  PUP-4809 
 
 
 
  Mismatch in Error Message and Actual Behavior  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Affects Version/s:
 
 PUP 4.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-4809) Mismatch in Error Message and Actual Behavior

2015-07-07 Thread Josh Cooper (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-4809 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Mismatch in Error Message and Actual Behavior  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg does the parser allow parameter values to be uppercase, e.g. True? It seems the value is being interpreted to mean something special, note the "Invalid value True[]{:name=>""}". The backtrace is: 
 
 
 
 
 
 
Error: Parameter enabled failed on Yumrepo[mariadb]: Invalid value True[]{:name=>""}. Valid values are absent. Valid values match /^(True|False|0|1|No|Yes)$/i. at /root/manifest.pp:1 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parameter/value_collection.rb:190:in `validate' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parameter.rb:439:in `unsafe_validate' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:511:in `unsafe_validate' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/parameter.rb:452:in `validate' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:483:in `block in should=' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:483:in `each' 
 
 
 
 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:483:in `should='

Jira (PUP-4809) Mismatch in Error Message and Actual Behavior

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

 
 
 
 
 
 
 
 Puppet /  PUP-4809 
 
 
 
  Mismatch in Error Message and Actual Behavior  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-4809) Mismatch in Error Message and Actual Behavior

2015-07-01 Thread Richard Raseley (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Richard Raseley created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4809 
 
 
 
  Mismatch in Error Message and Actual Behavior  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/01 3:32 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Richard Raseley 
 
 
 
 
 
 
 
 
 
 
 

CentOS 7 x86_64
 

Puppet 4.2.0 (Installed via puppetlabs-release-pc1-el-7 repository)
 
 
Apply the following configuration: 
 
 
 
 
 
 
yumrepo { 'mariadb' : 
 
 
 
 
  ensure   => present, 
 
 
 
 
  enabled  => True,