Description of problem: Found by Insights team when analyzing 4.3 -> 4.4 upgrades and noticing csi-snapshot-controller-operator stuck at "Waiting for Deployment to deploy csi-snapshot-controller pods". Telemetry does not gather condition messages, they collect only Reason. And in this case, the reason was AsExpected, which is hard to filter with - this Reason is used in too many other cases. Each failure condition should have its own Reason. We should audit AsExpected occurrence in all storage operators: - cluster-csi-snapshot-controller-operator - cluster-storage-operator - CSI driver operators For example: https://github.com/openshift/cluster-storage-operator/pull/63/files#diff-97e82b0d41902abcb7a788ea37573993R328 https://github.com/openshift/cluster-csi-snapshot-controller-operator/blob/108649ce8d46991803eef8fa43f25f112f41addb/pkg/operator/sync.go#L199
Submitted the following PRs to update the CSI drivers: - https://github.com/openshift/aws-ebs-csi-driver-operator/pull/95 - https://github.com/openshift/csi-driver-manila-operator/pull/66 - https://github.com/openshift/openstack-cinder-csi-driver-operator/pull/5
In 4.6.0-0.nightly-2020-09-29-215452, all the PRs are included, marked this bug as verified.
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.6 GA Images), 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-2020:4196