Bug 1433287

Summary: Update generated gdeploy config file to restart glusterd post setting up systemd slice for glusterfs
Product: [oVirt] cockpit-ovirt Reporter: SATHEESARAN <sasundar>
Component: GdeployAssignee: Devyani Kota <dkota>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 0.10.7-0.0.15CC: bugs, sabose
Target Milestone: ovirt-4.1.2Flags: sasundar: ovirt-4.1?
sasundar: planning_ack?
rule-engine: devel_ack+
sasundar: testing_ack+
Target Release: 0.10.7-0.0.18   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-23 08:17:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1411323, 1447919    

Description SATHEESARAN 2017-03-17 10:18:47 UTC 
Description of problem:
-----------------------
The generated gdeploy config has the step to setup glusterfs slice. This works good in the case, when gluster-rpms were installed and then the slice was setup.

But in other cases, where glusterd is already running, it requires glusterd to be restarted for the slice setup to reflect.

So update the gdeploy config file to convert the action to 'restart' intead of 'start'

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
cockpit-ovirt-dashboard-0.10.7-0.0.15

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Initiate gluster deployment from cockpit
2. Review the generated gdeploy config file

Actual results:
---------------
glusterd is just started and so it doesn't restarts for slice configurations to come into effect

Expected results:
-----------------
glusterd should be restarted

Additional info:
-----------------
<existing_content>
  [service3]
  action=start
  service=glusterd
  slice_setup=yes
<existing_content>

<expected_content>
  [service3]
  action=restart
  service=glusterd
  slice_setup=yes
<expected_content>
Comment 1 SATHEESARAN 2017-03-20 07:06:34 UTC 
Kasturi has provided the information that the host deploy workflow restarts glusterd. But again, it would be safe to have the glusterd restarted post setting up slice.
Comment 2 SATHEESARAN 2017-05-19 14:35:23 UTC 
Tested with cockpit-ovirt-dashboard-0.10.7-0.0.18.el7ev

The generated gdeploy config file has a step to restart glusterd service post setting up slice