Issue #1537 has been reported by ohookins.
----------------------------------------
Refactor #1537: "ensure" and "enable" running order for a service is
inappropriate
http://reductivelabs.com/redmine/issues/show/1537
Author: ohookins
Status: Unreviewed
Priority: Normal
Assigned to:
Category: service
Target version:
Granted, I only have a single use case for this but it is valid. Say we have
several service levels of machine, and on the lowest level we don't want to run
puppet aside from during the build where we set up some defaults.
So we have something like this defined in the manifests:
class puppet::disable {
# Disable puppet
service { "puppet":
ensure => stopped,
enable => false,
}
}
Hovever, the "ensure" part is run first, which stops puppet in the middle of
the run. Since the "enable" part would usually be run afterwards, it is never
run. Therefore quite possibly puppet will stay chkconfig'ed on.
To fix this we just need the running order reversed. I can't think of any
reason why this would break things.
----------------------------------------
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://reductivelabs.com/redmine/my/account
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
