On Thursday, March 6, 2014 12:42:25 PM UTC-6, Garrett Honeycutt wrote: > > > You could change 'include ca' to 'require ca' and then safely remove the > require attribute from the service resource. This would ensure that all of > the resources from the ca class are handled before your service class. > > Yes, but no. The problem is not a resource ordering issue, it is a resource declaration issue. It cannot be resolved by adding resource relationships (unless incidentally), because Puppet disagrees with the OP that the resource in question has been declared at all. If it were in fact declared in class 'ca' then the error would not occur.
It is possible that there is a difference in the spelling of the file name between class 'ca' and class 'lumberjack::service'. In that case, switching from a relationship with the File to one with the Class would make the error go away (c.f. "incidentally"), but it would not ensure that a file of the name previously specified in class 'lumberjack::service' was managed. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6519f602-070b-4344-af7d-24102e1ab664%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
