There are no single or double quotes. That is the exact file I manually run
inside chroot environment during kickstart phase. I am kickstarting RHEL6U2
server, and in kickstart ssh access is turned on, so I could ssh into
chroot environment, and do "chroot /mnt/sysimage". When I manaully run this
code:
service {'cups':
enable => true,
}
It would keep saying this all the time:
# puppet apply a.pp
notice: /Stage[main]//Service[cups]/enable: enable changed 'false' to 'true'
notice: Finished catalog run in 0.23 seconds
This is causing me headache, no matter how many times I tried to run puppet
during kickstart phase, it would not converge, it would always try to
enable those services which are already enabled.
But if I ran the same a.pp on another server that's already kickstarted
(not chroot), then things are working as expected. The above would only
show up once if cups service is not enabled.
The only thing I could see if during kickstart, the RHEL6U2 server is in
selinux permissive mode, while after kickstarting, it is in selinux disable
mode. But this should still work inside selinux permissive mode. I am using
Puppet 2.7.9.
On Tue, Feb 14, 2012 at 8:30 AM, jcbollinger <[email protected]>wrote:
>
>
> 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.
>
>
--
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.