Using TALM to upgrade from 4.10.45 -> 4.10.47, upgrade completes while the SR-IOV operator fails to start due to image error

Description of problem: When using TALM to upgrade SNO from 4.10.45 to 4.10.47 with the latest RHOCP 4.10 operators, the upgrade complete with TALM policies compliant, even though the SR-IOV operator failed to upgrade.

Version-Release number of selected component (if applicable): upgrade from 4.10.45 to 4.10.47

How reproducible: Limited, different results per the customer in their last similar attempt.

Steps to Reproduce:
1.
2.
3.

Actual results:

$ oc get csv -A | awk '!seen[$2]++'
NAMESPACE NAME DISPLAY VERSION REPLACES PHASE
assisted-installer performance-addon-operator.v4.10.12 Performance Addon Operator 4.10.12 performance-addon-operator.v4.10.11 Succeeded
openshift-local-storage local-storage-operator.4.10.0-202302280915 Local Storage 4.10.0-202302280915 local-storage-operator.4.10.0-202212061900 Succeeded
openshift-logging cluster-logging.v5.6.3 Red Hat OpenShift Logging 5.6.3 cluster-logging.v5.6.2 Succeeded
openshift-operator-lifecycle-manager packageserver Package Server 0.19.0 Succeeded
openshift-ptp ptp-operator.4.10.0-202303010615 PTP Operator 4.10.0-202303010615 ptp-operator.4.10.0-202212072254 Succeeded
openshift-sriov-network-operator sriov-network-operator.4.10.0-202212061900 SR-IOV Network Operator 4.10.0-202212061900 Replacing
openshift-sriov-network-operator sriov-network-operator.4.10.0-202302280915 SR-IOV Network Operator 4.10.0-202302280915 sriov-network-operator.4.10.0-202212061900 Failed

Expected results: expecting the upgrade to complete successfully for RHOCP and the updated operators.

Additional info: Information extracted from internal ticket