We see many failures in CMO e2e tests which could be avoided by retrying actions (e.g. network blips happen). They create fatigue and urgent fixes may get merged with unnecessary delay.

A few recent occurrences:
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-monitoring-operator/1054/pull-ci-openshift-cluster-monitoring-operator-master-e2e-agnostic-operator/1363801343407427584
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-monitoring-operator/1062/pull-ci-openshift-cluster-monitoring-operator-release-4.7-e2e-agnostic-operator/1362051761308700672