We have noticed that Azure install rate is now 85% and dropping:

https://sippy.dptools.openshift.org/sippy-ng/tests/4.11?filters=%257B%2522items%2522%253A%255B%257B%2522columnField%2522%253A%2522name%2522%252C%2522operatorValue%2522%253A%2522equals%2522%252C%2522value%2522%253A%2522cluster%2520install.install%2520should%2520succeed%253A%2520overall%2522%257D%252C%257B%2522columnField%2522%253A%2522variants%2522%252C%2522operatorValue%2522%253A%2522contains%2522%252C%2522value%2522%253A%2522azure%2522%257D%255D%252C%2522linkOperator%2522%253A%2522and%2522%257D

We've identified two problems in https://issues.redhat.com/browse/TRT-367, this bug represents one of them.

https://search.ci.openshift.org/?search=level%3Derror+msg%3DAttempted+to+gather+ClusterOperator+status+after+installation+failure%3A+listing+ClusterOperator+objects.*i%2Fo+timeout&maxAge=168h&context=1&type=bug%2Bissue%2Bjunit&name=azure&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

Currently showing 4.61% of all azure 4.11 jobs.

We see hits in past releases and as such I don't think this is a product regression, however it may be blocking us from green-lighting 4.11 as the install % for all core platforms is historically 95%+ at time of release.

Unclear when this problem started.

Here's a specific sample prow job to rally around:

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.10-e2e-azure-ovn/1542324425607614464