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:
When VDO a VDO volume is started the operating mode should be logged.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. Create VDO volume
2. Check logs for operating mode normal
Actual results:
Nothing about the state of VDO is logged on startup of a volume
Expected results:
VDO should log what state the volume is in
vdo[942]: VDO instance 0 volume operating mode: {normal|recovering|read-only}
Additional info:
Tested on:
RHEL-7.6-20180626.0
kernel-3.10.0-915.el7
kmod-vdo-6.1.1.99-1.el7
vdo-6.1.1.99-2.el7
There is new line when VDO is started in /var/log/messages:
kvdo13:journalQ: VDO commencing normal operation
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
Description of problem: When VDO a VDO volume is started the operating mode should be logged. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create VDO volume 2. Check logs for operating mode normal Actual results: Nothing about the state of VDO is logged on startup of a volume Expected results: VDO should log what state the volume is in vdo[942]: VDO instance 0 volume operating mode: {normal|recovering|read-only} Additional info: