Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 23 Jul 2013 11:38:48 +0000 (UTC)
From: "Harikrishna Patnala (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12635496.1362548288920.96397.1374579528301@arcas>
In-Reply-To: <JIRA.12635496.1362548288920@arcas>
References: <JIRA.12635496.1362548288920@arcas>
Subject: [jira] [Assigned] (CLOUDSTACK-1528) No UI level check for
 Overcommit ratio;It is accepting special character,negative values and zero
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harikrishna Patnala reassigned CLOUDSTACK-1528:
-----------------------------------------------

    Assignee: Harikrishna Patnala  (was: Bharat Kumar)
    
> No UI level check for Overcommit ratio;It is accepting special character,negative values and zero
> -------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1528
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1528
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, UI
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: Harikrishna Patnala
>             Fix For: 4.2.0
>
>         Attachments: screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg
>
>
> 1-There is no check in UI for special character and zero.
> 2-If we provide any special character or zero for overcommit ratio in UI ,DB is getting upgraded by default value 1.
> Steps
> --------
> 1-Create a cluster provide some special characters for overcommit ratio
> Expected
> -------------
> should have some error message , overcommite ratio cant't be special character or less than zero etc.
> Actual
> ------------
> cluster is getting created with overcommit ratio ={special character,zero,-ive values} but DB is storing default value 1 .
> DB
> -------
> mysql> select* from cluster_details;
> +----+------------+-----------------------+-------+
> | id | cluster_id | name                  | value |
> +----+------------+-----------------------+-------+
> |  1 |          1 | cpuOvercommitRatio    | 1.0   |
> |  2 |          1 | memoryOvercommitRatio | 1.0   |
> |  3 |          2 | cpuOvercommitRatio    | 1.0   |
> |  4 |          2 | memoryOvercommitRatio | 1.0   |
> |  5 |          3 | cpuOvercommitRatio    | 1.0   |
> |  6 |          3 | memoryOvercommitRatio | 1.0   |
> +----+------------+-----------------------+-------+

--
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