glusterfs.git, branch v5.5

doc: Added release notes for 5.5

2019-03-15T12:56:07+00:00

Fixes: bz#1689214
Change-Id: I57a1afa2649828d0399fab2bf163a05cf35358db
Signed-off-by: ShyamsundarR

eventsapi: Fix error while handling GlusterCmdException

2019-03-15T12:45:45+00:00

`GlusterCmdException` was wrongly accessed instead of accessing
`GlusterCmdException.message`.

Fixes: bz#1687249
Change-Id: I35ec1b05726050bfd8761e05ad9b9e47917dc0c6
Signed-off-by: Aravinda VK 
(cherry picked from commit 27f6375df009c8c4798b72aeafce79456007d21f)

cluster/afr: Send truncate on arbiter brick from SHD

2019-03-12T07:21:26+00:00

Problem:
In an arbiter volume configuration SHD will not send any writes onto the arbiter
brick even if there is data pending marker for the arbiter brick. If we have a
arbiter setup on the geo-rep master and there are data pending markers for the files
on arbiter brick, SHD will not mark any data changelog during healing. While syncing
the data from master to slave, if the arbiter-brick is considered as ACTIVE, then
there is a chance that slave will miss out some data. If the arbiter brick is being
newly added or replaced there is a chance of slave missing all the data during sync.

Fix:
If there is data pending marker for the arbiter brick, send truncate on the arbiter
brick during heal, so that it will record truncate as the data transaction in changelog.

Change-Id: I3242ba6cea6da495c418ef860d9c3359c5459dec
fixes: bz#1687687
Signed-off-by: karthik-us

core: make compute_cksum function op_version compatible

2019-03-11T00:31:01+00:00

Problem: commit 5a152a changed the mechansim of computing the
checksum. In heterogeneous cluster, peers are running into
rejected state because we have different cksum computation
mechansims in upgraded and non-upgraded nodes.

Solution: add a check for op-version so that all the nodes
in the cluster follow the same mechanism for computing the
cksum.

fixes: bz#1684569

> Change-Id: I1508f000e8c9895588b6011b8b6cc0eda7102193
> BUG: bz#1685120
> Signed-off-by: Sanju Rakonde 

Change-Id: I1508f000e8c9895588b6011b8b6cc0eda7102193
Signed-off-by: Sanju Rakonde

dict: handle STR_OLD data type in xdr conversions

2019-03-07T10:39:21+00:00

Currently a dict conversion on wire for 3.x protocol happens using
`dict_unserialize()`, which sets the type of data as STR_OLD. But the
new protocol doesn't send it over the wire as its not considered as a
valid format in new processes.

But considering we deal with old and new protocol when we do a rolling
upgrade, it will allow us to get all the information properly with new
protocol.

Credits: Krutika Dhananjay

Fixes: bz#1684385
Change-Id: I165c0021fb195b399790b9cf14a7416ae75ec84f
Signed-off-by: Amar Tumballi

doc: Added release notes for release 5.4

2019-02-26T14:21:12+00:00

Change-Id: I6aaa93edc4ae7d018c83c5d23d536075c013d0b5
fixes: bz#1667103
Signed-off-by: ShyamsundarR

eventsapi: Fix Python3 compatibility issues

2019-02-26T05:11:49+00:00

- Fixed Relative import and non-package import related issues.
- socketserver import issues fix
- Renamed installed directory name to `gfevents` from `events`(To
  avoid any issues with other global libs)

Fixes: bz#1649054
Change-Id: I3dc38bc92b23387a6dfbcc0ab8283178235bf756
Signed-off-by: Aravinda VK 
(cherry picked from commit cd68f7b88b9a2c9a4e4ff9fca61517384e54130a)

packaging: Obsoleting glusterfs-gnfs for upgrade

2019-02-25T15:23:26+00:00

Master refs
>    https://review.gluster.org/#/c/glusterfs/+/22253/
>    fixes: bz#1672711
>    Change-Id: Iad7194e788a8eeecd617614e9f8a1fe3264a384d
>    Signed-off-by: Sahina Bose 
>    Signed-off-by: Jiffin Tony Thottan 

Fixes: bz#1679968
Change-Id: Ib66d15953abb2645238f01c8ee9df54d2b35736a
Signed-off-by: Kaleb S. KEITHLEY 
Signed-off-by: Jiffin Tony Thottan

socket: socket event handlers now return void

2019-02-25T15:23:11+00:00

Problem:
Returning any value from socket event handlers to the event sub-system
doesn't make sense since event sub-system cannot handle socket
sub-system errors.

Solution:
Change return type of all socket event handlers to 'void'

mainline:
> Reviewed-on: https://review.gluster.org/c/glusterfs/+/22221

Change-Id: I70dc2c57f12b7ea2fae41120f71aa0d7fe0b2b6f
Fixes: bz#1651246
Signed-off-by: Milind Changire 
(cherry picked from commit 776ba851c6ee6c265253d44cf1d6e4e3d4a21772)

fuse: reflect the actual default for lru-limit option

2019-02-25T15:16:31+00:00

in both `--help` text and man page

updates: bz#1667103
Change-Id: I9aa9367c6863ac8e2403255280697c9e6be26cf0
Signed-off-by: Amar Tumballi