Bug 1948012

Summary:	service-ca constantly reporting type "Upgradeable" status Unknown
Product:	OpenShift Container Platform	Reporter:	W. Trevor King <wking>
Component:	service-ca	Assignee:	Miloslav Trmač <mitr>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.8	CC:	adam.kaplan, aos-bugs, gvanderp, kewang, mfojtik, mjudeiki, rrackow, sanchezl, wewang, wking
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: The service-ca-operator was not explicitly populating an “Upgradeable” condition in its ServiceCA custom resource. Consequence: The service-ca’s ClusterOperator custom resource reported the “Upgradeable” condition as “Unknown”. Fix: The “Upgradeable” condition in the ServiceCA custom resource is explicitly populated, triggering a corresponding condition in the ClusterOperator custom resource. Result: Both the ServiceCA and the service-ca’s ClusterOperator custom resources now report a specific “Upgradeable” value.	Story Points:	---
Clone Of:	1948011	Environment:
Last Closed:	2021-07-27 22:58:43 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:
Bug Depends On:
Bug Blocks:	1966148

Description W. Trevor King 2021-04-09 18:29:42 UTC

+++ This bug was initially created as a clone of Bug #1948011 +++

+++ This bug was initially created as a clone of Bug #1928141 +++

service-ca currently sets Upgradeable=Unknown, which is potentially confusing to users.  If it does not want to block minor updates, it should either leave Upgradeable completely unset or set it Upgradeable=True.  When this bug is fixed, we should remove the temporary exception I'm granting in [1].

[1]: https://github.com/openshift/origin/pull/26030

Comment 3 W. Trevor King 2021-05-25 23:55:59 UTC

Moving back to POST for a moment, so I can hang the origin PR that drops the exception on this bug too.

Comment 5 W. Trevor King 2021-05-27 14:03:29 UTC

I was too quick on dropping the origin exceptions, because until the operator changes make their way back to 4.7, a stricter origin will fail 4.7->4.8 updates.  Back to POST so I can revert...

Comment 11 errata-xmlrpc 2021-07-27 22:58:43 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438