Description of problem: After removing the services (glusterfs, nfs, rpc-bind), the "gluster peer status" showing nodes in the cluster connected. Version-Release number of selected component (if applicable): glusterfs-3.7.1-15 How reproducible: Always Steps to Reproduce: 1.Add firewall services (glusterfs, nfs, rpc-bind) 2.Create a cluster of two nodes (node-1 and node-2) 3.Remove firewall services from the n/w zone in node-2 4.Check "gluster peer status" on node-1 Actual results: peer status showing "Connected" for Node-2 Expected results: Peer status has to show "Disconnected" for Node-2 Additional info: After "service glusterd restart", peer status showing properly.
IMO, firewalld doesn't change the behaviour of already established connections which is the case here. A subsequent peer probe/mount would fail post removal of the service file. If that's correct I wouldn't consider it as a bug :)
(In reply to Atin Mukherjee from comment #2) > IMO, firewalld doesn't change the behaviour of already established > connections which is the case here. A subsequent peer probe/mount would fail > post removal of the service file. If that's correct I wouldn't consider it > as a bug :) Thanks for that quick information. We can check with firewalld service behavior and then consider further actions required on this bug
Any updates on this, Satheesaran?
(In reply to Atin Mukherjee from comment #4) > Any updates on this, Satheesaran? Agree with comment2. Closing this bug