DescriptionBala Konda Reddy M
2018-05-03 12:21:58 UTC
Created attachment 1430644[details]
Brick is offline
Description of problem:
Bricks are in the offline state when glusterd is started when NIC is down
Version-Release number of selected component (if applicable):
3.12.2-8
How reproducible:
2/2
Steps to Reproduce:
1. Created and started a replica volume X3
2. Stop glusterd on node
3. Bring down the NIC( ifdown <interface>) where glusterd is stopped.
4. Start glusterd
Actual results:
glusterd is up and running, glusterfsd is NA and seen NFS daemon
Expected results:
glusterd, glusterfsd and glustershd should be running
Additional info:
Once the nic is up, brick on one node is offline where we brought down the NIC
gluster vol status
Status of volume: testvol
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick 10.70.37.193:/bricks/brick0/testvol 49155 0 Y 17871
Brick 10.70.37.163:/bricks/brick0/testvol 49155 0 Y 17797
Brick 10.70.37.67:/bricks/brick0/testvol N/A N/A N N/A
Self-heal Daemon on localhost N/A N/A Y 3270
Self-heal Daemon on dhcp37-193.lab.eng.blr.
redhat.com N/A N/A Y 17979
Self-heal Daemon on dhcp37-163.lab.eng.blr.
redhat.com N/A N/A Y 17868
Task Status of Volume testvol
------------------------------------------------------------------------------
There are no active volume tasks
After reboot, all bricks are online
gluster vo status
Status of volume: testvol
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick 10.70.37.193:/bricks/brick0/testvol 49155 0 Y 17871
Brick 10.70.37.163:/bricks/brick0/testvol 49155 0 Y 17797
Brick 10.70.37.67:/bricks/brick0/testvol 49152 0 Y 2429
Self-heal Daemon on localhost N/A N/A Y 2420
Self-heal Daemon on dhcp37-193.lab.eng.blr.
redhat.com N/A N/A Y 17979
Self-heal Daemon on dhcp37-163.lab.eng.blr.
redhat.com N/A N/A Y 17868
Task Status of Volume testvol
------------------------------------------------------------------------------
There are no active volume tasks
Created attachment 1430644 [details] Brick is offline Description of problem: Bricks are in the offline state when glusterd is started when NIC is down Version-Release number of selected component (if applicable): 3.12.2-8 How reproducible: 2/2 Steps to Reproduce: 1. Created and started a replica volume X3 2. Stop glusterd on node 3. Bring down the NIC( ifdown <interface>) where glusterd is stopped. 4. Start glusterd Actual results: glusterd is up and running, glusterfsd is NA and seen NFS daemon Expected results: glusterd, glusterfsd and glustershd should be running Additional info: Once the nic is up, brick on one node is offline where we brought down the NIC gluster vol status Status of volume: testvol Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.37.193:/bricks/brick0/testvol 49155 0 Y 17871 Brick 10.70.37.163:/bricks/brick0/testvol 49155 0 Y 17797 Brick 10.70.37.67:/bricks/brick0/testvol N/A N/A N N/A Self-heal Daemon on localhost N/A N/A Y 3270 Self-heal Daemon on dhcp37-193.lab.eng.blr. redhat.com N/A N/A Y 17979 Self-heal Daemon on dhcp37-163.lab.eng.blr. redhat.com N/A N/A Y 17868 Task Status of Volume testvol ------------------------------------------------------------------------------ There are no active volume tasks After reboot, all bricks are online gluster vo status Status of volume: testvol Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.37.193:/bricks/brick0/testvol 49155 0 Y 17871 Brick 10.70.37.163:/bricks/brick0/testvol 49155 0 Y 17797 Brick 10.70.37.67:/bricks/brick0/testvol 49152 0 Y 2429 Self-heal Daemon on localhost N/A N/A Y 2420 Self-heal Daemon on dhcp37-193.lab.eng.blr. redhat.com N/A N/A Y 17979 Self-heal Daemon on dhcp37-163.lab.eng.blr. redhat.com N/A N/A Y 17868 Task Status of Volume testvol ------------------------------------------------------------------------------ There are no active volume tasks