[jira] [Assigned] (CLOUDSTACK-2107) Only scaling up memory(ram) in not triggering vm live migration ;Unable to scale vm due to Catch exception com.xensource.xenapi.Types$HostNotEnoughFreeMemory when s
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nitin Mehta reassigned CLOUDSTACK-2107:
---
Assignee: Nitin Mehta (was: Harikrishna Patnala)
Only scaling up memory(ram) in not triggering vm live migration ;Unable to
scale vm due to Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this operation
Key: CLOUDSTACK-2107
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2107
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: prashant kumar mishra
Assignee: Nitin Mehta
Priority: Critical
Fix For: 4.2.0
Attachments: access_log.2013-04-19.txt, apilog.log, catalina.out,
management-server.log, RamScaleUp.png
For cpu scalup ,vms getting live migrated to other host in cluster if no
resources are available on current host ,but not in case of RAM Scaleup
Steps to reproduce
1-Create zone-pod-cluster with one host
2-Deploy vm so that no resource left on host
3-Add another host in same cluster
4- Try to scale up vm's ram (in new service offering keep cpu speed same as
previous ,increase ram by 500 MB)
Expected
--
since there is no resource left on current host vm should get live migrate to
other available host and scaleup should be successful .
Actual
-
scaleup failed due to not enough resource on current host,;CS did not try to
live migrate vm to other host on cluster
My observation
--
1-VM are getting live migrated in case of cpu scale up if current host does
not have resource
2-Tried to scaleup vm to service offering x failed but able to deploy a new
vm with same service offering
Service offering details
--
Tried to scaleup from SO 20 to SO 22
1-SO 22
mysql select * from service_offering_view where id=22 \G
*** 1. row ***
id: 22
uuid: 528443f5-f044-4e64-b1e1-87f6c0136921
name: smallcpu2ram
display_text: smallcpu2ram
created: 2013-04-18 18:48:17
tags: NULL
removed: NULL
use_local_storage: 0
system_use: 0
cpu: 1
speed: 1500
ram_size: 1024
nw_rate: NULL
mc_rate: NULL
ha_enabled: 0
limit_cpu_use: 0
host_tag: NULL
default_use: 0
vm_type: NULL
sort_key: 0
domain_id: NULL
domain_uuid: NULL
domain_name: NULL
domain_path: NULL
1 row in set (0.00 sec)
2-SO 20
mysql select * from service_offering_view where id=20 \G
*** 1. row ***
id: 20
uuid: 4bafd8c7-c8cc-42db-a630-61909556803b
name: smallcpu2
display_text: smallcpu2
created: 2013-04-18 18:39:59
tags: NULL
removed: NULL
use_local_storage: 0
system_use: 0
cpu: 1
speed: 1500
ram_size: 500
nw_rate: NULL
mc_rate: NULL
ha_enabled: 0
limit_cpu_use: 0
host_tag: NULL
default_use: 0
vm_type: NULL
sort_key: 5
domain_id: NULL
domain_uuid: NULL
domain_name: NULL
domain_path: NULL
1 row in set (0.00 sec)
Snippet of MS Log
---
2013-04-19 07:40:58,312 DEBUG [agent.transport.Request] (DirectAgent-12:null)
Seq 1-521863179: Processing: { Ans: , MgmtId: 7191687856187, via: 1, Ver:
v1, Flags: 110, [{ScaleVmAnswer:{result:false,details:Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this
operation,wait:0}}] }
2013-04-19 07:40:58,312 DEBUG [agent.transport.Request]
(catalina-exec-6:null) Seq 1-521863179: Received: { Ans: , MgmtId:
7191687856187, via: 1, Ver: v1, Flags: 110, { ScaleVmAnswer } }
2013-04-19 07:40:58,312 ERROR [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-6:null) Unable to scale vm due to Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this operation
2013-04-19 07:40:58,313 DEBUG
[jira] [Assigned] (CLOUDSTACK-2107) Only scaling up memory(ram) in not triggering vm live migration ;Unable to scale vm due to Catch exception com.xensource.xenapi.Types$HostNotEnoughFreeMemory when s
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala reassigned CLOUDSTACK-2107:
---
Assignee: Harikrishna Patnala
Only scaling up memory(ram) in not triggering vm live migration ;Unable to
scale vm due to Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this operation
Key: CLOUDSTACK-2107
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2107
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: prashant kumar mishra
Assignee: Harikrishna Patnala
Priority: Critical
Fix For: 4.2.0
Attachments: access_log.2013-04-19.txt, apilog.log, catalina.out,
management-server.log, RamScaleUp.png
For cpu scalup ,vms getting live migrated to other host in cluster if no
resources are available on current host ,but not in case of RAM Scaleup
Steps to reproduce
1-Create zone-pod-cluster with one host
2-Deploy vm so that no resource left on host
3-Add another host in same cluster
4- Try to scale up vm's ram (in new service offering keep cpu speed same as
previous ,increase ram by 500 MB)
Expected
--
since there is no resource left on current host vm should get live migrate to
other available host and scaleup should be successful .
Actual
-
scaleup failed due to not enough resource on current host,;CS did not try to
live migrate vm to other host on cluster
My observation
--
1-VM are getting live migrated in case of cpu scale up if current host does
not have resource
2-Tried to scaleup vm to service offering x failed but able to deploy a new
vm with same service offering
Service offering details
--
Tried to scaleup from SO 20 to SO 22
1-SO 22
mysql select * from service_offering_view where id=22 \G
*** 1. row ***
id: 22
uuid: 528443f5-f044-4e64-b1e1-87f6c0136921
name: smallcpu2ram
display_text: smallcpu2ram
created: 2013-04-18 18:48:17
tags: NULL
removed: NULL
use_local_storage: 0
system_use: 0
cpu: 1
speed: 1500
ram_size: 1024
nw_rate: NULL
mc_rate: NULL
ha_enabled: 0
limit_cpu_use: 0
host_tag: NULL
default_use: 0
vm_type: NULL
sort_key: 0
domain_id: NULL
domain_uuid: NULL
domain_name: NULL
domain_path: NULL
1 row in set (0.00 sec)
2-SO 20
mysql select * from service_offering_view where id=20 \G
*** 1. row ***
id: 20
uuid: 4bafd8c7-c8cc-42db-a630-61909556803b
name: smallcpu2
display_text: smallcpu2
created: 2013-04-18 18:39:59
tags: NULL
removed: NULL
use_local_storage: 0
system_use: 0
cpu: 1
speed: 1500
ram_size: 500
nw_rate: NULL
mc_rate: NULL
ha_enabled: 0
limit_cpu_use: 0
host_tag: NULL
default_use: 0
vm_type: NULL
sort_key: 5
domain_id: NULL
domain_uuid: NULL
domain_name: NULL
domain_path: NULL
1 row in set (0.00 sec)
Snippet of MS Log
---
2013-04-19 07:40:58,312 DEBUG [agent.transport.Request] (DirectAgent-12:null)
Seq 1-521863179: Processing: { Ans: , MgmtId: 7191687856187, via: 1, Ver:
v1, Flags: 110, [{ScaleVmAnswer:{result:false,details:Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this
operation,wait:0}}] }
2013-04-19 07:40:58,312 DEBUG [agent.transport.Request]
(catalina-exec-6:null) Seq 1-521863179: Received: { Ans: , MgmtId:
7191687856187, via: 1, Ver: v1, Flags: 110, { ScaleVmAnswer } }
2013-04-19 07:40:58,312 ERROR [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-6:null) Unable to scale vm due to Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this operation
2013-04-19 07:40:58,313 DEBUG
