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:
The "vdo modify" command no longer accepts the "--writePolicy" parameter. This means that the user is unable to change the configured write policy of a VDO volume and stage the change for the next VDO volume restart.
(Note that the ability to change the write policy immediately is still available via the "vdo changeWritePolicy --name=<vdoname> --writePolicy=<policy>" command.)
Version-Release number of selected component (if applicable):
vdo-6.1.0.114-14.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create a VDO volume with "--name=vdo1" and default options (e.g.: auto write policy, etc.)
2. Execute "vdo modify --name=vdo1 --writePolicy=async
Actual results:
# vdo modify --name=vdo1 --writePolicy=async
usage: vdo modify [-h] (-a | -n <volume>) [--blockMapCacheSize <megabytes>]
[--blockMapPeriod <period>] [--readCache {disabled,enabled}]
[--readCacheSize <megabytes>]
[--vdoAckThreads <threadCount>]
[--vdoBioRotationInterval <ioCount>]
[--vdoBioThreads <threadCount>]
[--vdoCpuThreads <threadCount>]
[--vdoHashZoneThreads <threadCount>]
[--vdoLogicalThreads <threadCount>]
[--vdoPhysicalThreads <threadCount>] [-f <file>]
[--logfile <pathname>] [--verbose]
vdo modify: error: unrecognized arguments: --writePolicy=async
Expected results:
The configuration of the VDO volume "vdo1" is changed to "async" write policy.
Additional info:
The "vdo modify ... --writePolicy=<policy>" command is used by the VDO Ansible module to configure the write policy and stage it for the next restart (which the Ansible administrator can execute at will by executing a "vdo stop" playbook, followed by a "vdo start" playbook.)
Description of problem: The "vdo modify" command no longer accepts the "--writePolicy" parameter. This means that the user is unable to change the configured write policy of a VDO volume and stage the change for the next VDO volume restart. (Note that the ability to change the write policy immediately is still available via the "vdo changeWritePolicy --name=<vdoname> --writePolicy=<policy>" command.) Version-Release number of selected component (if applicable): vdo-6.1.0.114-14.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create a VDO volume with "--name=vdo1" and default options (e.g.: auto write policy, etc.) 2. Execute "vdo modify --name=vdo1 --writePolicy=async Actual results: # vdo modify --name=vdo1 --writePolicy=async usage: vdo modify [-h] (-a | -n <volume>) [--blockMapCacheSize <megabytes>] [--blockMapPeriod <period>] [--readCache {disabled,enabled}] [--readCacheSize <megabytes>] [--vdoAckThreads <threadCount>] [--vdoBioRotationInterval <ioCount>] [--vdoBioThreads <threadCount>] [--vdoCpuThreads <threadCount>] [--vdoHashZoneThreads <threadCount>] [--vdoLogicalThreads <threadCount>] [--vdoPhysicalThreads <threadCount>] [-f <file>] [--logfile <pathname>] [--verbose] vdo modify: error: unrecognized arguments: --writePolicy=async Expected results: The configuration of the VDO volume "vdo1" is changed to "async" write policy. Additional info: The "vdo modify ... --writePolicy=<policy>" command is used by the VDO Ansible module to configure the write policy and stage it for the next restart (which the Ansible administrator can execute at will by executing a "vdo stop" playbook, followed by a "vdo start" playbook.)