Bug 1346253 - [RFE] Provide a option in the sections to abort, if the intended the operation fails
Summary: [RFE] Provide a option in the sections to abort, if the intended the operatio...
Keywords:
Status: CLOSED DUPLICATE of bug 1341484
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Sachidananda Urs
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-14 11:16 UTC by SATHEESARAN
Modified: 2016-06-16 08:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-16 08:11:24 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2016-06-14 11:16:58 UTC
Description of problem:
-----------------------
gdeploy should provide the option to abort the installation when the particular section fails.

What happens with HCI installation, if something fails, gdeploy doesn't exit there, but continues to the next step, which lead to total misconfiguration.

Take for example, if the creation of vg fails, then there is no point in creation of lv1 ( thick-pool ), lv2 ( thin-pool ), lv3 ( thin lv), lv4 (thin-lv )

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gdeploy-2.0-16

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
NA

Actual results:
---------------
gdeploy configuration doesn't stop on failure

Expected results:
-----------------
Provide an option in each of the section - 'abort_on_failure=<val>' - where val can be 0 or 1.

Additional info:
----------------
Based on the requirement the user can opt to abort the gdeploy configuration/installation to abort on failure, or to proceed if required.

Comment 1 SATHEESARAN 2016-06-14 11:17:40 UTC
Credits to Kasturi for bring in this valid scenario.

Comment 2 SATHEESARAN 2016-06-16 08:11:24 UTC

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


Note You need to log in before you can comment on or make changes to this bug.