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

Bug 1723540

Summary:	The status information confuse users during software upgrading
Product:	OpenShift Container Platform	Reporter:	Weibin Liang <weliang>
Component:	Cluster Version Operator	Assignee:	Abhinav Dahiya <adahiya>
Status:	CLOSED DUPLICATE	QA Contact:	liujia <jiajliu>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
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:	2019-06-24 18:47:47 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:

Description Weibin Liang 2019-06-24 18:43:35 UTC

Description of problem:
During software upgrading, I got two different errors and the working status reached at 89% one time, then down to 75% and 3%, and go back to 89% again. 

Those errors and wrong upgrading progress really confuse the users, even upgrading finished at the end. 

Version-Release number of the following components:
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        False         112m    Cluster version is 4.1.2


How reproducible:
Easy

Steps to Reproduce:
oc adm upgrade --to=4.1.3 #from 4.1.2


Actual results:
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          2m44s   Working towards 4.1.3: 13% complete
[root@dhcp-41-193 ~]# oc get clusterversion
Error from server (NotFound): Unable to list "config.openshift.io/v1, Resource=clusterversions": the server could not find the requested resource (get clusterversions.config.openshift.io)
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          7m27s   Working towards 4.1.3: 67% complete
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          8m11s   Unable to apply 4.1.3: an unknown error has occurred
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          8m15s   Unable to apply 4.1.3: an unknown error has occurred
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          27m     Working towards 4.1.3: 89% complete
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          36m     Working towards 4.1.3: 75% complete
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          38m     Working towards 4.1.3: 3% complete
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          39m     Working towards 4.1.3: 67% complete
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.2     True        True          39m     Working towards 4.1.3: 89% complete
[root@dhcp-41-193 ~]# oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.1.3     True        False         18s     Cluster version is 4.1.3

Expected results:
Show correct working progress status and only show the errors when upgrading fail and stop.

Comment 1 Abhinav Dahiya 2019-06-24 18:47:47 UTC


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