When we use `oc` to download ocp-mirror 4.14.16 from local registry to local directory, one blob's checksum is different from the checksum in filename.

cmd:
/opt/dci-quay/artifacts/4.14.16/oc adm release mirror -a /root/clusterconfigs-raven-cluster-1/OCP-4.14/pull-secret.json-combined --to-dir=/opt/dci-quay/artifacts/4.14.16/mirror --from=dci-mirror-registry.rackg06.local/ocp4/openshift4:4.14.16-x86_64

4.14.16

very hard to reproduce in fine network environment

1. download mirror
/opt/dci-quay/artifacts/4.14.16/oc adm release mirror -a /root/clusterconfigs-raven-cluster-1/OCP-4.14/pull-secret.json-combined --to-dir=/opt/dci-quay/artifacts/4.14.16/mirror --from=dci-mirror-registry.rackg06.local/ocp4/openshift4:4.14.16-x86_64

2. tar mirror
/usr/bin/tar czf /opt/dci-quay/artifacts/4.14.16/ocp-mirror-4.14.16.tar.gz -C /opt/dci-quay/artifacts/4.14.16/mirror .

3. copy the file to another directory
/bin/cp /opt/dci-quay/artifacts/4.14.16/raven-ws/ocp-mirror-4.14.16.tar.gz /opt/ftp_root/4.14.16/

4. untar the mirror and check the sha256sum of file "mirror/v2/openshift/release/sha256:17c0bef796bbb6b965f81e6ce798347ba149e49f889c9c2db8effdfa8ef97779"

checksum does not match:
filename - 17c0bef796bbb6b965f81e6ce798347ba149e49f889c9c2db8effdfa8ef97779
checksum - 5917e735f64a3b1d03b3e5f94a0ec7bdb5240d04d3ffa41b283b3363c08a4ddf

The match of the checksum and the filename should be guaranteed.

We are leveraging this in DCI pipeline. The step to reproduce is automatically driven by DCI.