Bug 1850693

Summary:	VDO mount options are added for the bricks created on top of LUKS devices
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	rhhi	Assignee:	Gobinda Das <godas>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.5	CC:	rhs-bugs
Target Milestone:	---
Target Release:	RHHI-V 1.8
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gluster-ansible-infra-1.0.4-11.el8rhgs.noarch.rpm	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1850830 (view as bug list)		Environment:
Last Closed:	2020-08-04 14:52:36 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:
Bug Depends On:	1850830
Bug Blocks:	1779977

Description SATHEESARAN 2020-06-24 17:47:27 UTC

Description of problem:
-----------------------
When creating the bricks on the top of LUKS device, those devices have mount options similar to VDO devices added in /etc/fstab


Version-Release number of selected component (if applicable):
--------------------------------------------------------------
gluster-ansible-infra-1.0.4-10.el8rhgs
RHVH-4.4.1

How reproducible:
------------------
Always

Steps to Reproduce:
---------------------
1. Provide the LUKS device for bricks for engine, vmstore, data
2. Enable VDO only on one brick
3. Check /etc/fstab mount options for the bricks for all the bricks

Actual results:
---------------
All the bricks contains the mount option relevant for VDO volumes

Expected results:
------------------
Only the bricks created on top of VDO volumes should have the relevant VDO options

Comment 3 SATHEESARAN 2020-07-10 11:08:12 UTC

Tested with gluster-ansible-infra-1.0.4-11.el8rhgs

When LUKS devices are used as disks, the fstab mount options no longer reflect the VDO mount options

UUID=eaf61294-73f2-4c27-8622-48149a98b8eb /gluster_bricks/engine xfs inode64,noatime,nodiratime 0 0
UUID=b99d1bae-c289-4a5b-bff3-7dd066b29f45 /gluster_bricks/data xfs inode64,noatime,nodiratime 0 0
UUID=c6810c7f-7015-414d-aea9-ad991852aa2f /gluster_bricks/vmstore xfs inode64,noatime,nodiratime 0 0
UUID=c274902f-65e7-4fde-a1c5-ab5cf381bd5f /gluster_bricks/testvol xfs inode64,noatime,nodiratime 0 0

Comment 4 errata-xmlrpc 2020-08-04 14:52:36 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHHI for Virtualization 1.8 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:3314