Bug 1416366

Summary: Provide a way to continue upgrade
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: inecas, lzap, mbacovsk, stbenjam
Target Milestone: Unspecified   
Target Release: Unused   
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: 2017-01-26 17:58:33 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: 1410795    

Description Lukas Zapletal 2017-01-25 11:24:36 UTC 
When upgrade fails during our pre/post steps (usually rake tasks), there is no way to recover other than manually investigating what happened.

This is a suggestion to store list of successful steps so upgrade can be either reexecuted (if the rest is idempotent) or at least providing an option to skip executed steps.

Easy implementation would be touching some timestamp files in /var/lib and informing user about skipped steps (and how to re-execute them when needed).

This is a RFE but I think this should be handled with priority for the next major upgrade.
Comment 1 Ivan Necas 2017-01-25 15:44:28 UTC 
We are already doing the touching thing. How does it differ form https://bugzilla.redhat.com/show_bug.cgi?id=1264597 ?

I though the upgrades are idempotent.

-- Ivan
Comment 3 Lukas Zapletal 2017-02-27 12:47:16 UTC 
Sure.