[
https://issues.apache.org/jira/browse/CLOUDSTACK-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070601#comment-15070601
]
ASF GitHub Bot commented on CLOUDSTACK-4572:
--------------------------------------------
Github user koushik-das commented on the pull request:
https://github.com/apache/cloudstack/pull/1283#issuecomment-167045587
@anshul1886 If the fix was added in 4.2, why it got missed out? Can you
check the history and update?
> 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)
