On Feb 14, 2:59 am, hai wu <[email protected]> wrote:
> This is a simple test code, named as 'a.pp':
>
> service { 'cups':
>   enable => false,
>
> }
>
> During RHEL kickstart process, I tried to run the above after doing "chroot
> /mnt/sysimage"
>
> If 'chkconfig --list cups' shows cups is on, no mater how many time you ran
> "puppet apply a.pp", it always seems to see nothing for cups service,
> nothing happened.
>
> If 'chkconfig --list cups' shows cups is not on, no matter how many times
> ran "puppet apply a.pp", it keeps trying to enable it all the time with the
> following picture:
>
> notice: /Stage[main]//Service[cups]/enable: enable changed 'false' to 'true'
>
> Any way to fix the above?


I doubt Puppet is behaving as you describe with the manifest you
presented.  Puppet is behaving exactly as it would if you had
specified "enable => true".  In your real manifest, do you perhaps
have single or double quotes around "false"?  If so, remove them.
Also, since a chroot is involved, verify that you're actually feeding
Puppet the manifest file you think you're feeding it.


John

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" 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-users?hl=en.

Reply via email to