Bug 1224706

Summary: [New] - Cannot assign gluster network role to the logical networks created.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: RHS-C QE <rhsc-qe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.1CC: asrivast, nlevinki, rhs-bugs, sabose, vagarwal
Target Milestone: ---   
Target Release: RHGS 3.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhsc-3.1.0-58 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-29 05:29:42 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: 1202842, 1224288    

Description RamaKasturi 2015-05-25 12:08:56 UTC
Description of problem:
UI displays an error message "Gluster networks are not supported in this cluster compability version"  while assigning gluster network role to  the logical networks 

Version-Release number of selected component (if applicable):
rhsc-3.1.0-0.0.scratch.master.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. create a logical network called 'glusternetwork'
2. Now try assigning the role of gluster network to the logical network created.
3.

Actual results:
Ui displays an operation cancelled dialog box with message "Error while executing action: Gluster networks are not supported in this cluster compatibility version"

Expected results:
User should be able to successfully assign the role to the logical network.

Additional info:

Comment 2 RamaKasturi 2015-06-05 07:20:04 UTC
Verified and works fine with build rhsc-3.1.0-0.58.master.el6.noarch.

Able to assign logical network to gluster network in cluster compatibility version of 3.5

Comment 4 errata-xmlrpc 2015-07-29 05:29:42 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://rhn.redhat.com/errata/RHEA-2015-1494.html