Bug 1741064 - [4.1.z]cluster-autoscaler/machine-api clusteroperator degraded reporting missing reason/detail information clusteroperator degraded reporting missing reason/detail information
Summary: [4.1.z]cluster-autoscaler/machine-api clusteroperator degraded reporting miss...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.1.z
Assignee: Jan Chaloupka
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-14 07:58 UTC by Junqi Zhao
Modified: 2019-08-16 10:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1741062
Environment:
Last Closed: 2019-08-16 10:50:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Jan Chaloupka 2019-08-15 11:20:01 UTC 
I checked the code of both machine-api and cluster-autoscaler operators and we do report reason when operator's status is degraded:

machine-api-operator: https://github.com/openshift/machine-api-operator/blob/release-4.1/pkg/operator/status.go#L113-L114
machine-api-operator: https://github.com/openshift/machine-api-operator/blob/release-4.2/pkg/operator/status.go#L124-L125

cluster-autoscaler-operator: https://github.com/openshift/cluster-autoscaler-operator/blob/release-4.2/pkg/operator/status.go#L227-L230
cluster-autoscaler-operator: https://github.com/openshift/cluster-autoscaler-operator/blob/release-4.1/pkg/operator/status.go#L218-L221

Junqi Zhao, when you were looking for operators that do not have the reason field set, were both machine-api and cluster-autoscaler in degraded state?
Comment 3 Jan Chaloupka 2019-08-16 10:50:56 UTC 
Reason fields are already present in both operators. Closing.
Note You need to log in before you can comment on or make changes to this bug.