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 912021 - spelling issue in error message from virt-top when libvirtd is stopped
Summary: spelling issue in error message from virt-top when libvirtd is stopped
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Gunannan Ren
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-17 09:14 UTC by tingting zheng
Modified: 2014-06-18 07:19 UTC (History)
8 users (show)

Fixed In Version: libvirt-1.0.3-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:28:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description tingting zheng 2013-02-17 09:14:36 UTC 
Description of problem:
spelling issue in error message from virt-top when libvirtd is stopped

Version-Release number of selected component (if applicable):
libvirt-1.0.2-1.el7.x86_64
virt-top-1.0.8-3.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Stop libvirtd.
# service libvirtd status
libvirtd is stopped

2.Run virt-top.
# virt-top
libvir: XML-RPC error : Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory
libvirt: VIR_ERR_SYSTEM_ERROR: VIR_FROM_RPC: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory

Actual results:
Wrong spell error messages show:libvir: XML-RPC error
s/libvir/libvirt

Expected results:
# virt-top
libvirt: XML-RPC error : Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory

Additional info:
Comment 2 Gunannan Ren 2013-03-04 12:46:39 UTC 
patch sent out
https://www.redhat.com/archives/libvir-list/2013-March/msg00093.html
Comment 3 Gunannan Ren 2013-03-04 15:24:52 UTC 
commit b95c13cd33a85606ec920df455b8606a37a18a8c
Author: Guannan Ren <gren>
Date:   Mon Mar 4 20:38:18 2013 +0800

    util: use string libvirt to prefix error message instead of libvir
    
    BZ:https://bugzilla.redhat.com/show_bug.cgi?id=912021
    Without error handler set, virDefaultErrorFunc will be called, the
    error message is prefixed with "libvir:". It become a little better
    by using prefix "libvirt:" when working with upper application.
    
    For example:
    1, stop libvirtd daemon
    2, run virt-top.
    libvir: XML-RPC error : Failed to connect \
            socket to '/var/run/libvirt/libvirt-sock-ro': \
            No such file or directory
    libvirt: VIR_ERR_SYSTEM_ERROR: VIR_FROM_RPC: \
            Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': \
            No such file or directory
Comment 4 yanbing du 2013-03-06 09:51:58 UTC 
libvirt-1.0.3-1.el7.x86_64
1. stop libvirtd
2. 
# virt-top
libvirt: XML-RPC error : Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory
libvirt: VIR_ERR_SYSTEM_ERROR: VIR_FROM_RPC: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No such file or directory

Bug can VERIFIED.
Comment 5 Ludek Smid 2014-06-13 12:28:27 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.