Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1741064

Summary:	[4.1.z]cluster-autoscaler/machine-api clusteroperator degraded reporting missing reason/detail information clusteroperator degraded reporting missing reason/detail information
Product:	OpenShift Container Platform	Reporter:	Junqi Zhao <juzhao>
Component:	Cloud Compute	Assignee:	Jan Chaloupka <jchaloup>
Status:	CLOSED NOTABUG	QA Contact:	Jianwei Hou <jhou>
Severity:	medium	Docs Contact:
Priority:	high
Version:	4.1.z	CC:	agarcial, ecordell, jfan
Target Milestone:	---
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1741062	Environment:
Last Closed:	2019-08-16 10:50:56 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:

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.