[Bug 1457957] [NEW] puppet uses upstart for service status checks in vivid

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Robie Basak (racb):

After upgrading one of my servers to 15.04/vivid (from original
14.10/utopic install), I had a failing puppet job. The error message is:

Error: /Stage[main]/Main/Service[ssh]: Could not evaluate: Execution of
'/sbin/status ssh' returned 1: status: Unable to connect to Upstart:
Failed to connect to socket /com/ubuntu/upstart: Connection refused

After some research it seems that this happens with all daemons that
have an upstart config file hanging around in '/etc/init/'. Puppet
checks for existence of that file, and then assumes that it should issue
the '/sbin/status <service>' command in order to check the service
status. For all services that don't have an upstart conf installed,
puppet uses '/etc/init.d/<service> status', which works perfectly (for
ssh and munin-node, the two services I used while verifying the
behavior).

As I assume that we cannot expect to have all services drop the upstart
config in their vivid packages (I'm not sure about the status of upstart
support in vivid), the best fix should be to have puppet check for
'/etc/init.d/<service>' before trying '/etc/init/<service>/.conf', at
least on vivid.

puppet-common version: 3.7.2-1ubuntu2

Note: even setting service 'hasstatus => no' and 'status =>
/etc/init.d/ssh status' in the puppet Service definition does not force
puppet to not issue the command (which probably should be a separate
bug).

** Affects: puppet (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: needs-upstream-report systemd-boot vivid
-- 
puppet uses upstart for service status checks in vivid
https://bugs.launchpad.net/bugs/1457957
You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report.