Red Hat Bugzilla – Bug 1366203
set volume options before starting the volume
Last modified: 2017-03-07 12:45:40 EST
Description of problem: ----------------------- When the volume section is mentioned in the gdeploy conf file along with the set of volume options, volume is actually started and then those options are set on the volume. Its a good practice to set the list of volume options on the volume and then to start the volume. Version-Release number of selected component (if applicable): ------------------------------------------------------------- gdeploy-2.0-16 How reproducible: ----------------- NA Steps to Reproduce: ------------------- NA Actual results: --------------- volume is started and then the options are set on the volume Expected results: ----------------- volume options should be set on the volume and then the volume should be started
This is hard requirement for setting up SSL/TLS configuration on the volume.
Commit: https://github.com/gluster/gdeploy/commit/405025b8c0 resolves the issue. This bug was fixed as part of resolving github issue. Should be available in the latest build. 2.0.1-2
Tested with ansible-2.2 and gdeploy-2.0.1-2.el7rhgs Volume options are first set on the volume and then the volume is started. Here is snip from the logs to prove the same <snip> TASK [Sets options for volume] ************************************************* changed: [host1.example.com] => (item={u'key': u'group', u'value': u'virt'}) PLAY RECAP ********************************************************************* dhcp37-172.lab.eng.blr.redhat.com : ok=1 changed=1 unreachable=0 failed=0 PLAY [master] ****************************************************************** TASK [Starts a volume] ********************************************************* changed: [host1.example.com] </snip>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0260.html