cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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]
Date Thu, 14 Mar 2013 21:06:14 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602745#comment-13602745
] 

ASF subversion and git services commented on CLOUDSTACK-1645:
-------------------------------------------------------------

Commit 105618896bab9de790065c3913cc33eb878ead1b in branch refs/heads/master from [~sanjay.tripathi]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=1056188 ]

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]

                
> 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

Mime
View raw message