Lorello,
I believe this issue is being tracked at
https://projects.puppetlabs.com/issues/14297 and there is a pull request in
that should resolve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hi Lorello,
In the puppet source code at github you can see how the status is
checked via upstart:
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb
The is a search for 'start' on the status output. So if ssh is running
and status ssh gives the following out
Hi, I've the same problem on Lucid Ec2 hosts: ssh service does not
restart correctly using hasstatus => true, even expliciting upstart as
provider
I'm using Puppet version 2.7.14 from skettler's PPA
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
It says fixed but I don't think it's fixed. I'm using Ubuntu 11.10 with
Puppet 2.7.10 and still having this problem.
I also filed Puppet bug #12773: Service Status detection does not always
work properly on Ubuntu in https://projects.puppetlabs.com/issues/12773
See also forum thread: puppet servi
This bug was fixed in the package puppet - 0.25.4-2ubuntu6
---
puppet (0.25.4-2ubuntu6) lucid; urgency=low
* Fix init service provider to correctly check the status of services
using upstart jobs (LP: #551544).
* Package spec/ tests so that both test/ and spec/ tests can be ru
** Changed in: puppet (Ubuntu Lucid)
Status: Triaged => In Progress
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Branch linked: lp:~mathiaz/ubuntu/lucid/upstart/workaround-status-
exit-code
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
As mentioned on IRC:
ttx: bug #551544> possibly simpler to just get this fixed in
upstart for release; can you make sure mathiaz talks with Keybuk
about this?
(bug #552786 is the corresponding upstart bug)
slangasek: yes
--
puppet in lucid does not support upstart status
https://bugs.launch
i18n aside, that seems like an elegant workaround given the deadlines
involved.
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Presumably even if there is i18n, you could force LANG=C or similar?
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here is a proposal:
Add a statuscmd function in the puppet debian service provider. If the
initscript script is a symlink to /lib/init/upstart-job, use the
following command as the statuscmd instead of the default [initscript,
:status] defined in the init provider:
sh -c "invoke-rc.d SERVICE sta
** Changed in: puppet (Ubuntu Lucid)
Assignee: (unassigned) => Mathias Gug (mathiaz)
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
** Changed in: puppet (Ubuntu Lucid)
Milestone: None => ubuntu-10.04
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
See also https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/552786
for something vaguely related
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
To clarify, assuming the status situation with upstarted init.d scripts
is resolved, I don't see any major reason why the existing provider
wouldn't continue to at least function well enough for users?
The update-rc situation isn't ideal, which is why I suggested an initctl
based provider, which r
I'll try and find the bug in a second, but apparently the lack of any
return codes from /etc/init.d/foo status when a service has been
upstarted is a bug.
Ultimately I feel puppet needs an initctl based service provider.
--
puppet in lucid does not support upstart status
https://bugs.launchpad.
** Changed in: puppet (Ubuntu Lucid)
Importance: Medium => High
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
** Changed in: puppet (Ubuntu)
Importance: Undecided => Medium
** Changed in: puppet (Ubuntu)
Status: New => Confirmed
** Also affects: puppet (Ubuntu Lucid)
Importance: Medium
Status: Confirmed
--
puppet in lucid does not support upstart status
https://bugs.launchpad.net/b
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42477382/Dependencies.txt
** Description changed:
Binary package hint: puppet
- Puppet does not currently have an "upstart" provider for the server
+ Puppet does not currently have an "upstart" provider for the service
19 matches
Mail list logo