Steve Langasek <steve.langa...@canonical.com> writes:
> This is a bug in puppet, then; there's no reason that puppet should be
> trying to call 'status startpar-bridge', and the fact that it's doing
> so is a bug in the puppet code in question.
When you run "puppet resource service", puppet will enumerate _all_
services on that server (init scripts, upstart jobs, systemd services,
whatnot, and then check if it is running, and if it is enabled on boot.
When the operatingsystem is "ubuntu", the service provider is "upstart",
The relevant code for handling services on ubuntu is:
defaultfor :operatingsystem => :ubuntu
commands :start => "/sbin/start",
:stop => "/sbin/stop",
:restart => "/sbin/restart",
:status_exec => "/sbin/status",
:initctl => "/sbin/initctl"
Is this wrong for Ubuntu?
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276766
Title:
'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
