Bug 1317168 - [RFE]: UI option for healing a gluster volume [NEEDINFO]
Summary: [RFE]: UI option for healing a gluster volume
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Scott Herold
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-12 17:27 UTC by Raghavendra Bhat
Modified: 2020-04-15 14:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-09 10:04:45 UTC
oVirt Team: Gluster
Target Upstream Version:
sabose: needinfo? (rabhat)

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra Bhat 2016-03-12 17:27:13 UTC 
Description of problem:
Currently there's no way how to work with heal gluster subcommand via RHCS / RHEV-M. No alternative to CLI command gluster volume heal <volname> *.

It can be really useful to control & check heal also from GUI.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Sahina Bose 2016-07-26 10:22:35 UTC 
Does Bug 1205641 address your requirement? There's monitoring of heal added to 4.0, do you also need a way to trigger self-heal (isn't heal automatically triggered in gluster replicate volume)?
Comment 2 Yaniv Kaul 2016-12-01 18:00:24 UTC 
Is this going to 4.1?
Comment 3 Sahina Bose 2016-12-02 05:59:49 UTC 
No - heal monitoring has been added in 4.1, self-heal is auto-triggered in gluster and we do not yet provide the option from UI to force trigger of heal
Comment 4 Sahina Bose 2017-02-09 10:04:45 UTC 
Closing this bug as requested information in Comment 1 not provided, and Bug 1205641 addresses heal monitoring

Please re-open if you have further requirements
Note You need to log in before you can comment on or make changes to this bug.