On Monday, February 17, 2014 4:13:38 AM UTC-6, Andreas Dvorak wrote: > > Hi John, > > thank you for your reply. You have found an other issue. > But my main problem is that the second call of "replace" is ignored. > >
As I said at the end, I don't think the second 'replace' resource is being ignored at all. At any rate, you have presented no evidence of it, and I have no reason to believe that the manifest you presented would be subject to such an issue. I already described one way that you could test whether the resource is in fact ignored. On the other hand, the real problem I described will result in Puppet deciding under some circumstances that the Exec resource inside one of your baader::replace resources is already in sync. Depending on the logging level with which you are running the agent, that might result in nothing related to the resource being emitted to the log / standard out, which in turn could lead you to think that the resource was being ignored. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/8c10ec17-c747-411f-8582-885f7c26363e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
