[jira] [Created] (CLOUDSTACK-3713) scaling up system vm is successful but UI popup message "Failed to scale vm"

prashant kumar mishra created CLOUDSTACK-3713: - Summary: scaling up system vm is successful but UI popup message "Failed to scale vm" Key: CLOUDSTACK-3713 URL: https://issues.apache.org/jira/browse/C

[jira] [Updated] (CLOUDSTACK-3712) unable to update service offerings of stopped system vms;com.cloud.exception.InvalidParameterValueException: unable to find a virtual machine with id 3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3712: -- Attachment: logs_db.rar > unable to update service offerings o

[jira] [Created] (CLOUDSTACK-3712) unable to update service offerings of stopped system vms;com.cloud.exception.InvalidParameterValueException: unable to find a virtual machine with id 3

prashant kumar mishra created CLOUDSTACK-3712: - Summary: unable to update service offerings of stopped system vms;com.cloud.exception.InvalidParameterValueException: unable to find a virtual machine with id 3 Key: CL

[jira] [Updated] (CLOUDSTACK-3703) change service offering of stopped vm on kvm is failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3703: -- Description: Steps to reproduce 1-pre

[jira] [Updated] (CLOUDSTACK-3703) change service offering of stopped vm on kvm is failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3703: -- Attachment: screenshot-1.jpg > change service offering of stop

[jira] [Updated] (CLOUDSTACK-3703) change service offering of stopped vm on kvm is failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3703: -- Attachment: Logs_DB.rar > change service offering of stopped v

[jira] [Created] (CLOUDSTACK-3703) change service offering of stopped vm on kvm is failing

prashant kumar mishra created CLOUDSTACK-3703: - Summary: change service offering of stopped vm on kvm is failing Key: CLOUDSTACK-3703 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3703

[jira] [Updated] (CLOUDSTACK-3664) scaling up vms is not considering parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3664: -- Description: steps to reproduce 1-prepare a CS se

[jira] [Updated] (CLOUDSTACK-3664) scaling up vms is not considering parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3664: -- Attachment: screenshot-1.jpg > scaling up vms is not consideri

[jira] [Updated] (CLOUDSTACK-3664) scaling up vms is not considering parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3664: -- Summary: scaling up vms is not considering parameter "cluster.(me

[jira] [Updated] (CLOUDSTACK-3664) scaling up vm is not considering cluster parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3664: -- Description: steps to reproduce 1-prepare a CS se

[jira] [Updated] (CLOUDSTACK-3664) scaling up vm is not considering cluster parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3664: -- Attachment: Logs_DB.rar > scaling up vm is not considering clu

[jira] [Created] (CLOUDSTACK-3664) scaling up vm is not considering cluster parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold"

prashant kumar mishra created CLOUDSTACK-3664: - Summary: scaling up vm is not considering cluster parameter "cluster.(memory/cpu).allocated.capacity.disablethreshold" Key: CLOUDSTACK-3664 URL: https:/

[jira] [Closed] (CLOUDSTACK-3551) scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling VM:

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-3551. - Assignee: (was: Harikrishna Patnala) tested on xen 6.1;passed

[jira] [Updated] (CLOUDSTACK-3637) system vm scaleup is failing on xen server ;Unable to Scale the vm: s-1-VMas vm does not have xs tools to support dynamic scaling

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3637: -- Attachment: Logs_db.rar > system vm scaleup is failing on xen

[jira] [Created] (CLOUDSTACK-3637) system vm scaleup is failing on xen server ;Unable to Scale the vm: s-1-VMas vm does not have xs tools to support dynamic scaling

prashant kumar mishra created CLOUDSTACK-3637: - Summary: system vm scaleup is failing on xen server ;Unable to Scale the vm: s-1-VMas vm does not have xs tools to support dynamic scaling Key: CLOUDSTACK-3637

[jira] [Commented] (CLOUDSTACK-3624) system vm scaleup is failing on vmware;java.lang.RuntimeException: Memory size after hot add must be at least 2048MB

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712171#comment-13712171 ] prashant kumar mishra commented on CLOUDSTACK-3624: --- Observation ==

[jira] [Updated] (CLOUDSTACK-3624) system vm scaleup is failing on vmware;java.lang.RuntimeException: Memory size after hot add must be at least 2048MB

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3624: -- Summary: system vm scaleup is failing on vmware;java.lang.RuntimeEx

[jira] [Updated] (CLOUDSTACK-3624) system vm scaleup is failing on vmware;ava.lang.RuntimeException: Memory size after hot add must be at least 2048MB

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3624: -- Attachment: Logs_DB.rar > system vm scaleup is failing on vmwa

[jira] [Created] (CLOUDSTACK-3624) system vm scaleup is failing on vmware;ava.lang.RuntimeException: Memory size after hot add must be at least 2048MB

prashant kumar mishra created CLOUDSTACK-3624: - Summary: system vm scaleup is failing on vmware;ava.lang.RuntimeException: Memory size after hot add must be at least 2048MB Key: CLOUDSTACK-3624 URL: h

[jira] [Closed] (CLOUDSTACK-2184) Failed to scale up number of vcpus;Only scaling up the vm is supported, new service offering should have both cpu and memory greater than the old values

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-2184. - tested on xen 6.1 ; = Tried scaling up from SO(CPU=1000

[jira] [Closed] (CLOUDSTACK-2181) Scale down is allowed when one resource(say cpu) is being scale up and other resource (say ram)is being scale down ;but not allowed when both resources are being sc

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-2181. - passed > Scale down is allowed when one resource(say

[jira] [Updated] (CLOUDSTACK-3551) scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3551: -- Priority: Blocker (was: Critical) > scaling up VM from small

[jira] [Closed] (CLOUDSTACK-2085) VM weight on xen remain same as before vmscaleup ;because "Add-To-VCPUs-Params-Live.sh" is not getting copied on xs host

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-2085. - passed > VM weight on xen remain same as before vmscale

[jira] [Updated] (CLOUDSTACK-3551) scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3551: -- Attachment: XEN_MS_DB.rar > scaling up VM from small SO to a S

[jira] [Created] (CLOUDSTACK-3551) scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling VM

prashant kumar mishra created CLOUDSTACK-3551: - Summary: scaling up VM from small SO to a SO (with 2 GB RAM) is failing ; Unable to scale vm due to Catch exception com.xensource.xenapi.Types$XenAPIException when scaling VM:i-2-10-VM d

[jira] [Updated] (CLOUDSTACK-1528) No UI level check for Overcommit ratio;It is accepting special character,negative values and zero

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1528: -- Component/s: API > No UI level check for Overcommit ratio;It i

[jira] [Updated] (CLOUDSTACK-3491) delete host resulting NPE; Exception caught while handling disconnect: java.lang.NullPointerException

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3491: -- Attachment: Logs_DB.rar > delete host resulting NPE; Exception

[jira] [Created] (CLOUDSTACK-3491) delete host resulting NPE; Exception caught while handling disconnect: java.lang.NullPointerException

prashant kumar mishra created CLOUDSTACK-3491: - Summary: delete host resulting NPE; Exception caught while handling disconnect: java.lang.NullPointerException Key: CLOUDSTACK-3491 URL: https://issues.a

[jira] [Comment Edited] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704474#comment-13704474 ] prashant kumar mishra edited comment on CLOUDSTACK-3446 at 7/10/13 12:00 PM: --

[jira] [Commented] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704474#comment-13704474 ] prashant kumar mishra commented on CLOUDSTACK-3446: --- these link may

[jira] [Updated] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3446: -- Attachment: Logs_DB.rar > Guest OS is getting memory=memory in

[jira] [Updated] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3446: -- Description: Steps to reproduce --- 1-prep

[jira] [Created] (CLOUDSTACK-3446) Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention

prashant kumar mishra created CLOUDSTACK-3446: - Summary: Guest OS is getting memory=memory in SO / memory.overcommit.ratio on kvm host even there is no contention Key: CLOUDSTACK-3446 URL: https://issu

[jira] [Updated] (CLOUDSTACK-3415) Guest os memory is not getting dynamically adjusted incase of overcommit

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3415: -- Attachment: Logs_DB.rar > Guest os memory is not getting dynam

[jira] [Created] (CLOUDSTACK-3415) Guest os memory is not getting dynamically adjusted incase of overcommit

prashant kumar mishra created CLOUDSTACK-3415: - Summary: Guest os memory is not getting dynamically adjusted incase of overcommit Key: CLOUDSTACK-3415 URL: https://issues.apache.org/jira/browse/CLOUDST

[jira] [Commented] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > ava

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700453#comment-13700453 ] prashant kumar mishra commented on CLOUDSTACK-1695: --- screenshot sho

[jira] [Updated] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > avail

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1695: -- Attachment: screenshot-1.jpg > Not enough cpu avialable in clu

[jira] [Updated] (CLOUDSTACK-1695) Not enough cpu avialable in cluster according to new overcommit ratio but all stopped Vms can be started without any failure(required cpu for stopped vm is > > avail

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1695: -- Attachment: DB_logs.rar > Not enough cpu avialable in cluster

[jira] [Updated] (CLOUDSTACK-3365) cluster level parameters cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3365: -- Summary: cluster level parameters cluster.(cpu/memory).allocated.c

[jira] [Updated] (CLOUDSTACK-3365) cluster level parameter cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3365: -- Attachment: Db_Logs.rar > cluster level parameter > cluster.(

[jira] [Updated] (CLOUDSTACK-3365) cluster level parameter cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3365: -- Attachment: screenshot-1.jpg > cluster level parameter > clus

[jira] [Created] (CLOUDSTACK-3365) cluster level parameter cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value

prashant kumar mishra created CLOUDSTACK-3365: - Summary: cluster level parameter cluster.(cpu/memory).allocated.capacity.notificationthreshold is not considering overcommit value Key: CLOUDSTACK-3365

[jira] [Closed] (CLOUDSTACK-1705) Overcommit ratio can be set at cluster level , Parameter "cpu.overprovisioning.factor" should not be there in Global settings

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-1705. - > Overcommit ratio can be set at cluster level , Parameter > "cpu.o

[jira] [Closed] (CLOUDSTACK-3187) cluster.(cpu/memory).allocated.capacity.disablethreshold in not considering overcommit factor;cluster is getting disable based on actual use

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-3187. - tested on master stable branch passed > cluster.(cpu/me

[jira] [Closed] (CLOUDSTACK-1622) Global parameter "cluster.memory.allocated.capacity.disablethreshold" is not disabling cluster after threshold value

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-1622. - tested on master stable branch ---passed > Global param

[jira] [Closed] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-1704. - Tested on master stable branch,passed > cluster is not

[jira] [Closed] (CLOUDSTACK-1534) Disable/Enable-unmanage/manage cluster is setting CPU overcommit and Memory overcommit ratio to 1(default value)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-1534. - tested on master stable branch passed > Disable/En

[jira] [Updated] (CLOUDSTACK-2982) listTemplates with templatefilter as “All” is not showing proper listing of templates when there are multiple zones.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2982: -- Priority: Major (was: Minor) > listTemplates with templatefil

[jira] [Updated] (CLOUDSTACK-2536) parameters (cpu/memory)overcommit ratio and (cpu/memory).overprosioning.factor are redundant(cluster level)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2536: -- Priority: Critical (was: Major) > parameters (cpu/memory)ove

[jira] [Updated] (CLOUDSTACK-3267) scaling up vm is failing on xen6.0.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3267: -- Summary: scaling up vm is failing on xen6.0.2 (was: scaling up vm

[jira] [Updated] (CLOUDSTACK-3267) scaling up vm is failing o on xen6.0.2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3267: -- Attachment: Logs_DB.rar > scaling up vm is failing o on xen6.0

[jira] [Created] (CLOUDSTACK-3267) scaling up vm is failing o on xen6.0.2

prashant kumar mishra created CLOUDSTACK-3267: - Summary: scaling up vm is failing o on xen6.0.2 Key: CLOUDSTACK-3267 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3267 Project: Clou

[jira] [Updated] (CLOUDSTACK-3230) UI add cluster remains in processing state

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3230: -- Attachment: screenshot-1.jpg > UI add cluster remains in proce

[jira] [Created] (CLOUDSTACK-3230) UI add cluster remains in processing state

prashant kumar mishra created CLOUDSTACK-3230: - Summary: UI add cluster remains in processing state Key: CLOUDSTACK-3230 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3230 Project:

[jira] [Updated] (CLOUDSTACK-3228) system vms are not comming up in zone with two cluster xen and kvm;Zone host is ready, but secondary storage vm template: 3 is not ready on secondary storage: 2

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3228: -- Attachment: DB_logs.rar > system vms are not comming up in zon

[jira] [Created] (CLOUDSTACK-3228) system vms are not comming up in zone with two cluster xen and kvm;Zone host is ready, but secondary storage vm template: 3 is not ready on secondary storage: 2

prashant kumar mishra created CLOUDSTACK-3228: - Summary: system vms are not comming up in zone with two cluster xen and kvm;Zone host is ready, but secondary storage vm template: 3 is not ready on secondary storage: 2

[jira] [Created] (CLOUDSTACK-3187) cluster.(cpu/memory).allocated.capacity.disablethreshold in not considering overcommit factor;cluster is getting disable based on actual use

prashant kumar mishra created CLOUDSTACK-3187: - Summary: cluster.(cpu/memory).allocated.capacity.disablethreshold in not considering overcommit factor;cluster is getting disable based on actual use Key: CLOUDSTACK-31

[jira] [Updated] (CLOUDSTACK-3187) cluster.(cpu/memory).allocated.capacity.disablethreshold in not considering overcommit factor;cluster is getting disable based on actual use

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3187: -- Attachment: DB_Logs.rar > cluster.(cpu/memory).allocated.capac

[jira] [Reopened] (CLOUDSTACK-3083) create volume doesn't check Global parameter " pool.storage.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra reopened CLOUDSTACK-3083: --- reopening with new observation, please close it if it is not a vali

[jira] [Updated] (CLOUDSTACK-3083) create volume doesn't check Global parameter " pool.storage.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3083: -- Attachment: Logs_Db.rar > create volume doesn't check Global p

[jira] [Commented] (CLOUDSTACK-3083) create volume doesn't check Global parameter " pool.storage.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690193#comment-13690193 ] prashant kumar mishra commented on CLOUDSTACK-3083: --- Observe Two po

[jira] [Updated] (CLOUDSTACK-3083) create volume doesn't check Global parameter " pool.storage.capacity.disablethreshold"

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3083: -- Attachment: Logs_DB.rar > create volume doesn't check Global p

[jira] [Created] (CLOUDSTACK-3083) create volume doesn't check Global parameter " pool.storage.capacity.disablethreshold"

prashant kumar mishra created CLOUDSTACK-3083: - Summary: create volume doesn't check Global parameter " pool.storage.capacity.disablethreshold" Key: CLOUDSTACK-3083 URL: https://issues.apache.org/jira/

[jira] [Closed] (CLOUDSTACK-1739) VMs are getting 1 GB memory on KVM hypervisor ,when they are deployed with Service Offering having RAM >=1GB and overcommit ratio is set to some value>1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-1739. - > VMs are getting 1 GB memory on KVM hypervisor ,when they are de

[jira] [Updated] (CLOUDSTACK-3053) Template creation from snapshot is failing on VMware setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3053: -- Description: Step to reproduce -- 1-Prepar

[jira] [Updated] (CLOUDSTACK-3053) Template creation from snapshot is failing on VMware setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-3053: -- Attachment: DB_Logs.rar > Template creation from snapshot is f

[jira] [Created] (CLOUDSTACK-3053) Template creation from snapshot is failing on VMware setup

prashant kumar mishra created CLOUDSTACK-3053: - Summary: Template creation from snapshot is failing on VMware setup Key: CLOUDSTACK-3053 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3053

[jira] [Closed] (CLOUDSTACK-1396) uuid field is NULL in hypervisore_capability table for Vmware ESXI 5.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-1396. - > uuid field is NULL in hypervisore_capability table for Vmware ESXI

[jira] [Closed] (CLOUDSTACK-1381) VMware cluster size in CS =(max_host_per_cluster valuse in hypervisore _capability table +1)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra closed CLOUDSTACK-1381. - > VMware cluster size in CS =(max_host_per_cluster valuse in hypervi

[jira] [Updated] (CLOUDSTACK-2990) After scaling up ,increased memory and cpu is not getting registered in guest OS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2990: -- Summary: After scaling up ,increased memory and cpu is not gettin

[jira] [Commented] (CLOUDSTACK-2990) After scaling up increased memory and cpu is not getting registered in guest OS

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682213#comment-13682213 ] prashant kumar mishra commented on CLOUDSTACK-2990: --- went through s

[jira] [Created] (CLOUDSTACK-2990) After scaling up increased memory and cpu is not getting registered in guest OS

prashant kumar mishra created CLOUDSTACK-2990: - Summary: After scaling up increased memory and cpu is not getting registered in guest OS Key: CLOUDSTACK-2990 URL: https://issues.apache.org/jira/brow

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Component/s: VMware > Actual capacity availble for vm deployem

[jira] [Commented] (CLOUDSTACK-2985) Scaling up cpu is not triggering live migration

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682137#comment-13682137 ] prashant kumar mishra commented on CLOUDSTACK-2985: --- please refer t

[jira] [Updated] (CLOUDSTACK-2985) Scaling up cpu is not triggering live migration

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2985: -- Description: Steps to reproduce - 1-ha

[jira] [Updated] (CLOUDSTACK-2985) Scaling up cpu is not triggering live migration

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2985: -- Attachment: DB_Logs.rar > Scaling up cpu is not triggering liv

[jira] [Created] (CLOUDSTACK-2985) Scaling up cpu is not triggering live migration

prashant kumar mishra created CLOUDSTACK-2985: - Summary: Scaling up cpu is not triggering live migration Key: CLOUDSTACK-2985 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2985 Proj

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Attachment: screenshot-1.jpg > Actual capacity availble for vm

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Attachment: screenshot-2.jpg > Actual capacity availble for vm

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Attachment: (was: screenshot-2.jpg) > Actual capacity avai

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Attachment: DB_Logs.rar > Actual capacity availble for vm depl

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Attachment: (was: screenshot-1.jpg) > Actual capacity avai

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Attachment: (was: screenshot-3.jpg) > Actual capacity avai

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Assignee: (was: Bharat Kumar) > Actual capacity availble f

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Description: ->For vmware cluster(with only one host) vcenter sh

[jira] [Updated] (CLOUDSTACK-1809) Actual capacity availble for vm deployement in vmware cluster is less than what Dashboard shows (total_capacity in op_host_capacity table)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1809: -- Summary: Actual capacity availble for vm deployement in vmware clus

[jira] [Updated] (CLOUDSTACK-2975) At zone level setting same parameter page is getting displayed repeatedly when you scroll down

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2975: -- Attachment: screenshot-1.jpg > At zone level setting same para

[jira] [Updated] (CLOUDSTACK-2975) At zone level setting same parameter page is getting displayed repeatedly when you scroll down

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2975: -- Description: steps to reproduce -- 1- go t

[jira] [Created] (CLOUDSTACK-2975) At zone level setting same parameter page is getting displayed repeatedly when you scroll down

prashant kumar mishra created CLOUDSTACK-2975: - Summary: At zone level setting same parameter page is getting displayed repeatedly when you scroll down Key: CLOUDSTACK-2975 URL: https://issues.apach

[jira] [Updated] (CLOUDSTACK-2954) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does n

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2954: -- Description: MS log is full of this message API -- -

[jira] [Updated] (CLOUDSTACK-2954) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does n

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2954: -- Attachment: DB_Logs.rar > Unable to execute API command query

[jira] [Created] (CLOUDSTACK-2954) Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does n

prashant kumar mishra created CLOUDSTACK-2954: - Summary: Unable to execute API command queryasyncjobresult due to invalid value. Invalid parameter jobid value=undefined due to incorrect long value format, or entity does not exist or

[jira] [Updated] (CLOUDSTACK-2941) system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configurati

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2941: -- Priority: Critical (was: Major) > system vm scaleup is failed

[jira] [Updated] (CLOUDSTACK-2941) system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configurati

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2941: -- Attachment: DB_and_logs.rar > system vm scaleup is failed due

[jira] [Created] (CLOUDSTACK-2941) system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configurati

prashant kumar mishra created CLOUDSTACK-2941: - Summary: system vm scaleup is failed due to (Unable to scale vm due to Unable to execute ScaleVmCommand due to java.lang.RuntimeException: Invalid virtual machine configuration)

[jira] [Updated] (CLOUDSTACK-2939) CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2939: -- Description: Steps to reproduce 1-Dep

[jira] [Updated] (CLOUDSTACK-2939) CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2939: -- Attachment: logs.rar > CPU limit is not getting set for vm aft

[jira] [Updated] (CLOUDSTACK-2939) CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-2939: -- Attachment: screenshot-1.jpg > CPU limit is not getting set fo

[jira] [Created] (CLOUDSTACK-2939) CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled

prashant kumar mishra created CLOUDSTACK-2939: - Summary: CPU limit is not getting set for vm after scaleup to a service offering which have cpu cap enabled Key: CLOUDSTACK-2939 URL: https://issues.apac

<    1   2   3   4   5   6   7   8   >