Bug 873263

Summary: support raw ipv6 addresses in URIs
Product: Red Hat Enterprise Virtualization Manager Reporter: David Jaša <djasa>
Component: mingw-virt-viewerAssignee: Marc-Andre Lureau <marcandre.lureau>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: acathrow, berrange, cfergeau, dallan, dblechte, desktop-qa-list, djasa, dyasny, gkong, jbiddle, jwu, mkrcmari, mzhan, pvine, rwu, sgrinber, vehrlich, zpeng
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mingw-virt-viewer-0.5.3-18.el6ev Doc Type: Bug Fix
Doc Text:
Previously, due to parsing bugs, it was not possible to start remote-viewer from the command line with an IPv6 URI. Now, URIs containing IPv6 addresses are parsed correctly and starting remote-viewer from the command line is successful.
Story Points: ---
Clone Of: 813865 Environment:
Last Closed: 2013-06-10 19:58:57 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 David Jaša 2012-11-05 13:24:57 UTC
Occurs on windows builds, too (all windows versions/archs)
mingw-virt-viewer-0.5.3-16
mingw-spice-gtk-0.12-9


+++ This bug was initially created as a clone of Bug #813865 +++

+++ This bug was initially created as a clone of Bug #813375 +++

Description of problem:
support ipv6 addresses on CLI. IPv6 passed via controller works.

Version-Release number of selected component (if applicable):
virt-viewer-0.5.2-4

How reproducible:
always

Steps to Reproduce:
try to connect to qemu over ipv6:
1. remote-viewer spice://ipv6_addr/?port=PORT
2. remote-viewer spice://[ipv6_addr]/?port=PORT
3.
  
Actual results:
none of above works

Expected results:
some of above works

Additional info:
when address is passed via controller, remote-viewer works

--- Additional comment from berrange on 2012-04-18 16:45:35 BST ---

The RFC compliant syntax would be the second example you give

>  remote-viewer spice://[ipv6_addr]/?port=PORT

I have confirmed that this is indeed broken for both SPICE and VNC. The VNC support can be fixed in virt-viewer itself. The SPICE fix needs to be done in SPICE-GTK

--- Additional comment from berrange on 2012-04-18 17:46:40 CEST ---

Proof of concept upstream patch:

http://lists.freedesktop.org/archives/spice-devel/2012-April/008769.html

--- Additional comment from berrange on 2012-04-19 16:58:17 CEST ---

Alternative patch now posted

http://lists.freedesktop.org/archives/spice-devel/2012-April/008808.html

--- Additional comment from acathrow on 2012-04-23 16:25:13 CEST ---

What's the driver for this being a blocker for 6.3?

--- Additional comment from berrange on 2012-04-23 16:29:10 CEST ---

AFAIK, IPv6 support was a requirement of any RHEL6 application, in this case we need spice-gtk to support it for virt-viewer, so that it can connect to an IPv6 enabled KVM host

--- Additional comment from berrange on 2012-04-23 18:54:29 CEST ---

New (hopefully final) version of upstream patch

http://lists.freedesktop.org/archives/spice-devel/2012-April/008833.html

--- Additional comment from berrange on 2012-04-24 11:54:01 CEST ---

Committed upstream in

commit 50add15ef69cde34346e11b5c91e1257cecb2696
Author: Daniel P. Berrange <berrange>
Date:   Thu Apr 19 11:12:09 2012 +0100

    Fix multiple problems with URI parsing

--- Additional comment from dblechte on 2012-05-22 17:15:42 CEST ---

moving to 6.4. Deadline is less than 24 hours from now. The patches were not approved upstream.

--- Additional comment from djasa on 2012-05-31 18:28:33 CEST ---

please take bug #827115 into account when looking at the patches.

Comment 2 Marc-Andre Lureau 2013-02-14 18:28:53 UTC
since it's in RHEL and we did a rebase, it should be fixed in RHEVM too, moving to MODIFIED (correct?)

Comment 12 errata-xmlrpc 2013-06-10 19:58:57 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.

http://rhn.redhat.com/errata/RHEA-2013-0889.html