No, you're looking at it backwards. cryptsetup should not have to carry any embedded information about what identifies a RAID container, that's the responsibility of blkid. The bug is that the cryptsetup job is *being called at all* for this block device.
No, you're looking at it backwards. cryptsetup should not have to carry any embedded information about what identifies a RAID container, that's the responsibility of blkid. The bug is that the cryptsetup job is *being called at all* for this block device.