Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@cloudstack.apache.org
Date: Fri, 22 Mar 2013 12:49:14 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12638422.1363913362686.34595.1363956554809@arcas>
In-Reply-To: <JIRA.12638422.1363913362686@arcas>
References: <JIRA.12638422.1363913362686@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-1772) the change in vnc listening
 port will cause live migration doesn't work
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610211#comment-13610211 ] 

ASF subversion and git services commented on CLOUDSTACK-1772:
-------------------------------------------------------------

Commit ff63854b4d827033758835dc38231574994ed518 in branch refs/heads/master from Chip Childers <chip.childers@gmail.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ff63854 ]

CLOUDSTACK-1772: revert bc94948e0604e0e5931759be3c3d3155e84686f6, doesn't specify vnc listening port, make live migration work

                
> the change in vnc listening port will cause live migration doesn't work
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1772
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1772
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.1.0, 4.2.0
>            Reporter: edison su
>            Assignee: edison su
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> Reported by Marcus: "To be clear, it doesn't break consoleproxy for me, but it breaks migration as wido mentions in his long first post. I think he intended to fix it with the new libvirt 0.5.0 bindings rather than roll back, but it didn't happen before the cut.  It should probably be rolled back on both 4.1 and master at this point, lest it be forgotten, and he can add it back in once we for certain have the new libvirt bindings and fix."
> So we revert the change made by Wido for 4.1, then waiting for libvirt java binding 0.5.0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira