Bug 1693933 - Qualify EC volumes with brick multiplexing over fuse access protocol
Summary: Qualify EC volumes with brick multiplexing over fuse access protocol
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: disperse
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.5.0
Assignee: Mohit Agrawal
QA Contact: Upasana
URL:
Whiteboard:
Depends On:
Blocks: 1696803
TreeView+ depends on / blocked
 
Reported: 2019-03-29 04:48 UTC by Atin Mukherjee
Modified: 2019-10-30 12:20 UTC (History)
8 users (show)

Fixed In Version: glusterfs-6.0-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-30 12:20:22 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:20:46 UTC

Comment 8 Nag Pavan Chilakam 2019-07-23 09:28:59 UTC
Also some earlier testing we did was tracked at https://docs.google.com/spreadsheets/d/1_jmnDAcs1TqXbWjw-r4iCYo4zGKheSAzP1lfMSxVS6w/edit#gid=0
Kindly note that we may be doing additional rounds of non-functional testing in regression cycle, and if we hit any issues, we would raise them seperately, and can take a call on those bugs based on severity.

Bugs reported so far which are either related to ec+bmux or hit on those testbeds can be tracked at https://bugzilla.redhat.com/buglist.cgi?classification=Red%20Hat&f1=cf_qa_whiteboard&list_id=10354050&o1=substring&product=Red%20Hat%20Gluster%20Storage&query_format=advanced&v1=3.5.0-cvlt

Comment 10 errata-xmlrpc 2019-10-30 12:20:22 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/RHEA-2019:3249


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