You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kiran Koneti (JIRA)" <ji...@apache.org> on 2013/07/05 13:33:48 UTC
[jira] [Created] (CLOUDSTACK-3382) Unable to Migrate VM's If the
hosts are implicitly or explicitly dedicated.
Kiran Koneti created CLOUDSTACK-3382:
----------------------------------------
Summary: Unable to Migrate VM's If the hosts are implicitly or explicitly dedicated.
Key: CLOUDSTACK-3382
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3382
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Install and Setup
Affects Versions: 4.2.0
Reporter: Kiran Koneti
Priority: Blocker
Fix For: 4.2.0
The details of the defect are as follows:
1)I have created a Advanced Zone setup with two hosts.
2)Then created a VM using the Strict Implicit for one account and created another VM with different account without using any dedication.
3)two VM's are created on two hosts available and one is implicitly dedicated host and other one is a shared host.
4)then tried to migrate the VM from one account to another and clicked on the UI option available.
Observed that the there is a popup saying no suitable host found.
But according to the FS of the Dedicated resources Zone/pod/cluster/host it says as below:
"Migration of VMs
1.If VM to be migrated is non-dedicated:
a.if destination host is implicitly or explicitly dedicated, migrate it to that host, but an alert is generated
b.if destination host is non-dedicated, migrate it to the destination host.
2.If VM to be migrated is dedicated
a.if destination host is implicitly or explicitly dedicated to the same account, migrate it to that host.
b.if destination host is implicitly or explicitly dedicated to different account, migrate it to that host, but an alert is generated
c.if destination host is non-dedicated, migrate it to that host but an alert is generated"
--
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