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:
virsh domifaddr cannot get any output in quiet mode
Version-Release number of selected component (if applicable):
libvirt-1.2.14-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.prepare a running vm with agent:
# virsh list
Id Name State
----------------------------------------------------
6 test3 running
2.check output
# virsh domifaddr test3 --source agent
Name MAC address Protocol Address
-------------------------------------------------------------------------------
lo 00:00:00:00:00:00 ipv4 127.0.0.1/8
- - ipv6 ::1/128
ens8 52:54:00:1a:cb:3f ipv6 fe80::5054:ff:fe1a:cb3f/64
virbr0 52:54:00b:51:e7 ipv4 192.168.122.1/24
virbr0-nic 52:54:00b:51:e7 N/A N/A
3. heck quite model output
# virsh -q domifaddr test3 --source agent
Actual results:
virsh domifaddr cannot get any output in quiet mode
Expected results:
fix it
# virsh -q domifaddr test3 --source agent
lo 00:00:00:00:00:00 ipv4 127.0.0.1/8
- - ipv6 ::1/128
ens8 52:54:00:1a:cb:3f ipv6 fe80::5054:ff:fe1a:cb3f/64
virbr0 52:54:00b:51:e7 ipv4 192.168.122.1/24
virbr0-nic 52:54:00b:51:e7 N/A N/A
Additional info:
Upstream patch:
commit 156fde0b1a7d9421403401b837152990a900c88b
Author: Luyao Huang <lhuang>
Date: Fri Apr 3 17:41:03 2015 +0800
virsh: Fix domifaddr output in quiet mode
In virsh we have two printing functions: vshPrint() which prints a
string onto stdout and vshPrintExtra() which does not print anything
if virsh is run in quiet mode. Usually, the former is used to print
actual results, while the latter to print strings like table headers
and other formatting stuff. However, in cmdDomIfAddr we have
mistakenly used vshPrintExtra even for actual data. After this patch,
the output should look like the following:
# virsh -q domifaddr test3 --source agent
lo 00:00:00:00:00:00 ipv4 127.0.0.1/8
- - ipv6 ::1/128
ens8 52:54:00:1a:cb:3f ipv6 fe80::5054:ff:fe1a:cb3f/64
virbr0 52:54:00:db:51:e7 ipv4 192.168.122.1/24
virbr0-nic 52:54:00:db:51:e7 N/A N/A
v1.2.14-44-g156fde0
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-2015-2202.html
description of problem: virsh domifaddr cannot get any output in quiet mode Version-Release number of selected component (if applicable): libvirt-1.2.14-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.prepare a running vm with agent: # virsh list Id Name State ---------------------------------------------------- 6 test3 running 2.check output # virsh domifaddr test3 --source agent Name MAC address Protocol Address ------------------------------------------------------------------------------- lo 00:00:00:00:00:00 ipv4 127.0.0.1/8 - - ipv6 ::1/128 ens8 52:54:00:1a:cb:3f ipv6 fe80::5054:ff:fe1a:cb3f/64 virbr0 52:54:00b:51:e7 ipv4 192.168.122.1/24 virbr0-nic 52:54:00b:51:e7 N/A N/A 3. heck quite model output # virsh -q domifaddr test3 --source agent Actual results: virsh domifaddr cannot get any output in quiet mode Expected results: fix it # virsh -q domifaddr test3 --source agent lo 00:00:00:00:00:00 ipv4 127.0.0.1/8 - - ipv6 ::1/128 ens8 52:54:00:1a:cb:3f ipv6 fe80::5054:ff:fe1a:cb3f/64 virbr0 52:54:00b:51:e7 ipv4 192.168.122.1/24 virbr0-nic 52:54:00b:51:e7 N/A N/A Additional info: Upstream patch: commit 156fde0b1a7d9421403401b837152990a900c88b Author: Luyao Huang <lhuang> Date: Fri Apr 3 17:41:03 2015 +0800 virsh: Fix domifaddr output in quiet mode In virsh we have two printing functions: vshPrint() which prints a string onto stdout and vshPrintExtra() which does not print anything if virsh is run in quiet mode. Usually, the former is used to print actual results, while the latter to print strings like table headers and other formatting stuff. However, in cmdDomIfAddr we have mistakenly used vshPrintExtra even for actual data. After this patch, the output should look like the following: # virsh -q domifaddr test3 --source agent lo 00:00:00:00:00:00 ipv4 127.0.0.1/8 - - ipv6 ::1/128 ens8 52:54:00:1a:cb:3f ipv6 fe80::5054:ff:fe1a:cb3f/64 virbr0 52:54:00:db:51:e7 ipv4 192.168.122.1/24 virbr0-nic 52:54:00:db:51:e7 N/A N/A v1.2.14-44-g156fde0