Hide Forgot
Description of problem: run net-dhcp-leases command in quiet mode cannot get any output Version-Release number of selected component (if applicable): libvirt-1.2.8-5.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.# virsh net-dhcp-leases default Expiry Time MAC address Protocol IP address Hostname Client ID or DUID ------------------------------------------------------------------------------------------------------------------- 2014-10-13 14:45:09 00:22:44:66:88:aa ipv4 192.168.122.48/24 - - 2.# virsh -q net-dhcp-leases default <------no output Actual results: run net-dhcp-leases command in quiet mode cannot get any output Expected results: # virsh -q net-dhcp-leases default 2014-10-13 14:45:09 00:22:44:66:88:aa ipv4 192.168.122.48/24 Additional info: from man virsh: -q, --quiet Avoid extra informational messages.
Send a patch to upstream: https://www.redhat.com/archives/libvir-list/2014-November/msg00002.html
Fixed upstream by: commit ff071bc8b29c5442a080be0cd367e82286bdbcd3 Author: Luyao Huang <lhuang> AuthorDate: 2014-11-01 18:41:20 +0800 Commit: Martin Kletzander <mkletzan> CommitDate: 2014-11-06 15:13:55 +0100 virsh: fix net-dhcp-leases no output in quiet mode When run net-dhcp-leases in quiet mode, cannot get any output. # virsh -q net-dhcp-leases default Signed-off-by: Luyao Huang <lhuang> git describe: v1.2.10-32-gff071bc contains: v1.2.11-rc1~271
Verify it as follows. Move its status to VERIFIED. # rpm -q libvirt libvirt-1.2.17-1.el7.x86_64 # virsh net-dhcp-leases default Expiry Time MAC address Protocol IP address Hostname Client ID or DUID ------------------------------------------------------------------------------------------------------------------- 2015-07-06 16:26:07 52:54:00:68:ce:60 ipv4 192.168.122.104/24 - - # virsh -q net-dhcp-leases default 2015-07-06 16:26:07 52:54:00:68:ce:60 ipv4 192.168.122.104/24 - - # virsh --quiet net-dhcp-leases default 2015-07-06 16:26:07 52:54:00:68:ce:60 ipv4 192.168.122.104/24 - -
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