Issue #14844 has been reported by Chris Price.
----------------------------------------
Bug #14844: upstart provider can't list services via 'puppet resource'
application
https://projects.puppetlabs.com/issues/14844
Author: Chris Price
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords:
Branch:
This ticket is going to look a lot like #14843, but it is a different issue.
I just installed puppet 3.0-rc via the apt/yum repos on a clean centos6 VM and
a clean ubuntu 10.04 VM. Running this command:
puppet resource service
on the CentOS machine yields output that looks like this:
...
service { 'sshd':
ensure => 'running',
enable => 'true',
}
service { 'udev-post':
ensure => 'stopped',
enable => 'true',
}
...
However, running the same command on the Ubuntu machine yields:
Error: Could not run: no block given
Running again with --trace gives:
Error: Could not run: no block given
/usr/lib/ruby/1.8/puppet/util/execution.rb:35
/usr/lib/ruby/1.8/open-uri.rb:32
/usr/lib/ruby/1.8/open-uri.rb:32
/usr/lib/ruby/1.8/puppet/util/execution.rb:34
/usr/lib/ruby/1.8/puppet/provider.rb:54
/usr/lib/ruby/1.8/puppet/provider/service/upstart.rb:30
/usr/lib/ruby/1.8/puppet/type.rb:892
/usr/lib/ruby/1.8/puppet/type.rb:885
/usr/lib/ruby/1.8/puppet/type.rb:885
/usr/lib/ruby/1.8/puppet/indirector/resource/ral.rb:14
/usr/lib/ruby/1.8/puppet/indirector/indirection.rb:255
/usr/lib/ruby/1.8/puppet/application/resource.rb:230
/usr/lib/ruby/1.8/puppet/application/resource.rb:142
/usr/lib/ruby/1.8/puppet/application.rb:350
/usr/lib/ruby/1.8/puppet/application.rb:342
/usr/lib/ruby/1.8/puppet/application.rb:436
/usr/lib/ruby/1.8/puppet/application.rb:342
/usr/lib/ruby/1.8/puppet/util.rb:529
/usr/lib/ruby/1.8/puppet/application.rb:342
/usr/lib/ruby/1.8/puppet/util/command_line.rb:74
/usr/bin/puppet:10
I suspect the problem is in the upstart provider, since that’s the major
difference between the code path for this command on Cent vs. Ubuntu. I haven’t
tried this command with previous versions of puppet on debian-based machines; I
assume it should work, but if for some reason it’s not supported, we at least
need to do a better job with the error messaging.
(The VMs used to repro this are the same ones we use for PE acceptance testing.)
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" 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-bugs?hl=en.
