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.
Bug 1001628 - virsh ignores --log option
Summary: virsh ignores --log option
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Kletzander
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-27 12:29 UTC by Ján Tomko
Modified: 2014-06-18 00:54 UTC (History)
7 users (show)

Fixed In Version: libvirt-1.1.1-3.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 10:42:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ján Tomko 2013-08-27 12:29:13 UTC
Description of problem:
virsh doesn't log into a file despite the --log option being specified

Version-Release number of selected component (if applicable):
libvirt-client-1.1.1-2.el7

How reproducible:
101.80 %


Steps to Reproduce:
virsh -l logfile start domain404
error: failed to get domain 'domain404'
error: Domain not found: no domain with matching name 'domain404'


Actual results:
# cat logfile
cat: logfile: No such file or directory


Expected results:
# cat logfile
[2013.08.27 08:23:21 virsh 795] ERROR failed to get domain 'domain404'
[2013.08.27 08:23:21 virsh 795] ERROR Domain not found: no domain with matching name 'domain404'


Additional info:
Logging to files specified by the VIRSH_LOG_FILE environment variable works.
Introduced by:
commit abfff210060625af8914e28601f1ec6ed96b05ae
Author:     Martin Kletzander <mkletzan>
AuthorDate: 2013-03-13 09:03:34 +0100

    Make vshDebug work when parsing parameters
git describe: v1.0.3-78-gabfff21 contains: v1.0.4-rc1~85

Comment 2 Martin Kletzander 2013-08-27 12:34:20 UTC
This issue is already being fixed on upstream.

Comment 3 Martin Kletzander 2013-08-28 09:15:46 UTC
Fixed upstream with v1.1.1-247-gac43da7:

commit ac43da705f0e7c23dffd87c0705ff01711b88ac0
Author: Martin Kletzander <mkletzan>
Date:   Tue Aug 27 13:19:24 2013 +0200

    virsh: Fix debugging

Comment 6 Hao Liu 2013-09-02 06:52:50 UTC
Verified this fix.

Packages:
libvirt-client-1.1.1-3.el7.x86_64

Verify steps:
1. Run virsh cmd with log file.
# virsh -l logfile start domain404
error: failed to get domain 'domain404'
error: Domain not found: no domain with matching name 'domain404'

2. Check log file.
# cat logfile
[2013.09.02 14:49:17 virsh 5301] ERROR failed to get domain 'domain404'
[2013.09.02 14:49:17 virsh 5301] ERROR Domain not found: no domain with matching name 'domain404'

Comment 7 Ludek Smid 2014-06-13 10:42:59 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.