You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/24 11:51:58 UTC

[jira] [Commented] (CLOUDSTACK-9603) 'concurrent.snapshots.threshold.perhost' does not validate value given

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

ASF GitHub Bot commented on CLOUDSTACK-9603:
--------------------------------------------

GitHub user priyankparihar opened a pull request:

    https://github.com/apache/cloudstack/pull/1776

    CLOUDSTACK-9603: concurrent.snapshots.threshold.perhost does not valiā€¦

    concurrent.snapshots.threshold.perhost does not validate value given

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/priyankparihar/cloudstack CLOUDSTACK-9603

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1776.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1776
    
----
commit 141926b1439c2fe99621c9c56114e948066f17c3
Author: Priyank Parihar <pr...@accelerite.com>
Date:   2016-09-06T17:41:06Z

    CLOUDSTACK-9603: concurrent.snapshots.threshold.perhost does not validate value given.

----


> 'concurrent.snapshots.threshold.perhost' does not validate value given
> ----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9603
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9603
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Priyank Parihar
>            Assignee: Priyank Parihar
>            Priority: Minor
>
> concurrent.snapshots.threshold.perhost this setting at global and cluster level should accept only integer values. It is accepting string values as well which should be rejected.



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