You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sailaja Mada (JIRA)" <ji...@apache.org> on 2013/07/22 16:42:48 UTC
[jira] [Closed] (CLOUDSTACK-1645) Resources limit is not validated
with update compute offering [ Instances are updated to higher CPU/Memory
resources though there are no resources available @ account/domain]
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sailaja Mada closed CLOUDSTACK-1645.
------------------------------------
This is fixed with latest 4.2 . Hence closing the bug,
> Resources limit is not validated with update compute offering [ Instances are updated to higher CPU/Memory resources though there are no resources available @ account/domain]
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1645
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1645
> 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: Sailaja Mada
> Assignee: Sanjay Tripathi
> Priority: Critical
> Fix For: 4.2.0
>
>
> Setup: Advanced Networking zone with Xen 6.1 host
> Steps:
> 1. Create Child Domain and set CPU resource limit to 2 core as Domain limits
> 2. Deploy VM with 1 core CPU
> 3. Create New Compute offering with 4 CPU
> 4. Update instance compute offering from 1 core to 4 core cpu
> 5. Start the instance
> Observation:
> 1. Instances are updated to higher CPU/Memory resources though there are no resources available @ account/domain
> 2.Resources limit is not validated with update compute offering
> Expected results :
> 1.Resources limit need to be validated while performing Update offering .
--
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