Description of problem:
Instead of self daemon, nfs server is coming up after glusterd restart.
Version-Release number of selected component (if applicable):
3.8.4-50
How reproducible:
2/2
Steps to Reproduce:
1. Created replica volume 2*2 using 3 nodes cluster and started it.
2. Stop glusterd on other two nodes.
3. Check the volume status on node where glusterd is running and do glusterd restart
4. check the gluster vol status
Actual results:
Before glusterd restart
Status of volume: replica_vol
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick 10.70.37.52:/bricks/brick0/replica_vo
l N/A N/A N N/A
Brick 10.70.37.52:/bricks/brick1/replica_vo
l N/A N/A N N/A
Self-heal Daemon on localhost N/A N/A Y 4062
Task Status of Volume replica_vol
------------------------------------------------------------------------------
There are no active volume tasks
After glusterd restart
Status of volume: replica_vol
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick 10.70.37.52:/bricks/brick0/replica_vo
l N/A N/A N N/A
Brick 10.70.37.52:/bricks/brick1/replica_vo
l N/A N/A N N/A
NFS Server on localhost N/A N/A N N/A
Task Status of Volume replica_vol
------------------------------------------------------------------------------
There are no active volume tasks
Expected results:
Self heal daemon should come up, not nfs-server daemon
Additional info:
Considering the nature of the test case, this isn't a priority to be fixed in coming months. Engineering wouldn't be spending time in fixing this going forward. Closing this as won't fix. If you have any valid justification on why this test case can be a priority for users, please feel free to reopen.