Hi guys,

The Puppet that comes with Ubuntu Vivid (3.7.2) is broken -- it doesn't 
correctly resolve whether a service is an Upstart service, so e.g. any mysql 
service notification will fail when trying to restart a service (some other 
services fail too). This is because the 'service' Puppet type is trying to 
invoke /sbin/{start,stop,status,restart,reload} scripts, which fail. So 
basically Puppet issues 'reload mysql', when it should be issuing 'service 
mysql reload'

There's an easy work-around -- I have written a simple script that emulates 
old-style service init behavior, and symlinked it into /sbin/ as 
appropriate; however, this dirty hack may cause problems down the road, so 
I really would rather avoid it.

I am hoping that an official Puppetlabs release for Vivid might fix the 
problem. Do you guys know when/if it's coming? I keep checking in 
https://apt.puppetlabs.com/, but there's nothing there still...

Alternatively, does anyone know how to make the stock distro Puppet package 
resolve the service type correctly?


BTW, in case anyone cares, here's my work-around script -- I put it at 
/usr/local/bin/initWrapper:

#!/bin/bash

commandName=$(basename $0)
serviceName=$1

service "$serviceName" "$commandName"

Then you just replace the symlinks at 
/sbin/{start,stop,status,restart,reload} with symlinks to this new 
script... Now the puppet manifests finish running fine.

However, this work-around strikes me as dangerous, so I don't recommend 
anyone use it.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/afb567dd-37f1-436e-bb38-4aa678b55e69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to