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:
The virt-who debugging message will output on TUI.
Version-Release number of selected component (if applicable):
rhev-hypervisor 6.3-20120815.0.el6_3
How reproducible:
100%
Steps to Reproduce:
1. Install the rhev-hypervisor 6.3-20120815.0.el6_3 on one machine in virtlab like dell-pet105-01 or other.
2. Rigister the host to sam and rhevm.then install at least one guest vm on the host.
3. Configure the virt-who on the host.
# vi /etc/sysconfig/virt-who
VIRTWHO_BACKGROUND=1
VIRTWHO_DEBUG=1
VIRTWHO_INTERVAL=2
4. Restart the virt-who service on the host.
5. Drop to the TUI and check the TUI.
actual result:.
The debugging message will be output in the TUI.
expect result:
In TUI there should be no debugging message.
Additional info:
I have check it on rhev-hypervisor 6.3 20120426.0.l6_3,it has the same result.
Closing as notabug
1. We don't support dropping to a shell and editing files manually
2. You're enabling debugging which is off by default. Adding this causes the output to go to stdout which is displayed. If this is a bug, then it's a bug that virt-who debugging goes to stdout.
Description of problem: The virt-who debugging message will output on TUI. Version-Release number of selected component (if applicable): rhev-hypervisor 6.3-20120815.0.el6_3 How reproducible: 100% Steps to Reproduce: 1. Install the rhev-hypervisor 6.3-20120815.0.el6_3 on one machine in virtlab like dell-pet105-01 or other. 2. Rigister the host to sam and rhevm.then install at least one guest vm on the host. 3. Configure the virt-who on the host. # vi /etc/sysconfig/virt-who VIRTWHO_BACKGROUND=1 VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=2 4. Restart the virt-who service on the host. 5. Drop to the TUI and check the TUI. actual result:. The debugging message will be output in the TUI. expect result: In TUI there should be no debugging message. Additional info: I have check it on rhev-hypervisor 6.3 20120426.0.l6_3,it has the same result.