Bug 1399038

Summary:	Tiering tests don't work in NetBSD
Product:	[Community] GlusterFS	Reporter:	Krutika Dhananjay <kdhananj>
Component:	tiering	Assignee:	hari gowtham <hgowtham>
Status:	CLOSED WONTFIX	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nbalacha, rgowdapp, rkavunga, rtalur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-02 08:13:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Krutika Dhananjay 2016-11-28 06:55:26 UTC

Description of problem:

Tiering commands don't work in NetBSD.

As per the following conversation on IRC:

(12:09:09  IST) rastar: pranithk1: general advice for all teams
(12:09:38  IST) rastar: pranithk1: grep "BUG=000000" tests/bugs/<your-component>
(12:10:07  IST) rastar: pranithk1: and for all those tests which have that line, file a bug and replace with BUG=<BUGID>

Raising this bug as an umbrella bug for all those tests in NetBSD that are marked bad/known issues against tiering, so that the string:

#G_TESTDEF_TEST_STATUS_NETBSD7=KNOWN_ISSUE,BUG=0000000

is filled with the id of this bug in the 'BUG' field.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Amar Tumballi 2018-11-02 08:13:28 UTC

Patch https://review.gluster.org/#/c/glusterfs/+/21331/ removes tier functionality from GlusterFS. 

https://bugzilla.redhat.com/show_bug.cgi?id=1642807 is used as the tracking bug for this. Recommendation is to convert your tier volume to regular volume (either replicate, ec, or plain distribute) with "tier detach" command before upgrade, and use backend features like dm-cache etc to utilize the caching from backend to provide better performance and functionality.