Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1639136

Summary:	Revert fix for bug 1614430 as it breaks heal monitoring
Product:	[oVirt] vdsm	Reporter:	Gobinda Das <godas>
Component:	Gluster	Assignee:	Kaustav Majumder <kmajumde>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.30.0	CC:	bugs, lveyde, matonb, sabose
Target Milestone:	ovirt-4.2.7	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdsm v4.20.43	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-02 14:37:30 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:	1637302

Description Gobinda Das 2018-10-15 06:42:48 UTC

Description of problem:
 We had patch https://gerrit.ovirt.org/#/c/94269/  which was merged and failed in QA.Looks like there are some more fixes needed from VDSM side which may take more time.
So to unblock we need to revert the patch and move BZ to 4.2.8

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 2018-10-16 06:15:09 UTC

*** Bug 1637302 has been marked as a duplicate of this bug. ***

Comment 2 SATHEESARAN 2018-10-22 10:05:08 UTC

Tested with vdsm-4.20.43

There are no error messages related self-heal

Comment 3 Sandro Bonazzola 2018-11-02 14:37:30 UTC

This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 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.