Bug 1520988

Summary: [RFE] VDO Should Log Volume's Operating Mode When Started
Product: Red Hat Enterprise Linux 7 Reporter: Dennis Keefe <dkeefe>
Component: kmod-kvdoAssignee: corwin <corwin>
Status: CLOSED ERRATA QA Contact: Jakub Krysl <jkrysl>
Severity: low Docs Contact:
Priority: low    
Version: 7.5CC: awalsh, jkrysl, limershe, sweettea
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 6.1.1.88 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1548459 (view as bug list) Environment:
Last Closed: 2018-10-30 09:38:49 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:
Bug Depends On:    
Bug Blocks: 1546181, 1548459, 1654309    

Description Dennis Keefe 2017-12-05 15:19:01 UTC
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:

Comment 6 Jakub Krysl 2018-07-10 13:51:11 UTC
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

Comment 8 errata-xmlrpc 2018-10-30 09:38:49 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, 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