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>
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.
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