Jira (PDB-714) Exported resource relationship woes

[Zach Leslie (JIRA)]

Title: Message Title

Zach Leslie commented on an issue   Re: Exported resource relationship woes This appears to be related to a module conflict. I triple checked the modules in each of the modulepaths and removed any conflicting modules which then allowed the catalog to get submitted to PuppetDB. I don't know why the catalog was compiling in the first place and failing on submission to PuppetDB, but in any case, the catalog is now retrievable by the node in question. Apologies for the false alarm. Thanks for taking the time to look at this with me Kenneth Barber. Add Comment   PuppetDB / PDB-714 Exported resource relationship woes Consider the following. {code} @@concat::fragment { "bacula-client-${::fqdn}":   target => '/etc/bacula/conf.d/client.conf',   content => template('bacula/client.conf.erb'),   tag => "bacula-${bacula::params::bacula_director}", } {code} The above resource exports a fragment from a node to be backed up. For those familiar with the fragmen... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.