----- "Silviu Paragina" <[email protected]> wrote:
> >
> I've been left with the impression that if augeas fails for provider
> reasons it fails the whole run.
>
> My test case would imply the same thing.
>
> sil...@puppet-test:/etc/puppet/repo/development/modules/puppet$ cat
> test.pp
> augeas
> { "puppet settings":
> context => "/files/etc/puppet/puppet.conf",
> changes => [ "set main/report true",
> "set main/server puppet.paragina.ro",],
> }
>
>
> exec
> { "/test.sh":
> }
> sil...@puppet-test:/etc/puppet/repo/development/modules/puppet$ cat
> /test.sh
> #!/bin/sh
>
> date >> /touchme
> exit 1
> sil...@puppet-test:/etc/puppet/repo/development/modules/puppet$ sudo
> puppet test.pp \
> >
> warning: Could not retrieve fact fqdn
> Could not find a default provider for augeas
> sil...@puppet-test:/etc/puppet/repo/development/modules/puppet$ ls
> /touchme
> ls: cannot access /touchme: No such file or directory
>
> There is no dependency between them yet the exec resource wasn't
> applied. If I remember right, the issue with this was that the run
> failed without installing augeas and the machine would be left in a
> ever
> failing state.
>
At puppetcamp Luke said the cron issue is a bug and if someone files it,
they'll fix it.
You should be able to install package{"cron":} in a run and later in the same
run make crontabs if those resources require => Package["cron"]
--
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.
