Issue #21478 has been updated by Justin Stoller.
If I understand this correctly it is because Puppet doesn't know about Upstart instances natively, there is currently a [hack to allow it to understand instances of two well known network services](https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb#L42-L47) I think the simplest solution (if plymouth-ready is only used at boot and can be fully ignored) is to add it to the excludes list. Quick and dirtier, if Puppet needs to know about the instances of plymouth-ready is to add it to the list of special cases I referenced earlier. The best long term solution (though it might take a bit of work) would to let Puppet figure out what services can have instances and what the ENV variable is to control them (I don't know a way of doing that without inspecting the .conf file). ---------------------------------------- Bug #21478: Puppet fails on plymouth-ready https://projects.puppetlabs.com/issues/21478#change-93717 * Author: Richard Stevenson * Status: Unreviewed * Priority: Normal * Assignee: * Category: * Target version: * Affected Puppet version: 3.2.2 * Keywords: * Branch: ---------------------------------------- The command "puppet resource service" fails with the error "Error: Could not run: Execution of '/sbin/status plymouth-ready' returned 1: status: Unknown parameter: UPSTART_EVENTS". This occurs when puppet 3.2.2-1puppetlabs1 is run on Ubuntu 12.04.2, with the updated plymouth package, version 0.2.2-2ubuntu31.1 installed, but not with older versions of the plymouth package. This appears to be due to the newly added /etc/init/plymouth-ready.conf file, introduced in response to this ubuntu bug (https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/982889). When its status is requested with "status plymouth-ready", it fails with a familiar "status: Unknown parameter: UPSTART_EVENTS". I reported this on the ubuntu launchpad here (https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1194971), but was informed that this is desired behaviour for jobs that have an instance, and that the bug is with puppet. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
