You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kishan Kavala (JIRA)" <ji...@apache.org> on 2014/09/08 14:39:28 UTC
[jira] [Commented] (CLOUDSTACK-7497) [LXC][UI] deploy VM failing
as hypervisor type passed is KVM instead of LXC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125461#comment-14125461 ]
Kishan Kavala commented on CLOUDSTACK-7497:
-------------------------------------------
This is not specific to LXC.
UI issue in mixed hypervisor setup.
> [LXC][UI] deploy VM failing as hypervisor type passed is KVM instead of LXC
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7497
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7497
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Affects Versions: 4.5.0
> Reporter: shweta agarwal
> Assignee: Kishan Kavala
> Priority: Blocker
> Fix For: 4.5.0
>
>
> Repro steps:
> Create a LXC zone with 2 cluster one LXc and one KVM
> Create VM with LXC template
> Bug:
> Deploy vm fails as hypervisor type is passed as KVM
> 014-09-05 14:06:09,520 DEBUG [c.c.a.ApiServlet] (catalina-exec-8:ctx-7b5dcb24) ===START=== 10.146.0.131 -- GET command=deployVirtualMachine&response=json&sessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3D&zoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82a&templateid=2175190d-212a-4078-aedb-d25e4ddcdeb3&hypervisor=KVM&serviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810b&affinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47&iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48&_=1409906169711
> 2014-09-05 14:06:09,581 INFO [c.c.a.ApiServer] (catalina-exec-8:ctx-7b5dcb24 ctx-2a5b99cd) Hypervisor passed to the deployVm call, is different from the hypervisor type of the template
> 2014-09-05 14:06:09,582 DEBUG [c.c.a.ApiServlet] (catalina-exec-8:ctx-7b5dcb24 ctx-2a5b99cd) ===END=== 10.146.0.131 -- GET command=deployVirtualMachine&response=json&sessionkey=NZyAJuyUuohCrPbjervw1hkdBlM%3D&zoneid=7d97ec72-39c7-4fbc-b6f3-7710ada1a82a&templateid=2175190d-212a-4078-aedb-d25e4ddcdeb3&hypervisor=KVM&serviceofferingid=82ab5842-2a12-4160-bba4-4b2ff81e810b&affinitygroupids=345511d9-fa5f-46e8-b101-1d4ea0a1ba47&iptonetworklist%5B0%5D.networkid=04bf986a-ac13-4eaf-84e9-e99dcf508c48&_=1409906169711
> 2014-09-05 14:06:12,573 DEBUG [o.a.c.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-6de2885c) Zone 2 is ready to launch secondary storage VM
> 2014-09-05 14:06:12,689 DEBUG [c.c.c.ConsoleProxyManagerImpl] (consoleproxy-1:ctx-a134b2b7) Zone 2 is ready to launch console proxy
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)