Bug 1717633
| Summary: | clusteroperator/machine-api does not define any related resources | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Luis Sanchez <sanchezl> |
| Component: | Cloud Compute | Assignee: | Alberto <agarcial> |
| Status: | CLOSED ERRATA | QA Contact: | Jianwei Hou <jhou> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | agarcial, sponnaga, zhsun |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:31:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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
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 |
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)