Back to bug 1319638

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-03-21 08:55:49 UTC Keywords ZStream
Prasanna Kumar Kalever 2016-03-21 09:03:18 UTC Assignee rhs-bugs prasanna.kalever
Atin Mukherjee 2016-03-21 09:17:06 UTC CC amukherj
Blocks 1311817
SATHEESARAN 2016-03-21 09:34:50 UTC CC sasundar
Flags needinfo?(amukherj)
Prasanna Kumar Kalever 2016-03-21 09:39:11 UTC Status NEW POST
SATHEESARAN 2016-03-21 10:28:05 UTC Flags needinfo?(amukherj)
Rahul Hinduja 2016-03-21 14:49:21 UTC CC rhinduja
Rejy M Cyriac 2016-03-21 16:06:53 UTC CC rcyriac
Atin Mukherjee 2016-03-21 16:48:39 UTC Status POST MODIFIED
Red Hat Bugzilla Rules Engine 2016-03-21 16:48:43 UTC Target Release --- RHGS 3.1.3
Satish Mohan 2016-03-24 13:27:39 UTC Status MODIFIED ON_QA
Fixed In Version glusterfs-3.7.9-1
Rahul Hinduja 2016-03-27 15:12:15 UTC QA Contact annair rhinduja
Rahul Hinduja 2016-04-21 08:06:21 UTC QA Contact rhinduja nerawat
Neha 2016-04-26 04:28:54 UTC Status ON_QA VERIFIED
sankarshan 2016-05-13 09:20:44 UTC CC sankarshan
Prasanna Kumar Kalever 2016-05-20 07:09:57 UTC Doc Text Cause:
Now with newer versions we have bind-insecure 'ON' by default.

Consequence:
while upgrading subset of nodes from a trusted storage pool,
nodes which have older versions of gluster 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.

Fix:
This patch will turn bind-insecure 'OFF' by default.

Result:
So, with this fix the upgrade will be smooth without peer
connection issues.
Laura Bailey 2016-06-14 01:46:21 UTC Doc Text Cause:
Now with newer versions we have bind-insecure 'ON' by default.

Consequence:
while upgrading subset of nodes from a trusted storage pool,
nodes which have older versions of gluster 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.

Fix:
This patch will turn bind-insecure 'OFF' by default.

Result:
So, with this fix the upgrade will be smooth without peer
connection issues.
Red Hat Gluster Storage 3.1 Update 2 contained an update that enabled both allow-insecure and bind-insecure by default. This meant that when users upgraded nodes with earlier Red Hat Gluster Storage versions, which expected secure connections with bind-insecure disabled, those nodes were rejected from the upgraded storage pool. This update disables bind-insecure by default and retains the default enablement of allow-insecure so that peer connection issues do not occur with older nodes.
Laura Bailey 2016-06-14 02:08:22 UTC CC prasanna.kalever
Flags needinfo?(prasanna.kalever)
SATHEESARAN 2016-06-14 06:00:35 UTC Doc Text Red Hat Gluster Storage 3.1 Update 2 contained an update that enabled both allow-insecure and bind-insecure by default. This meant that when users upgraded nodes with earlier Red Hat Gluster Storage versions, which expected secure connections with bind-insecure disabled, those nodes were rejected from the upgraded storage pool. This update disables bind-insecure by default and retains the default enablement of allow-insecure so that peer connection issues do not occur with older nodes. none
Flags needinfo?(prasanna.kalever)
errata-xmlrpc 2016-06-23 00:50:18 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-06-23 05:04:34 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-06-23 01:04:34 UTC
John Skeoch 2016-08-15 02:09:17 UTC CC sashinde
Rejy M Cyriac 2016-09-17 14:40:41 UTC Sub Component core
CC rhs-bugs, storage-qa-internal
Component glusterfs core

Back to bug 1319638