Incorrect error handling for content distribution if binary is not present in blob store

We did a content distribution and the publisher used a different blob store. So the reference to the binary could not be resolved.

We get a stack trace like below but the ui just shows the queue as running with 0 retries. So it seems the error is not handled correctly.

https://gist.github.com/cschneider/c663fa7912b4e643c9d761aa8b70906f