[Libfix] Change logic to restart glusterd

Problem:
bring_bricks_online() method uses direct
invocation of `service glusterd restart` at
line 212. However due to change in behaviour
of glusterd through patch [1] and [2] if
glusterd is restart more than 6 times in an
hour it goes into failed state which has to
be reset using the `systemctl rest-failed`
command. This causes a random failures as shown
below:
```
2020-08-25 18:00:51,600 INFO (run) root@rhs-vm24.blr.com (cp): service glusterd restart
2020-08-25 18:00:51,601 DEBUG (_get_ssh_connection) Retrieved connection from cache: root@rhs-vm24.blr.com
2020-08-25 18:00:51,830 INFO (_log_results) ^[[34;1mRETCODE (root@rhs-vm24.blr.com): 1^[[0m
2020-08-25 18:00:51,830 INFO (_log_results) ^[[31;1mSTDERR (root@rhs-vm24.blr.com)...
Redirecting to /bin/systemctl restart glusterd.service
Job for glusterd.service failed.
See "systemctl status glusterd.service" and "journalctl -xe" for details.
^[[0m
2020-08-25 18:00:51,830 ERROR (bring_bricks_online) Unable to restart glusterd on node rhs-vm24.blr.com
```

Fix:
Change the code to use restart_glusterd()
from gluster_init.

Links:
[1] https://review.gluster.org/#/c/glusterfs/+/23751/
[2] https://review.gluster.org/#/c/glusterfs/+/23970/

Change-Id: Ibe44463ac1d444f3d2155c9ae11680c9ffd8dab9
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>

0 files changed, 0 insertions, 0 deletions