Description of problem: ------------------------ Failure when creating VDO enabled gluster volume with day2 operation from web console. This is because the logic tries to restart all the VDO volumes and existing active VDO volumes can't be stopped. Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHHI-V 1.8 RHGS 3.5.2 gluster-ansible-infra-1.0.4-11.el8rhgs How reproducible: ----------------- Always Steps to Reproduce: -------------------- 1. Complete RHHI-V deployment 2. From web console create new volume with VDO enabled Actual results: --------------- Ansible playbook fails to stop all the VDO volumes Expected results: ----------------- Ansible playbook logic should stop only the newly created VDO volumes and start them --- Additional comment from RHEL Program Management on 2020-07-14 03:14:08 UTC --- This bug is automatically being proposed for RHHI-V 1.8 release at Red Hat Hyperconverged Infrastructure for Virtualization product, by setting the release flag 'rhiv‑1.8' to '?'. If this bug should be proposed for a different release, please manually change the proposed release flag.
The fix will be in the vdo_create.yml playbook under gluster-ansible-infra - '/etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vdo_create.yml' Existing ansible logic that restarts VDO volume <snip> - name: Restart all VDO volumes command: "vdo {{item}} -a" with_items: - stop - start </snip> This logic restarts all the VDO volumes. This works well for deployment time, as there won't any pre-existing VDO volumes, but it when it comes to day2 operation, there could be pre-existing VDO volume in the setup. so it is always safe to restart the VDO volume in the inventory file. The above code can be modified as: <modification> - name: Restart all VDO volumes shell: "vdo stop -n {{item.name}} && vdo start -n {{item.name}}" with_items: "{{ gluster_infra_vdo }}" </modification> This can be the workaround too
https://github.com/gluster/gluster-ansible-infra/pull/105
PR raised:-https://github.com/gluster/gluster-ansible-infra/pull/105 (moved to modified by mistake, the pr is not yet merged)
Tested with gluster-ansible-infra-1.0.4-15.el8rhgs Using day2 operation from web console, the new volume can be created with VDO enabled on the bricks
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 (gluster-ansible bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2020:5220