Description from customer - Marcus from Telia:
The reason appears to be that the resource modules ResourceCleanupTask with the below line (ResourceCleanUpTask.java:377 in the trace)
Node tempNode = (BINARY_RESOURCES_TEMPLATE.equals(template)) ? resourceNode.getNode(JcrResourceOrigin.BINARY_NODE_NAME) : resourceNode;
This line, which translates to
Node tempNode = ("resources:binary".equals(template)) ? resourceNode.getNode("binary") : resourceNode;
this assume that all nodes with the resources:binary template contain a "binary" subnode. This assumption is incorrect in our content, not just for the attached node example, which is the one that fails the upgrade task, but for all nodes in this tree with the resources:binary template. (see attached export from failing node in 5.4.6)