On Tuesday, September 25, 2012 4:20:26 AM UTC-5, Luke Bigum wrote: > > Hi Nikita, > > On 25/09/12 10:05, Nikita Burtsev wrote: > > Hello, > > > > We have a weird problem with includes: > > err: Could not retrieve catalog from remote server: Error 400 on > > SERVER: Could not find resource 'Class[Common_software]' for > > relationship from 'Class[Default_repositories]' > > > > My wild guess would be that "common_software" gets in before > > "default_repositories" and thus the error message. If i run agent > > again it sometimes goes away and configuration gets applied, sometimes > > it does not. I even tried using stages, did not help. > > > > No, this is not an ordering problem, because ordering (generally) > doesn't come into it when talking classes and relationships. It doesn't > matter in which order your classes are declared.
No, that's incorrect. Resource references must not be parsed before the declarations of the underlying resources, else you get an error along the lines of the one the OP reported. That's rather easy to address for dependencies on non-parametrized classes: because multiple declaration of such classes is safe, you can always just 'include' the needed class earlier in the same scope. That it is not safe to do so with parametrized classes is one of my biggest complaints about them. (Puppet 3 will make this situation somewhat better, but does not resolve it completely.) > It might be more > helpful if I reword the error to: > > "The class Default_repositories has a dependency on the class > Common_software, but I can't find the class Common_software declared > anywhere" > Naturally, if the referenced resource is not declared anywhere then its declaration cannot be parsed before the reference, but that's a special case. > > You say below you use inheritance. If your site classes inherit from > common_software, then common_software is implicitly declared in your > manifests, so you shouldn't see this problem. That's correct: a subclass can always assume that its superclass will be parsed first. If the superclass has not already been declared and cannot be autoloaded then the resulting error should identify the inheritance declaration, not some reference to the parent class in the subclass's body. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/50_Fa-M9jNMJ. To post to this group, send email to puppet-users@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.
