Dear All,
I have started to test 2.6.2rc1 in my organization. We would like to
move to 2.6 soon, which is not possible at the moment due to regressions
found in 2.6.0 and 2.6.1.
I have found 2 major issues in 2.6.2rc1 that blocks us again to move to
2.6. The first one is about the exec type:
# cat test-exec.pp
exec { "echo_test":
path => "/bin",
command => "echo test",
}
# puppet apply test-exec.pp
/usr/lib/ruby/site_ruby/1.8/puppet/util/metric.rb:62: warning:
parenthesize argument(s) for future version
/usr/lib/ruby/site_ruby/1.8/puppet/util/posix.rb:117: command not found:
which echo
err: /Stage[main]//Exec[echo_test]/returns: change from notrun to 0
failed: Could not find command 'echo'
Most of our current exec definitions are currently broken, since they do
not include the path to the which command. This issue is already a
reported in ticket #4299:
http://projects.puppetlabs.com/issues/4299
The second issue is about the package type. On our CentOS 5 host, puppet
does not complain when it does not found a package it has to install:
# cat test-pkg.pp
package { “fake_package”: ensure => installed, }
# puppet apply test-pkg.pp
/usr/lib/ruby/site_ruby/1.8/puppet/util/metric.rb:62: warning:
parenthesize argument(s) for future version
notice: /Stage[main]//Package[fake_package]/ensure: ensure changed
‘purged’ to ‘present’
# rpm -qa fake_package
# yum search fake_package
...
No Matches found
I have created ticket #4929 for this issue:
http://projects.puppetlabs.com/issues/4929
I would be glad if these two issues could be fixed in 2.6.2. Without a
fix for them, we will again stay stuck to 0.25.
Best regards,
Xavier
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
