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.

Description of problem:

VDO ansible module should have no mentions of --readCache. For more details on --readCache removal see BZ 1639792.

Version-Release number of selected component (if applicable):
vdo-6.2.0.293-10.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1.grep -R readCache /usr/share/doc/vdo
2.grep -R "read cache" /usr/share/doc/vdo

Actual results:
# grep -R readCache /usr/share/doc/vdo
/usr/share/doc/vdo/examples/ansible/vdo.py:        options.append("--readCache=enabled")
/usr/share/doc/vdo/examples/ansible/vdo.py:        options.append("--readCacheSize=" + params['readcachesize'])
# grep -R "read cache" /usr/share/doc/vdo
/usr/share/doc/vdo/examples/ansible/vdo.py:            - Enables or disables the read cache.  The default is
/usr/share/doc/vdo/examples/ansible/vdo.py:              'disabled'.  Choosing 'enabled' enables a read cache
/usr/share/doc/vdo/examples/ansible/vdo.py:            - Specifies the extra VDO device read cache size in
/usr/share/doc/vdo/examples/ansible/vdo.py:              with 4 bio threads will have a read cache memory usage
/usr/share/doc/vdo/examples/ansible/vdo.py:              overhead of 4.5 MB per 1 MB of read cache specified).

Expected results:
nothing

Additional info:

The design of the VDO Ansible module is to be able to work with multiple versions of VDO, which may remove non-required options.

In the case of the "--readCache" and "--readCacheSize" options, if the playbook specifies these options, VDO on RHEL 8 would return the error "vdo create: error: unrecognized arguments", with the arguments used.  This would be an indication to the user that the version of VDO does not support the "--readCache" or "--readCacheSize" options.

The above would be a more consistent and informative failure mode for the user

The VDO Ansible module has been a part of upstream Ansible since version 2.5.

BZ 1669534 calls for the removal of the "vdo.py" Ansible module from the VDO package, which satisfies the removal of the "--readCache" option as stated above.

Closing this BZ as a duplicate.

*** This bug has been marked as a duplicate of bug 1669534 ***