cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-6822) Instance->Change service offering ->Custom Instance allow to exceed domain cpu cores, cpuspeed and/or memory limits
Date Fri, 05 Dec 2014 14:37:13 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rohit Yadav reassigned CLOUDSTACK-6822:
---------------------------------------

    Assignee: Rohit Yadav

> Instance->Change service offering ->Custom Instance allow to exceed domain cpu
cores, cpuspeed and/or memory limits
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6822
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6822
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Storage Controller, Template, Usage, Volumes
>    Affects Versions: 4.3.0
>         Environment: Domain with custom offerings
>            Reporter: juan.barrio.altia
>            Assignee: Rohit Yadav
>            Priority: Critical
>              Labels: cpu, cpuspeed, custom, domain, limits, memory, offering, resource
>
> 1. Create a new domain
> 2. Create a new domain admin
> 3. Assign new custom instance to the new domain
> 4. As domain admin, create a new VM
> 5. Asign a new standard instance to this domain
> 6. Change instance to custom instance
> 7. Call updateResourceCount
> 8. Now resourcecount for domain are wrong
> 9. Change instance to custom instance exceeding domain limits
> 10. Instance is created
> -------------
> Seems resourcecount for domain is going wrong or limits are not checked as it would be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message