Bug 1120908

Summary:	[RFE] After snapshot restore fstab changes should be made automatically
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Paul Cuzner <pcuzner>
Component:	snapshot	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.0	CC:	mzywusko, rhs-bugs, sunkumar
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Update fstab files after snapshot restore operation Reason: Correctly handle the workflow following a restore Result: removes the overhead from customers, and potential for human error	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-02 12:33:18 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 Paul Cuzner 2014-07-18 01:17:43 UTC

Description of problem:

Following a snapshot restore, the brick paths change. However, the entries in the fstab of each peer in the trusted pool still points to the old bricks. At the moment (3.0GA), the admin is expected to updated every node to reflect the revised brick names in each peers /etc/fstab.

This RFE requests that the updates to fstab across the trusted pool should be automatic. This update should not be left to customers to do, and it should be viewed as part of the workflow relating to snapshot restore.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Sunny Kumar 2018-04-02 12:33:18 UTC

Closing this bug now we will file separate git-hub issue and will address in gd2.