+++ This bug was initially created as a clone of Bug #1734534 +++ Description of problem: When a user had edited the glusterd.vol file in /etc/glusterfs and updates the glusterfs packages, bricks cannot contact glusterd. Version-Release number of selected component (if applicable): glusterfs-6 and above (including mainline) How reproducible: Always Steps to Reproduce: 1. install glusterfs-5 or lower 2. create and start a volume 3. edit glusterd.vol and modify options like base port / max port 4. yum update gluster packages to glusterfs-6 5. restart volumes Actual result: bricks can't talk to glusterd Expected result: bricks should be able to talk to glusterd on 24007. --- Additional comment from Raghavendra Talur on 2019-08-05 14:33:01 UTC --- I think the change happened in c96778b354ea82943442aab158adbb854ca43a52 commit upstream and I propose that we fix this problem by keeping the default in code for glusterd and letting glusterd.vol override ride instead of having the value only in glusterd.vol.
REVIEW: https://review.gluster.org/23160 (rpc/transport: have default listen-port) posted (#1) for review on master by Atin Mukherjee
REVIEW: https://review.gluster.org/23160 (rpc/transport: have default listen-port) merged (#2) on master by Amar Tumballi