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 1838314

Summary:	Enhance vdo status to show pending changes [RFE]
Product:	Red Hat Enterprise Linux 8	Reporter:	Susan LeGendre-McGhee <slegendr>
Component:	vdo	Assignee:	Susan LeGendre-McGhee <slegendr>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:	Marek Suchánek <msuchane>
Priority:	unspecified
Version:	8.3	CC:	awalsh, fsuba, slegendr
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	6.2.4.4	Doc Type:	Enhancement
Doc Text:	Suggested text: The output of `vdo status` is now able to reflect changes that are pending, but not yet active on the VDO volume.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-18 14:39:44 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:

Description Susan LeGendre-McGhee 2020-05-20 21:07:51 UTC

Description of problem:
vdo status does not show pending changes from vdo modify that will take effect when the vdo volume is restarted.  

Version-Release number of selected component (if applicable):

How reproducible: 100%


Steps to Reproduce:
1. Create a VDO device
2. Run vdo status to see the initial configuration
3. Modify one or more parameters using vdo modify
4. Run vdo status again

Actual results:

vdo status shows the current device configuration

Expected results:

vdo status shows the current device configuration, along with pending modifications

Additional info:

Comment 2 Susan LeGendre-McGhee 2020-07-14 19:07:55 UTC

In order to prevent breaking anything that relies on parsing the output of 'vdo status' in its current format, I am thinking that this will need to be implemented as an option to the status command. If anyone has an alternate suggestion, please let me know.

Comment 4 Susan LeGendre-McGhee 2020-08-31 15:28:55 UTC

The new option to the 'vdo status' command is '--pending'. Pending modifications will only be shown for modifiable parameters of running VDO volumes that are permitted to be modified while the volume is running. Pending modifications are denoted with square brackets in the status output.

Comment 8 Filip Suba 2020-10-20 08:36:54 UTC

Verified with vdo-6.2.4.14-14.el8.

# vdo status --pending
...
VDOs:
  VDO:
    Acknowledgement threads: 1
    Activate: enabled
    Bio rotation interval: 64
    Bio submission threads: 4
    Block map cache size: 128M
    Block map period: 16380
    Block size: 4096
    CPU-work threads: 2    [4]
    Compression: enabled
    Configured write policy: auto
    Deduplication: enabled
...

Comment 10 errata-xmlrpc 2021-05-18 14:39:44 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 (kmod-kvdo 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-2021:1588