Bug 1717732 - clusteroperator/support does not define any related resources
Summary: clusteroperator/support does not define any related resources
Keywords:
Status: CLOSED DUPLICATE of bug 1717509
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.1.z
Assignee: Aravindh Puthiyaparambil
QA Contact: Fan Jia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-06 03:23 UTC by Luis Sanchez
Modified: 2019-07-17 23:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-17 23:56:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Luis Sanchez 2019-06-06 03:23:29 UTC
Description of problem:

The support 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)

Comment 1 Aravindh Puthiyaparambil 2019-07-17 23:56:32 UTC
This is already tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1717509. There is a PR (https://github.com/operator-framework/operator-marketplace/pull/211) open to fix this in 4.1.z and is waiting on approval. I will close this as duplicate.

*** This bug has been marked as a duplicate of bug 1717509 ***


Note You need to log in before you can comment on or make changes to this bug.