Bug 1635938

Summary:	fstab entry for a XFS bricks created on VDO volume, should have additional mount option
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	gluster-ansible	Assignee:	Sachidananda Urs <surs>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	apaladug, rcyriac, rhs-bugs, sabose, sanandpa, sankarshan, sasundar
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.4.z Batch Update 1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gluster-ansible-roles-1.0.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1635939 (view as bug list)		Environment:
Last Closed:	2018-10-31 08:42:30 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:
Bug Blocks:	1635939

Description SATHEESARAN 2018-10-04 02:26:51 UTC

Description of problem:
-----------------------
Kernel Filesystem service is started ahead of VDO service. To enable VDO service to start ahead, there is a special mount option - 'x-systemd.requires=vdo.service' - that needs to be added to the XFS fstab entry.

Example:
/dev/gluster_vg_sdc/gluster_lv_engine /gluster_bricks/engine xfs inode64,noatime,nodiratime,x-systemd.requires=vdo.service 0 0

But the gluster-ansible role is not adding this special mount option to fstab entry, if VDO is enabled

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gluster-ansible-role-1.0

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

Steps to Reproduce:
-------------------
1. Create a playbook that enabled VDO volumes & creates bricks up on that.
2. Observe the /etc/fstab

Actual results:
---------------
fstab entry doesn't have the special mount option - 'x-systemd.requires=vdo.service', and this leads to reboot of hosts going to maintenance shell as the filesystems are not available

Expected results:
-----------------
If XFS bricks are created on the VDO volume, fstab entry should have additional mount option - 'x-systemd.requires=vdo.service'

Comment 2 Sachidananda Urs 2018-10-04 08:24:14 UTC

Patch: https://github.com/gluster/gluster-ansible-infra/commit/db8fc7 should fix the issue.

Comment 4 SATHEESARAN 2018-10-16 02:43:56 UTC

Tested with gluster-ansible-role-1.0.3

When XFS filesystem created over VDO volume, fstab entry is added with the required options

/dev/gluster_vg_sdc/gluster_lv_data /gluster_bricks/data xfs inode64,noatime,nodiratime,x-systemd.requires=vdo.service 0 0
/dev/gluster_vg_sdc/gluster_lv_vmstore /gluster_bricks/vmstore xfs inode64,noatime,nodiratime,x-systemd.requires=vdo.service 0 0
/dev/gluster_vg_sdc/gluster_lv_engine /gluster_bricks/engine xfs inode64,noatime,nodiratime,x-systemd.requires=vdo.service 0 0

Comment 6 errata-xmlrpc 2018-10-31 08:42:30 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, 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/RHBA-2018:3428