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 1115809 - Error messages are not clearly enough during start a guest with source protocol='gluster'
Summary: Error messages are not clearly enough during start a guest with source protoc...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: 7.0
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-03 07:35 UTC by Luyao Huang
Modified: 2014-07-03 08:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-03 08:33:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Luyao Huang 2014-07-03 07:35:13 UTC 
Description of problem:
Error messages are not clearly enough during start a guest with source protocol='gluster',while the gulsterd service is stop, error messages are not clearly enough during starting a guest.And the error messages are so long and 
can't print complete.


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

How reproducible:
100%

Steps to Reproduce:

1)prepare a guest with gluster:
#vi test-gluster.xml
........
    <disk type='network' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source protocol='gluster' name='gluster-vol1/r6-qcow2.img'>
        <host transport='unix' socket='/var/run/gluster/glusterd.socket'/>
      </source>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>
.........

2)# virsh define test-gluster.xml
Domain r6-qcow2 defined from test-gluster.xml

3)checking on gluster server
# service glusterd status
glusterd is stopped

3)#virsh start r6-qcow2

Actual results:
[root@dhcp-66-71-72 ~]# virsh start r6-qcow2
error: Failed to start domain r6-qcow2
error: internal error: early end of file from monitor: possible problem:
[2014-07-02 05:57:20.101911] E [common-utils.c:222:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known)
[2014-07-02 05:57:20.102039] E [name.c:242:af_inet_client_get_remote_sockaddr] 0-gfapi: DNS resolution failed on host /var/run/gluster/glusterd.socket
[2014-07-02 05:57:20.102072] E [glfs-mgmt.c:696:mgmt_rpc_notify] 0-glfs-mgmt: failed to connect with remote-host: /var/run/gluster/glusterd.socket (Success)
qemu-kvm: -drive file=gluster+unix:///gluster-vol1/r6-qcow2.img?socket=/var/run/gluster/glusterd.socket,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: Gluster connection failed for server=/var/run/gluster/glusterd.socket port=0 volume=gluster-vol1 image=r6-qcow2.img transport=unix
qemu-kvm: -drive file=gluster+unix:///gluster-vol1/r6-qcow2.img?socket=/var/run/gluster/glusterd.socket,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image gluster+unix:///gluster-vol1/r6-qcow2.img?socket=/var/run/glust

Expected results:
Error message should be more useful and succinct,just like:
# virsh start r7
error: Failed to start domain r7
error: can not connect with the gluster server

Additional info:
Comment 2 Peter Krempa 2014-07-03 08:33:43 UTC 
We aim to provide as much useful data to the user as possible, thus changing the message to "can not connect with the gluster server" would be actually counter-productive.

The message you see is actually passed through from qemu so if you think it's too verbose please open a bug against qemu.

I'm closing this as NOTABUG as the message passthrough from qemu is actually a desired feature.
Note You need to log in before you can comment on or make changes to this bug.