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

Bug 1897612

Summary:	RFE: Installer task display
Product:	OpenShift Container Platform	Reporter:	Pablo Iranzo Gómez <pablo.iranzo>
Component:	Cluster Version Operator	Assignee:	Over the Air Updates <aos-team-ota>
Status:	CLOSED DUPLICATE	QA Contact:	Johnny Liu <jialiu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.6.z	CC:	aos-bugs, jokerman, wking, yanyang
Target Milestone:	---	Keywords:	RFE
Target Release:	---
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:	2020-11-13 17:53:26 UTC	Type:	Bug
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:	1831748

Description Pablo Iranzo Gómez 2020-11-13 16:10:00 UTC

Version:

$ openshift-install version
4.6.3

Platform:
baremetal IPI


What happened?

The install log, works fine as a general debug, but would be great to get some 'detail' in the oc get clusterversion as it 'progresses towards $VERSION' on install status

I'm thinking about something in the lines of 'waiting master nodes to power up' or other more descriptive messages that are in between what the log shows and just the % of install progress


# Always at least include the `.openshift_install.log`

Intermediate 'status' information shown

How to reproduce it (as minimally and precisely as possible)?

Perform an OpenShift installation

Comment 1 W. Trevor King 2020-11-13 17:53:26 UTC

installer is just passing on the string from ClusterVersion's status.  Cluster-version operator sets that string, so this is a CVO RFE.  We've had a few bugs around improvements to those condition strings, and the current tracker is bug 1768255, so I'm closing this request to fold it into that existing tracker.

*** This bug has been marked as a duplicate of bug 1768255 ***