VISHAL PANDEY
VISHAL PANDEY
@rmadaka @atinmu I think GD1, shows similar behaviour for volume info. Although Volume Status should show the status of shd which is still not implemented in GD2.
@atinmu Will make the changes.
Gluster volume status output not consistent on gd2 pods, after delete/reboot of gd2 pod on gcs setup
@rmadaka Can you check GD2 logs once and paste it here ?
Gluster volume status output not consistent on gd2 pods, after delete/reboot of gd2 pod on gcs setup
@atinmu Not yet. I have not been able to give time to this issue. Will work on it.
@atinmu The validations are happening through that infra. Only thing is that we call RegisterClusterOpValidationFunc() to register these validation functions. We can add validations directly in clusterOptMap. But, since we...
@atinmu As per our discussion in the morning, I tried using ValidateBool () but its not possible as the validation function for cluster options expects a function with string arguments...
@atinmu The shd test is failing because max-bricks-per-process is still not merged and in all shd tests I am killing one of the bricks from volume, so if brick-multiplexing is...
@atinmu Still working on this. Stuck in an issue regarding local mount by glfsheal binary because of which the self heal tests are failing.
@atinmu No. I have asked @aravindavk for some help.
@PrasadDesala I will need more information than just volume status as there could be numerous reasons as to why the Port shows as 0. One of them could be that...