Bug 1182373

Summary: [RFE][HC] - UI should allow a start with force option for a glusterfs volume in degraded state
Product: [oVirt] ovirt-engine Reporter: Paul Cuzner <pcuzner>
Component: RFEsAssignee: anmol babu <anbabu>
Status: CLOSED CURRENTRELEASE QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: medium    
Version: ---CC: amureini, anbabu, bugs, gklein, iheim, juwu, knarra, laravot, lsurette, mgoldboi, rbalakri, sabose, srevivo, ykaul
Target Milestone: ovirt-4.0.0-alphaKeywords: FutureFeature
Target Release: 4.0.0Flags: ylavi: ovirt-4.0.0?
rule-engine: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.0.0 Doc Type: Enhancement
Doc Text:
When one or more bricks are down on a started volume, you can now force start the brick(s) through the Administration Portal.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-12 14:05:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1177771, 1277939    
Attachments:
Description Flags
volume start force option none

Description Paul Cuzner 2015-01-15 00:41:10 UTC 
Description of problem:
when a volume has a brick down, but the other bricks are online the UI does not provide the admin with a start force option to bring the brick process back up. This means the admin has to logon to one of the nodes to issue the start from the CLI. In the hyperconverged use case, CLI level interaction is undesireable and problems like these should be resolved in the UI.

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


How reproducible:


Steps to Reproduce:
1. create a volume
2. kill a brick
3. start option is greyed out.

Actual results:
unable to get the brick process back online from the UI

Expected results:
a start for a volume in degraded should be allowed, to force missing processes to restart.

Additional info:
Comment 2 anmol babu 2015-09-23 05:34:18 UTC 
Moved it to ON_QA the patch is already merged and in 3.6 but I missed it accidentlly
Comment 3 Yaniv Kaul 2015-12-12 16:51:58 UTC 
How is it ON_QA for 4.0 already? (see target milestone and target release fields)
Comment 4 Yaniv Kaul 2015-12-12 16:52:23 UTC 
How is it ON_QA for 4.0 already? (see target milestone and target release fields)
Comment 5 anmol babu 2016-08-10 09:15:32 UTC 
@Yaniv, my apologies, this was wrongly moved on_qa as the patch was merged.
Comment 6 RamaKasturi 2016-08-11 12:21:08 UTC 
Verified and works fine with build ovirt-engine-4.0.2.2-0.1.el7ev.noarch.

Tested the following scenarios:
===============================
1) Kill one brick and start force from UI.
2) Kill two or more bricks and start force from UI.
3) start force all the volumes where some of the bricks are down.
4) start  button gets enabled only when volume is stopped/ some of the bricks in the volume are down.

Attaching the screenshot for the same.
Comment 7 RamaKasturi 2016-08-11 12:22:28 UTC 
Created attachment 1190047 [details]
volume start force option