On Thu, Feb 9, 2012 at 11:30, Aaron Grewell <aaron.grew...@gmail.com> wrote: > On 02/09/2012 06:16 AM, jcbollinger wrote: >> On Feb 8, 5:34 pm, Aaron Grewell <aaron.grew...@gmail.com> wrote: >>> I've got a bit of a head-scratcher here, though I'm sure it must be >>> something small. I'm trying to enable a service for next boot without >>> starting it. That usually "just works" but for some reason this time >>> around it isn't. The node keeps trying to start the service which >>> will always fail because it requires a reboot in order to enable the >>> necessary kernel parameters. How do I make Puppet stop trying to >>> start the service? >> >> I would try adding "ensure => undef" to the service's parameters. If >> that doesn't work then I can't imagine what would. > > Thanks John, that did the trick. I'm not sure if I've got a service > default set somewhere I didn't realize or what but at least now it's > doing the right thing.
Thanks, John, indeed. I hoped to find a bit more time to dig in and understand exactly why, but my intuition is that we have a default of `ensure => true` for anything that doesn't explicitly mention the value. For a service that is the equivalent of `ensure => running`, which would explain the behaviour you saw. For most types that is the right thing to do, if the user is trying to manage something about it. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
