Bug 616627

Summary:	Documentation, Admin GFS2: User-visible Differences between RHEL 6 and RHEL 5 cluster & clustered storage features
Product:	Red Hat Enterprise Linux 6	Reporter:	Paul Kennedy <pkennedy>
Component:	doc-Global_File_System_2	Assignee:	Steven J. Levine <slevine>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	adstrong, jha, slevine
Target Milestone:	rc	Keywords:	Documentation, FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	616624	Environment:
Last Closed:	2010-11-11 15:29:50 UTC	Type:	---
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:	616624
Bug Blocks:	616625

Description Paul Kennedy 2010-07-21 01:46:18 UTC

+++ This bug was initially created as a clone of Bug #616624 +++

Description of problem:
Based on requirements stated in Bug 561421, ensure that content in this
document aligns with those requirements.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Steven J. Levine 2010-10-12 20:11:27 UTC

I have updated the GFS2 document with the RHEL 6 user-visible differences and checked the changes into the SVN repository. I am moving this bug to MODIFIED.

Comment 4 Michael Doyle 2010-10-15 04:41:05 UTC

No details have been given of the changes to the document, therefore, we are
unable to verify this bug. Moving this bug to VERIFIED and if there are issues
from QE or SME review a new bug will be raised for this document.

Comment 5 releng-rhel@redhat.com 2010-11-11 15:29:50 UTC

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.