[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-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable) 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) Expected -- cpu limit should be set for the vm Actual there is no cpu limit for vm My observation -- 1-CPU limit is set to unlimited when i do scaleup from a SO (cpu cap enable) to a SO (cpu cap enable) . was: Steps to reproduce 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not enable) 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) Expected -- cpu limit should be set for the vm Actual there is no cpu limit for vm > 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.apache.org/jira/browse/CLOUDSTACK-2939 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, VMware >Affects Versions: 4.2.0 > Environment: VMware ESXI-5.1 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: logs.rar, screenshot-1.jpg > > > Steps to reproduce > > 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not > enable) > 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) > Expected > -- > cpu limit should be set for the vm > Actual > > there is no cpu limit for vm > My observation > -- > 1-CPU limit is set to unlimited when i do scaleup from a SO (cpu cap enable) > to a SO (cpu cap enable) . -- 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
[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 after scaleup to a service offering which > have cpu cap enabled > -- > > Key: CLOUDSTACK-2939 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2939 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, VMware >Affects Versions: 4.2.0 > Environment: VMware ESXI-5.1 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: logs.rar, screenshot-1.jpg > > > Steps to reproduce > > 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not > enable) > 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) > Expected > -- > cpu limit should be set for the vm > Actual > > there is no cpu limit for vm -- 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
[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 for vm after scaleup to a service offering which > have cpu cap enabled > -- > > Key: CLOUDSTACK-2939 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2939 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, VMware >Affects Versions: 4.2.0 > Environment: VMware ESXI-5.1 >Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: screenshot-1.jpg > > > Steps to reproduce > > 1-Deploye a vm with small service offering (memory:512,cpu:500;cpu cap=not > enable) > 2-Scaleup to service offering (memory:512,cpu:1000, cpu cap=enable) > Expected > -- > cpu limit should be set for the vm > Actual > > there is no cpu limit for vm -- 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
