Volume info not showing self heal daemon status for newly created volumes on gcs setup

[rmadaka]

Observed behavior

Volume Name: pvc-9e0f4b21-f162-11e8-86db-525400ba128f
Type: Replicate
Volume ID: b84f4c58-7b5a-4c40-9b59-014de1276781
State: Started
Capactiy:  10 PB
Transport-type: tcp
Options:
Number of Bricks: 3
Brick1: gluster-kube1-0.glusterd2.gcs:/var/run/glusterd2/bricks/pvc-9e0f4b21-f162-11e8-86db-525400ba128f/subvol1/brick1/brick
Brick2: gluster-kube3-0.glusterd2.gcs:/var/run/glusterd2/bricks/pvc-9e0f4b21-f162-11e8-86db-525400ba128f/subvol1/brick2/brick
Brick3: gluster-kube2-0.glusterd2.gcs:/var/run/glusterd2/bricks/pvc-9e0f4b21-f162-11e8-86db-525400ba128f/subvol1/brick3/brick

Note: Once we enable self-heal-daemon for first time, next time onward we are able to see the self-heal daemon status in volume info

Expected/desired behavior

Volume info should show the self-heal-daemon status for newly created volumes.

Details on how to reproduce (minimal and precise)

-> Create pvc -> Login to GD2 pod -> Then perform volume info. -> We will not able to see self-heal daemon status.

Information about the environment:

• Glusterd2 version used (e.g. v4.1.0 or master): v6.0-dev.39.git65dafcd
• Operating system used:
• Glusterd2 compiled from sources, as a package (rpm/deb), or container: container
• Using External ETCD: (yes/no, if yes ETCD version): yes
• If container, which container image:
• Using kubernetes, openshift, or direct install: kubernetes
• If kubernetes/openshift, is gluster running inside kubernetes/openshift or outside: inside

Other useful information

• glusterd2 config files from all nodes (default /etc/glusterd2/glusterd2.toml)
• glusterd2 log files from all nodes (default /var/log/glusterd2/glusterd2.log)
• ETCD configuration
• Contents of uuid.toml from all nodes (default /var/lib/glusterd2/uuid.toml)
• Output of statedump from any one of the node

Useful commands

• To get glusterd2 version

  glusterd2 --version
  

• To get ETCD version

  etcd --version
  

• To get output of statedump

  curl http://glusterd2-IP:glusterd2-Port/statedump
  

[vpandey-RH]

@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]

volume info doesn't need to however volume status has to. Please fix this.

@rmadaka did you actually mean volume status than info while filing the bug? If yes, then please change the title otherwise we don't need shd status in volume info apart from volume status.

[vpandey-RH]

@atinmu Will make the changes.

[atinmu]

Moving it out of GCS/1.0 as glustershd will not be enabled by default with 1.0 version.