[jira] [Comment Edited] (CLOUDSTACK-7501) System VM fails to move from one cluster to another cluster when hypervisor type differs

["Bharat Kumar (JIRA)" <ji...@apache.org>]

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

Bharat Kumar edited comment on CLOUDSTACK-7501 at 11/15/14 9:39 AM:
--------------------------------------------------------------------

if we do not mention any default hypervisor, Cloudstack tries to start a SSVM on different hypervisor after some retries. While creating a new SSVM vm we select the hypervisor type. If there is more than one hypervisor available for deployment we shuffle the list and pick one.

Note: In case of CPVM we do not do this unless the CPVM is destroyed.


was (Author: bharat.kumar):
if we do not mention any default hypervisor, Cloudstack tries to start a vm on different hypervisor after some retries. While creating a new system vm we select the hypervisor type. If there is more than one hypervisor available for deployment we shuffle the list and pick one.

> System VM fails to move from one cluster to another cluster when hypervisor type differs
> ----------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7501
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7501
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.5.0
>            Reporter: shweta agarwal
>            Assignee: Bharat Kumar
>            Priority: Critical
>             Fix For: 4.5.0
>
>         Attachments: Ms.tar.gz
>
>
> Repro steps:
> 1. Create a LXC advance zone setup with one LXC cluster 
> 2. When system vms are up .add one more KVM cluster
> 3. Put LXC host to maintenance
> Bug:
> System VM is not coming up on KVM  cluster
> Expected result:
> System VMs should come up on KVM cluster 
> Ms log shows :
> Cluster: 2 has HyperVisorType that does not match the VM, skipping this cluster
> which should not be the case in case of SSVM  and CPVM
> attaching MS logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)