Bug 1361478

Summary: Failed to resolve ipv6 address
Product: Red Hat Enterprise Linux 7 Reporter: Xiaodai Wang <xiaodwan>
Component: spice-gtkAssignee: Pavel Grunt <pgrunt>
Status: CLOSED ERRATA QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: juzhou, mxie, mzhan, pgrunt, rbalakri, tzheng
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: spice-gtk-0.31-5.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1362394 (view as bug list) Environment:
Last Closed: 2016-11-04 01:23:17 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:
Bug Depends On:    
Bug Blocks: 1362394    

Description Xiaodai Wang 2016-07-29 06:59:38 UTC
Description of problem:
Failed to resolve ipv6 address

Version-Release number of selected component (if applicable):
virt-viewer-2.0-11.el7.x86_64
spice-gtk-0.31-4.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a guest and make sure it's listen address is "::".
    <graphics type='spice' port='5900' autoport='yes' listen='0::0'>
      <listen type='address' address='0::0'/>
    </graphics>
2. Open the guest by remote-viewer.
$ remote-viewer spice://[::1]:5900

Actual results:
"Unable to connect to the graphic server spice://[::1]:5900" dialog pops up.
Error reseason is "Error resolving '[::1]': Name or service not known

Expected results:
The guest should be connected successfully.

Additional info:
This issue doesn't occur with spice-gtk-0.31-3.el7.x86_64

Comment 4 Pavel Grunt 2016-07-29 14:19:08 UTC
Fixed by: 5a301b201be77c0ece71640ba99e92733a93f950

Comment 8 errata-xmlrpc 2016-11-04 01:23:17 UTC
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-2016-2229.html