The business had a wish to copy content from production to acceptation (publishing environment). So I created a content deployment job to do so, and ran it.
It failed with the following error:
Content deployment job 'PROD -> ACC' failed.The exception thrown was 'Microsoft.SharePoint.SPException' : 'Feature '32e8942e-f6d6-48ec-ab6a-a75bedd2816d' for list template '10000' is not installed in this farm. The operation could not be completed.'
The feature ID points to a custom feature which is in fact installed in both environments, exactly the same WSP. One thing to note is that on the server which hosts central administration, there are no webapplications deployed. Because of that, the web scoped features are also omitted on that server and thus not present. Because of that, I enabled the Central Administration service on one of the front-ends and edited the content deployment settings to use that server instead of the central admin one. Didn't fix it.
When I test the job, it tests OK, so it's really the import causing problems.
So now the question is; should this work at all? Or do I need to get the web applications on the central admin server so the features are present there as well? Sounds a bit odd.