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:
After having created a VDO volume via the VDO Ansible module, if a playbook with a different "blockmapcachesize" value is executed with "ansible-playbook <blockmapcacheexpand_playbook>", where the "blockmapcacheexpand_playbook" file contains the line "blockmapcachesize:" with a size different from the currently configured size.
Version-Release number of selected component (if applicable):
Found in the version of the Ansible module from 6.1.0.98, after having applied the (still pending at this time) fixes from BZ 1536214, BZ 1536522, BZ 1536635, and BZ 1536564.
How reproducible:
100%
Steps to Reproduce:
1. Execute ansible-playbook against the target host with a playbook containing the following "vdo" section, to create a VDO volume on device /dev/md0:
- name: Create VDO volume vdo1
vdo:
name: vdo1
state: present
device: /dev/md0
logicalsize: 2T
2. Execute ansible-playbook against the same target host with a playbook containing the following "vdo" section, to modify the existing VDO volume "vdo1":
- name: Create VDO volume vdo1
vdo:
name: vdo1
state: present
device: /dev/md0
logicalsize: 2T
blockmapcachesize: 5G
Actual results:
The play finishes with status "ok" and "changed=0". The VDO volume retains its previous block map cache setting (the default is 128M).
Expected results:
The play finishes with status "ok" and "changed=1". The VDO volume updates its configuration to the new block map cache setting (so long as it is possible in the current configuration).
Additional info:
To clarify the description: if a playbook is executed that would ideally modify the block map cache size, it would result in no change. Ideally, this should result in a change.
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-2018:3094