Comment 1 for bug 1219097

So the problem here is that admin metadata is automatically created for every volume with admin context, which includes the migration destination volume. Regular metadata shouldn't exist for the new volume, but will check for that too.