this is only the library-go cherry-pick, it is still missing the revendoring on the operators https://github.com/openshift/cluster-kube-scheduler-operator/pull/370 https://github.com/openshift/cluster-kube-apiserver-operator/pull/1232 https://github.com/openshift/cluster-etcd-operator/pull/663 https://github.com/openshift/cluster-kube-controller-manager-operator/pull/564
*** Bug 2003538 has been marked as a duplicate of this bug. ***
@Antonio Ojea: As discussed bug only fixed in 4.10 not in 4.9. So I am moving bug back to ASSIGN. For 4.10: https://search.ci.openshift.org/?search=no+image+found+for+operand+pod&maxAge=48h&context=1&type=junit&name=4%5C.10&excludeName=upgrade&maxMatches=5&maxBytes=20971520&groupBy=job Results: No results found. For 4.9: https://search.ci.openshift.org/?search=no+image+found+for+operand+pod&maxAge=48h&context=1&type=junit&name=&excludeName=upgrade&maxMatches=5&maxBytes=20971520&groupBy=job Results: #1439826985923645440 junit 24 minutes ago event happened 46 times, something is wrong: ns/openshift-kube-apiserver-operator deployment/kube-apiserver-operator - reason/MissingVersion no image found for operand pod #1439464583604473856 junit 24 hours ago event happened 39 times, something is wrong: ns/openshift-kube-apiserver-operator deployment/kube-apiserver-operator - reason/MissingVersion no image found for operand pod
Will verify later
Reading code https://github.com/openshift/library-go/pull/1203, understood why it was so fixed; It applied to all static pod operators (kas, kcm, ks, etcd), not only kas; the original noisy event creation (https://github.com/openshift/library-go/pull/1049) didn't exclude the false podsFound situation. In CI, searched 'no image found for operand pod' restricted in 4.9 jobs of recent days, no occurrence is seen for any among kas/kcm/ks/etcd.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.4 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:3935
https://github.com/openshift/cluster-etcd-operator/pull/663 landed after 4.9.0 and shipped in 4.9.4, as described in comment 14. Updating the Target Release to 4.9.z to match.