Bug 1311084

Summary: [RFE] Deployment over gdeploy should be able to recover from failures
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Sachidananda Urs <surs>
Component: gdeployAssignee: Nandaja Varma <nvarma>
Status: CLOSED ERRATA QA Contact: Anush Shetty <ashetty>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: asrivast, bmohanra, musoni, nvarma, rcyriac, rhinduja, sabose, smohan
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: RHGS 3.1.3   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gdeploy-2.0-2 Doc Type: Enhancement
Doc Text:
In case of failures gdeploy would stop at that point and the user had to manually undo the partially completed operations before restarting the program. This was a manual and cumbersome exercise, and user had to login to the machines to fix. With this release gdeploy now continues from where it left off and all the earlier completed steps are ignored.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-23 05:29:29 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: 1258386, 1311386    

Description Sachidananda Urs 2016-02-23 11:00:35 UTC
gdeploy should ignore errors and continue from previous point of failure.

Currently in 1.0 release, gdeploy expects system to be cleaned up before
continuing. This is quite cumbersome, the tool should be able to continue
from the earlier point of failure.

Comment 2 Anush Shetty 2016-04-12 07:59:22 UTC
Verified with gdeploy-2.0-5.el7rhgs.noarch

Comment 4 errata-xmlrpc 2016-06-23 05:29:29 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, 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/RHEA-2016:1250