Bug 1717633 - clusteroperator/machine-api does not define any related resources
Summary: clusteroperator/machine-api does not define any related resources
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Alberto
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-05 20:36 UTC by Luis Sanchez
Modified: 2019-10-16 06:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:31:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:31:47 UTC

Description Luis Sanchez 2019-06-05 20:36:47 UTC 
Description of problem:

The machine-api ClusterOperator resource does not specify any related resources. This hinders problem-determination as tools cannot automatically collect the information needed to debug issues.

The cloud-credential 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 Alberto 2019-06-17 15:18:27 UTC 
https://github.com/openshift/machine-api-operator/pull/330
Comment 4 sunzhaohua 2019-06-25 06:09:40 UTC 
Verified

$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.2.0-0.nightly-2019-06-24-160709   True        False         6s      Cluster version is 4.2.0-0.nightly-2019-06-24-160709

$ oc get clusteroperator machine-api -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
  creationTimestamp: "2019-06-25T02:17:00Z"
  generation: 1
  name: machine-api
  resourceVersion: "125077"
  selfLink: /apis/config.openshift.io/v1/clusteroperators/machine-api
  uid: 50deb4ff-96ef-11e9-983f-0661cb113b00
spec: {}
status:
  conditions:
  - lastTransitionTime: "2019-06-25T02:17:26Z"
    status: "False"
    type: Progressing
  - lastTransitionTime: "2019-06-25T02:17:01Z"
    message: 'Cluster Machine API Operator is available at operator: 4.2.0-0.nightly-2019-06-24-160709'
    status: "True"
    type: Available
  - lastTransitionTime: "2019-06-25T02:17:01Z"
    status: "False"
    type: Degraded
  extension: null
  relatedObjects:
  - group: ""
    name: openshift-machine-api
    resource: namespaces
  versions:
  - name: operator
    version: 4.2.0-0.nightly-2019-06-24-160709
Comment 6 errata-xmlrpc 2019-10-16 06:31:27 UTC 
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:2922
Note You need to log in before you can comment on or make changes to this bug.