Bug 1555200 - [RFE] Implement reset-brick usage on the gluster volume
Summary: [RFE] Implement reset-brick usage on the gluster volume
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Gluster
Version: ---
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ovirt-4.2.2
: 4.20.22
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1396993
Blocks: Gluster-HC-3 1527302
TreeView+ depends on / blocked
 
Reported: 2018-03-14 07:06 UTC by Sandro Bonazzola
Modified: 2018-06-13 06:03 UTC (History)
5 users (show)

Fixed In Version: vdsm v4.20.22
Clone Of: 1396993
Environment:
Last Closed: 2018-05-14 15:10:43 UTC
oVirt Team: Gluster
Embargoed:
sbonazzo: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack+
sasundar: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 83979 0 None None None 2018-03-14 07:06:08 UTC
oVirt gerrit 83988 0 None None None 2018-03-14 07:06:08 UTC
oVirt gerrit 85880 0 None None None 2018-03-14 07:06:08 UTC
oVirt gerrit 85884 0 None None None 2018-03-14 07:06:08 UTC
oVirt gerrit 85885 0 None None None 2018-03-14 07:06:08 UTC
oVirt gerrit 88894 0 ovirt-4.2 MERGED gluster: api for reset-brick 2018-03-14 07:37:17 UTC
oVirt gerrit 88897 0 None None None 2018-03-14 07:06:08 UTC
oVirt gerrit 88898 0 ovirt-engine-4.2 MERGED webadmin: Support for reset brick 2018-03-15 10:56:15 UTC

Comment 2 Sandro Bonazzola 2018-03-14 07:08:35 UTC 
VDSM side of the RFE
Comment 3 SATHEESARAN 2018-05-12 11:18:39 UTC 
Verified with RHV 4.2.3-6 and glusterfs-3.12 with the following steps.

1. Create a new volume in a hyperconverged setup
2. Select a brick and perform a reset brick

Observed that the reset brick was successful and the contents of the bricks are healed successfully.
Comment 4 Sandro Bonazzola 2018-05-14 15:10:43 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.