Description of problem: The monitoring ClusterOperator resource does not specify any related resources. This hinders problem-determination as tools cannot automatically collect the information needed to debug issues. The operator should specify, at minimum, a namespace and a configuration resource to collect. Here is an example from kube-apisever: kind: ClusterOperator metadata: name: kube-apiserver status: relatedObjects: - group: operator.openshift.io name: cluster resource: kubeapiservers - group: '' name: openshift-config resource: namespaces - group: '' name: openshift-config-managed resource: namespaces - group: '' name: openshift-kube-apiserver-operator resource: namespaces - group: '' name: openshift-kube-apiserver resource: namespaces A new e2e test designed to catch this deficiency will white-list this component initially. This component should be removed from the white-list as part of resolving this issue. https://github.com/openshift/origin/blob/master/test/extended/operators/clusteroperators.go (link will be active once https://github.com/openshift/origin/pull/23044 merges)
Thanks Luis for bringing that up. I am not really sure what the implications are to prioritize this issue. Would you help me to understand that case a little better, please?
Actually, we clarified all necessary details offline and we already started working on it.
https://github.com/openshift/cluster-monitoring-operator/pull/375
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, 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-2019:1635