Bug 912021

Summary:	spelling issue in error message from virt-top when libvirtd is stopped
Product:	Red Hat Enterprise Linux 7	Reporter:	tingting zheng <tzheng>
Component:	libvirt	Assignee:	Gunannan Ren <gren>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.0	CC:	acathrow, cwei, dallan, dyuan, lcui, mjenner, mzhan, ydu
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libvirt-1.0.3-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 12:28:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.