it was because the case
$mysql_enabled = 1
class mysql::server {
service{mysqld: blablabla activate}
}
class stripdown{
if $mysql_enabled == 1 {
service{mysqld: blablabla deactivate}
}
}
node somenode {
include mysql::server
include stripdown
}
So you see in the case above, the parser will fail because service
[mysql] is included and defined twice (of course, since it is grammar
parser and not an AI ;-). But it would have worked if executed
( But i know the whole thing with variables is maybe a wrong
implementation of the problem )
On Dec 17, 10:34 pm, jcbollinger <john.bollin...@stjude.org> wrote:
> On Dec 16, 9:17 pm, Alexandre <alexandre.fou...@gmail.com> wrote:
> [...]
>
> > because otherwise Puppet would complain at -parsing- time, not execute
> > time, since it does not want to have the same ressource(here service)
> > declared twice, even if one is not included for the node,
>
> Puppet does not exhibit this problem for me. The only way I have been
> able to elicit a resource conflict error from Puppet is to have one
> node include two classes each declaring a resource of the same type
> and name. It is not enough to cause such an error (in my tests)
> simply for two classes to define the same resource -- both must be
> included in the same node to get the error. If you find differently
> then I encourage you to file a bug report.
>
> John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
