You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/23 12:06:46 UTC
[jira] [Commented] (CLOUDSTACK-4572) findHostsForMigration API does
not return correct host list
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069517#comment-15069517 ]
ASF GitHub Bot commented on CLOUDSTACK-4572:
--------------------------------------------
GitHub user anshul1886 opened a pull request:
https://github.com/apache/cloudstack/pull/1283
CLOUDSTACK-4572: findHostsForMigration API does not return correct host list
https://issues.apache.org/jira/browse/CLOUDSTACK-4572
Fix is missing in recent releases.
The api should return the list of suitable/unsuitable hosts
Added fix that creates a deep copy of the the variable allHosts and prevents faulty host list return.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-4572
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1283.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1283
----
commit 2cea4d42510230a61c2858ce5789b199cbc6398b
Author: Saksham Srivastava <sa...@citrix.com>
Date: 2013-08-30T19:30:41Z
CLOUDSTACK-4572: findHostsForMigration API does not return correct host list
Changes:
Expected behavior:
The api should return the list of suitable/unsuitable hosts
Added fix that creates a deep copy of the the variable allHosts and prevents faulty host list return.
----
> findHostsForMigration API does not return correct host list
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-4572
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4572
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.2.0
> Reporter: Saksham Srivastava
> Assignee: Anshul Gangwar
> Fix For: 4.2.1, 4.8.0
>
>
> Create multi cluster setup.
> Tag host in one cluster with host tag t1.
> Create a service offering using the host tag t1
> Deploy a vm using the tagged service offering.
> Even if tagged/untagged hosts are available across different clusters the api does not list correct hosts for migration for the deployed vm.
> Expected behavior:
> The api should return the list of suitable/unsuitable hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)