Bug 1856595

Summary: Failed to create VDO enabled volume with Day2 operation
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: gluster-ansibleAssignee: Prajith <pkesavap>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: godas, pkesavap, pprakash, puebele, rhs-bugs, sabose, sasundar, sheggodu
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.5.z Async Update   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gluster-ansible-infra-1.0.4-12 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1856594 Environment:
Last Closed: 2020-11-24 12:37:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1856594    

Description SATHEESARAN 2020-07-14 03:15:47 UTC 
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.
Comment 1 SATHEESARAN 2020-07-14 03:25:48 UTC 
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
Comment 2 Prajith 2020-07-31 14:56:00 UTC 
https://github.com/gluster/gluster-ansible-infra/pull/105
Comment 3 Prajith 2020-08-05 07:16:57 UTC 
PR raised:-https://github.com/gluster/gluster-ansible-infra/pull/105

(moved to modified by mistake, the pr is not yet merged)
Comment 16 SATHEESARAN 2020-11-07 01:53:26 UTC 
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
Comment 20 errata-xmlrpc 2020-11-24 12:37:41 UTC 
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