diff options
| author | Kaushal M <kaushal@redhat.com> | 2016-02-24 15:09:57 +0530 |
|---|---|---|
| committer | Kaushal M <kaushal@redhat.com> | 2016-02-28 20:46:17 -0800 |
| commit | 06f4a475f47f2acb243c9d1ad2e2f16587f0ff69 (patch) | |
| tree | 53d76ba7a6a3c79ea0c98ce32f9c7471ceb91454 /doc/release-notes/upgrading-from-3.7.2-or-older.md | |
| parent | 29adf166aa5f15202c5fe49369ad4f11df799c5b (diff) | |
Add missing release-notes
Change-Id: I16ad79b951c1e366fc94501063441459f9a4faad
BUG: 1311451
Signed-off-by: Kaushal M <kaushal@redhat.com>
Reviewed-on: http://review.gluster.org/13509
Smoke: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
Diffstat (limited to 'doc/release-notes/upgrading-from-3.7.2-or-older.md')
| -rw-r--r-- | doc/release-notes/upgrading-from-3.7.2-or-older.md | 37 |
1 files changed, 37 insertions, 0 deletions
diff --git a/doc/release-notes/upgrading-from-3.7.2-or-older.md b/doc/release-notes/upgrading-from-3.7.2-or-older.md new file mode 100644 index 00000000000..f4f41568455 --- /dev/null +++ b/doc/release-notes/upgrading-from-3.7.2-or-older.md @@ -0,0 +1,37 @@ +A new feature in 3.7.3 is causing troubles during upgrades from previous versions of GlusterFS to 3.7.3. +The details of the feature, issue and work around are below. + +## Feature +In GlusterFS-3.7.3, insecure-ports have been enabled by default. This +means that by default, servers accept connections from insecure ports, +clients use insecure ports to connect to servers. This change +particularly benefits usage of libgfapi, for example when it is used +in qemu run by a normal user. + +## Issue +This has caused troubles when upgrading from previous versions to +3.7.3 in rolling upgrades and when attempting to use 3.7.3 clients +with older servers. The 3.7.3 clients establish connections using +insecure ports by default. But the older servers still expect +connections to come from secure-ports (if this setting has not been +changed). This causes servers to reject connections from 3.7.3, and +leads to broken clusters during upgrade and rejected clients. + +## Workaround +There are two possible workarounds. +Before upgrading, + +1. Set 'client.bind-insecure off' on all volumes. +This forces 3.7.3 clients to use secure ports to connect to the servers. +This does not affect older clients as this setting is the default for them. + +2. Set 'server.allow-insecure on' on all volumes. +This enables servers to accept connections from insecure ports. +The new clients can successfully connect to the servers with this set. + + +If anyone faces any problems with these workarounds, please let us know via email[1][1] or in IRC[2][2]. + + +[1]: gluster-devel at gluster dot org / gluster-users at gluster dot org +[2]: #gluster / #gluster-dev @ freenode |