Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1669534

Summary: Remove Ansible module from VDO package
Product: Red Hat Enterprise Linux 8 Reporter: Dennis Keefe <dkeefe>
Component: vdoAssignee: Bryan Gurney <bgurney>
Status: CLOSED ERRATA QA Contact: vdo-qe
Severity: low Docs Contact: Marek Suchánek <msuchane>
Priority: unspecified    
Version: 8.1CC: awalsh, bgurney, rhandlin
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 6.2.1.20 Doc Type: Enhancement
Doc Text:
.The VDO Ansible module has been moved to Ansible packages Previously, the VDO Ansible module was provided by the `vdo` RPM package. Starting with this release, the module is provided by the `ansible` package instead. The original location of the VDO Ansible module file was: ---- /usr/share/doc/vdo/examples/ansible/vdo.py ---- The new location of the file is: ---- /usr/lib/python3.6/site-packages/ansible/modules/system/vdo.py ---- The `vdo` package continues to distribute Ansible playbooks. For more information on Ansible, see link:http://docs.ansible.com/[].
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:12:27 UTC Type: Bug
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: 1682564    
Bug Blocks:    

Description Dennis Keefe 2019-01-25 15:08:34 UTC
Description of problem:
VDO Ansible module is now in Ansible RPM.  Users should use the VDO Ansible module from the Ansible RPM instead of from the VDO RPM.  The VDO Ansible module should be removed from VDO's RPM  

files to be removed:
/usr/share/doc/vdo/examples/ansible/vdo.py
/usr/share/doc/vdo/examples/ansible/vdo.pyc
/usr/share/doc/vdo/examples/ansible/vdo.pyo

The Ansible directory also has playbooks, which are useful, so these can stay in the directory as a reference.


Files to keep:
/usr/share/doc/vdo/examples/ansible/test_vdocreate.yml
/usr/share/doc/vdo/examples/ansible/test_vdocreate_alloptions.yml
/usr/share/doc/vdo/examples/ansible/test_vdoremove.yml

Comment 1 Bryan Gurney 2019-03-18 17:56:01 UTC
The README.txt file will remain in the directory, with the following header:

----
This directory contains example playbooks for the "vdo" module in Ansible,
which can be used to create and remove VDO volumes, modify configuration
options, and start and stop VDO volumes.

The Ansible "vdo" module can be found in Ansible, version 2.5 or greater.
General information on Ansible can be found at http://docs.ansible.com/
----

Comment 2 Bryan Gurney 2019-03-18 18:00:18 UTC
*** Bug 1663259 has been marked as a duplicate of this bug. ***

Comment 10 Jakub Krysl 2019-07-25 12:48:44 UTC
vdo-6.2.1.102-11.el8.x86_64

# rpm -ql vdo | grep ansible
/usr/share/doc/vdo/examples/ansible
/usr/share/doc/vdo/examples/ansible/README.txt
/usr/share/doc/vdo/examples/ansible/test_vdocreate.yml
/usr/share/doc/vdo/examples/ansible/test_vdocreate_alloptions.yml
/usr/share/doc/vdo/examples/ansible/test_vdoremove.yml

# cat /usr/share/doc/vdo/examples/ansible/README.txt
This directory contains example playbooks for the "vdo" module in Ansible,
which can be used to create and remove VDO volumes, modify configuration
options, and start and stop VDO volumes.

The Ansible "vdo" module can be found in Ansible, version 2.5 or greater.
General information on Ansible can be found at http://docs.ansible.com/

To run a playbook:

1. On the control system, set up a passwordless SSH session via the
   "ssh-agent bash" and "ssh-add" commands.

2. Specify the managed hosts and groups by adding them to the
   /etc/ansible/hosts file on the control system.

3. Using the "hosts" value, construct a playbook detailing the desired state
   of the VDO volume.

4. When ready, execute "ansible-playbook <playbook.yml>".  For additional
   diagnostic output, run "ansible-playbook <playbook.yml> -vvvv".


VDO rpm no longer provides any .py ansible modules, only playbooks.

Comment 14 errata-xmlrpc 2019-11-05 22:12:27 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, 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-2019:3548