Description of problem:

commit 243a5b429f225acb8e7132264fe0a0835ff013d5 turn's 'ON'
allow-insecure and bind-insecure by default.

while upgrading subset of nodes from a trusted storage pool,
nodes which have older versions of glusterfs will expect
connection from secure ports only (since they still have
bind-insecure off) thus they reject connection from upgraded
nodes which now have insecure ports.

Hence we will run into connection issues between peers.


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

reproducible:
Simple, upgrading a subset of nodes from trusted pool will show you failure in connection between peers

Actual results:
Failure in connection between non-upgraded nodes and upgraded nodes

Expected results:
No connection issues between peers

Additional info: