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:
If virt-who is running, run virt-who with command line, it will show noice info in terminal side.

Version-Release number of selected component (if applicable):
virt-who-0.16-7.el6
subscription-manager-1.16.8-7.el6.x86_64
python-rhsm-1.16.6-1.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Make sure virt-who is running.
[root@dell-pesc440-01 virt-who.d]# service virt-who start
[root@dell-pesc440-01 virt-who.d]# service virt-who status
virt-who (pid  27312) is running...
2. Run virt-who with command line.
[root@dell-pesc440-01 virt-who.d]# virt-who -o -d --vdsm
2016-03-25 01:51:17,141 [virtwho.init INFO] MainProcess(27574):MainThread @virtwho.py:parseOptions:637 - Using reporter_id='dell-pesc440-01.rhts.eng.bos.redhat.com'
virt-who seems to be already running. If not, remove /var/run/virt-who.pid

Actual results:
It will show noisy info in terminal side
"2016-03-25 01:51:17,141 [virtwho.init INFO] MainProcess(27574):MainThread @virtwho.py:parseOptions:637 - Using reporter_id='dell-pesc440-01.rhts.eng.bos.redhat.com'"

Expected results:
It should only show info as the following:
"virt-who seems to be already running. If not, remove /var/run/virt-who.pid".

Additional info:

Fixed upstream:

https://github.com/virt-who/virt-who/commit/53ca0d97197f72c808a30113394993c7bd42560c

Fixed in virt-who-0.18-1.el6.

verified in virt-who-0.18-1.el6.


it only shows:
virt-who seems to be already running. If not, remove /var/run/virt-who.pid

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://rhn.redhat.com/errata/RHBA-2017-0675.html