Bug 1837540

Summary: [BM IPI] Cluster reports upgrade in progress after restoring to previous state after upgrade
Product: OpenShift Container Platform Reporter: Yurii Prokulevych <yprokule>
Component: EtcdAssignee: Suresh Kolichala <skolicha>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: geliu, mfojtik, sbatsche, skolicha, wlewis
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: LifecycleReset
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:00:21 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: 1877930    

Description Yurii Prokulevych 2020-05-19 15:44:24 UTC 
Description of problem:
-----------------------
Restoring cluster post upgrade 4.4 -> 4.5 to backup taken at 4.4 

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
4.4.0-0.nightly-2020-05-15-095335 upgraded to 4.5.0-0.nightly-2020-05-19-041951



Steps to Reproduce:
-------------------
1. https://url.corp.redhat.com/0ae67ea
2.
3.

Actual results:
---------------
Cluster reports there is ongoing upgrade, though actual backup was taken before starting upgrade

```
oc adm upgrade
info: An upgrade is in progress. Working towards 4.5.0-0.nightly-2020-05-19-041951: 11% complete

No updates available. You may force an upgrade to a specific release image, but doing so may not be supported and result in downtime or data loss.
```


Expected results:
-----------------
Cluster state shouldn't report upgrade in progress


Additional info:
----------------
Virtual setup: 3masters + 2 workers
Comment 5 Sam Batschelet 2020-06-20 13:01:17 UTC 
I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint.

In general, this falls under DR improvements/"correctness" work tasked for 4.6
Comment 8 Michal Fojtik 2020-08-30 13:59:24 UTC 
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 10 Michal Fojtik 2020-08-31 17:59:30 UTC 
The LifecycleStale keyword was removed because the bug got commented on recently.
The bug assignee was notified.
Comment 14 ge liu 2020-09-16 11:48:35 UTC 
Filed new bug https://bugzilla.redhat.com/show_bug.cgi?id=1879481 in verifying process.
Comment 26 errata-xmlrpc 2020-10-27 16:00:21 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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196