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.

In order to make it easier for the user to reference, all of the VDO utilities should implement a "--version" option.  This will help ensure that someone using the sources can keep things consistent on a deployment.

Also referenced: https://github.com/dm-vdo/vdo/issues/19

Mass migration to Filip.

*** Bug 1769549 has been marked as a duplicate of this bug. ***

Verified with vdo-6.2.2.117-13.el8.

# vdodmeventd --version
vdodmeventd version is: 6.2.2.117
# vdodumpconfig --version
vdodumpconfig version is: 6.2.2.117
# vdoforcerebuild --version
vdoforcerebuild version is: 6.2.2.117
# vdoformat --version
vdoformat version is: 6.2.2.117
# vdoreadonly --version
vdoreadonly version is: 6.2.2.117
# vdosetuuid --version
vdosetuuid version is: 6.2.2.117
# vdostats --version
133524.30
# vdo version
VDO version: 6.2.2.117

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-2020:1782