export concat::fragments does not work

[Vincent Miszczak]

Hello,

I need to export concat::fragment on some nodes and gather the results on some other.

To create the export I do something like :

@@concat::fragment{"/myfile-$fqdn":

   target=>"/myfile"

}

but on the export node I get : 

Invalid relationship [...] because Exec[concat_/myfile] doesn't seem to be in the catalog.

I don't want/need to declare a concat for "/myfile", because I would need the required filesystem layout for the final file. I just want to export fragments.

Am I missing something ?

[Klavs Klavsen]

You must define the concat for /myfile as well on all servers.

I've switched to file_concat for these things, and it helped me - and you might not need to define it with that module.. give it a whirl.

concat module has several deficiencies which all seemed to be very well resolved by the file_concat module (and you might be able to make that work without - which also has the advantage, that it does not copy files and some scripts to /tmp for it to work - and hence a --noop run can actually give you a diff, instead of failing as it does with concat module.

[jcbollinger]

Yes.  You are missing that it is not sensible to collect Concat::Fragments that have no associated Concat resource.  Such orphan Concat::Fragments are meaningless, and the module does not support them.

If you want to manage the fragments as separate files without concatenating them, then use File resources.  If you're trying to do something else then we could help you better if we knew what that was.


John