Bug 1330176

Summary: Each 'virt-top' exit/stop logs a message in /var/log/messages
Product: Red Hat Enterprise Linux 7 Reporter: Chetan Nagarkar <cnagarka>
Component: virt-topAssignee: Richard W.M. Jones <rjones>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: cnagarka, cww, juzhou, mxie, mzhan, tzheng, xiaodwan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-27 21:29:16 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:
Bug Depends On:    
Bug Blocks: 1420851    

Description Chetan Nagarkar 2016-04-25 14:19:16 UTC 
Description of problem:

Each 'virt-top' exit/stop logs a message in /var/log/messages. Error message as below,
"End of file while reading data: Input/output error"



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

How reproducible:

100%

Steps to Reproduce:
1. Run "Virt-top"
2. exit it with either 'q' or "Ctrl + C"

Actual results:

In /var/log/messages, Error logged as "End of file while reading data: Input/output error" each and every successful run of "virt-top"

Expected results:
No logs should be generated after every interruption or clean exit.

Additional info:

Case no: 01622013
Account Name: Wake County Public Schools
Customer reported this bug as not harmful but need attention as 'virt-top' running every 5 minutes in their application and creating the additional log lines in messages.
Comment 1 Richard W.M. Jones 2016-04-25 14:29:47 UTC 
Indeed, I can reproduce this as well.  It seems harmless as you say,
but it should be doing it!
Comment 3 Richard W.M. Jones 2016-07-06 10:34:56 UTC 
virt-top is not on the Approved Components List for RHEL 7.3, so
I cannot fix this at this time.
Comment 4 Richard W.M. Jones 2017-03-28 13:47:49 UTC 
Moving to RHEL 7.5 as this bug is cosmetic.