On 02/09/2012 11:39 AM, Daniel Pittman wrote:
>>> 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.
>
If so it's not well covered in the Type docs. I tested this class under
2.6.x previously and did not experience this issue so it may be a 2.7.x
change. A lot has changed about our environment since then so I can't
definitively point at anything but if it's a change in the Puppet
default value for 'ensure' then the docs should be updated to reflect
that. Currently the type docs for 2.7.9 have the following to say about
setting 'ensure' on a service:
ensure
Whether a service should be running. Valid values are stopped (also
called false), running (also called true).
--
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.
