[
https://issues.apache.org/jira/browse/CLOUDSTACK-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mice Xia resolved CLOUDSTACK-1852.
----------------------------------
Resolution: Fixed
[change]
ui/scripts/system.js: add 'Suitable' or 'Not Suitable' based on API response
'suitableformigration'
P.S: 4.1 may have the same problem from code perspective
> showing disconnected host as suitable target during system vms migration
> -------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1852
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1852
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: sadhu suresh
> Attachments: management-server.rar
>
>
> This issue applicable only to ssvm,cpvm and routervms and for normal
> guestvms CS shows correctly
> 1.setup advance zone with xen cluster
> 2 .add 2 hosts
> 3.deploy few VMs
> 4.put one of host into maintenance mode or put it in disconnect state
> 5.try to migrate Guest Vms
> 6.try to migrate systems including router
> Actual result:
> Step 5: during Guest Vs migrations CS shows host state correctly,i.e target
> is "not suitable "state.
> Step 6: For system vms,Cs shows target host is in "suitable state".due this
> to end user try to migrate system vms from one host another host and fails
> with exception.
> Expected result:
> It should discovers the host state correctly and update it correctly
> "suitable or Not suitable" during migration.
--
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
