Unable to start gluster volume after upgrade to RHGS 3.5

Issue

• When a volume is created and started each gluster cluster member should "scan" the portrange for gaps in the assignment of ports and if they can bind to this port; the port maps should be merged from each member to find a proper port for the brick.
• When there are so many volumes the port range indicated in /etc/glusterfs/glusterd.vol can have no ports free to accommodate the brick hence the volume can´t start.