Bug 1880370 - [Doc] Table 6.4. Red Hat Gluster Storage Support Matrix needs to be updated with the exact supported versions
Summary: [Doc] Table 6.4. Red Hat Gluster Storage Support Matrix needs to be updated w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Administration_Guide
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 3.5.z Batch Update 3
Assignee: Amrita
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: 1822639
TreeView+ depends on / blocked
 
Reported: 2020-09-18 11:20 UTC by Prasanth
Modified: 2021-01-11 08:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-11 08:57:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Prasanth 2020-09-18 11:20:54 UTC
Describe the issue:

Table 6.4. Red Hat Gluster Storage Support Matrix needs to be updated with the exact supported versions

We don't support 3.5 servers on rhel6, only clients allowed. 

On table entry for RHEL 6.10, we see now 3.4 and 3.5 as RHGS server, and as fuse client 3.5, 3.4, 3.3.z. See below:

Red Hat Enterprise Linux version Red Hat Gluster Storage version Native client version
6.10			         3.4, 3.5	       		 3.5, 3.4, 3.3.z


This should be updated as follows:

Red Hat Enterprise Linux version Red Hat Gluster Storage version Native client version
6.10			         3.4	       		        3.5*, 3.4, 3.3.z


Also we need to put a note that rhel6 native client with 3.5 version is supported only for 3.5 servers



Describe the task you were trying to accomplish:

Suggestions for improvement:

Document URL:

Chapter/Section Number and Title:

Product Version:

Environment Details:

Any other versions of this document that also needs this update:

Additional information:

Comment 3 Amrita 2020-10-14 06:01:16 UTC
Hi Team,
Moving this back to modified state as pm ack is required.

Thanks
Amrita


Note You need to log in before you can comment on or make changes to this bug.