Hide Forgot
Description of problem: After the HE deployment, in one of the host all the bricks are shown as down. But this isn't the actual case since the bricks are online during gluster volume show. Have attached the UI screenshot Version-Release number of selected component (if applicable): redhat-release-virtualization-host-4.2-3.0.el7.x86_64 glusterfs-3.12.2-8.el7rhgs.x86_64 How reproducible: Steps to Reproduce: 1.Complete HE deployment 2.Put the host to maintenance and later activate it 3.See the bricks down in UI Actual results: The bricks are showing up as down state Expected results: The bricks should return show online Additional info: Gluster volume status: [root@rhsqa-grafton7-nic2 glusterfs]# gluster volume status Status of volume: VDO_Test Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.45.29:/gluster_bricks/VDO_Test/ VDO_Test 49152 0 Y 3746 Brick 10.70.45.30:/gluster_bricks/VDO_Test/ VDO_Test 49152 0 Y 3756 Brick 10.70.45.31:/gluster_bricks/VDO_Test/ VDO_Test 49156 0 Y 48079 Self-heal Daemon on localhost N/A N/A Y 5044 Self-heal Daemon on rhsqa-grafton9.lab.eng. blr.redhat.com N/A N/A Y 52138 Self-heal Daemon on 10.70.45.30 N/A N/A Y 32637 Task Status of Volume VDO_Test ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: data Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.45.29:/gluster_bricks/data/data 49156 0 Y 5034 Brick 10.70.45.30:/gluster_bricks/data/data 49153 0 Y 27158 Brick 10.70.45.31:/gluster_bricks/data/data 49157 0 Y 48309 Self-heal Daemon on localhost N/A N/A Y 5044 Self-heal Daemon on rhsqa-grafton9.lab.eng. blr.redhat.com N/A N/A Y 52138 Self-heal Daemon on 10.70.45.30 N/A N/A Y 32637 Task Status of Volume data ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: engine Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.45.29:/gluster_bricks/engine/en gine 49155 0 Y 31307 Brick 10.70.45.30:/gluster_bricks/engine/en gine 49155 0 Y 29459 Brick 10.70.45.31:/gluster_bricks/engine/en gine 49152 0 Y 48597 Self-heal Daemon on localhost N/A N/A Y 5044 Self-heal Daemon on 10.70.45.30 N/A N/A Y 32637 Self-heal Daemon on rhsqa-grafton9.lab.eng. blr.redhat.com N/A N/A Y 52138 Task Status of Volume engine ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 10.70.45.29:/gluster_bricks/vmstore/v mstore 49154 0 Y 31146 Brick 10.70.45.30:/gluster_bricks/vmstore/v mstore 49154 0 Y 29393 Brick 10.70.45.31:/gluster_bricks/vmstore/v mstore 49158 0 Y 48567 Self-heal Daemon on localhost N/A N/A Y 5044 Self-heal Daemon on rhsqa-grafton9.lab.eng. blr.redhat.com N/A N/A Y 52138 Self-heal Daemon on 10.70.45.30 N/A N/A Y 32637 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks
Tested this on the version vdsm-4.20.29-1.el7ev.x86_64. Moving it to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3523