[ https://issues.apache.org/jira/browse/CLOUDSTACK-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681133#comment-13681133 ]
ASF subversion and git services commented on CLOUDSTACK-2957: ------------------------------------------------------------- Commit 2aafc39f3d0570fac1ddcebf4623f1c37e8e47e5 in branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2aafc39 ] CLOUDSTACK-2957 deployVm API size attribute should be capped by the storage.max.volume.size as it is in createVolume. > deployVm API size attribute should be capped by the storage.max.volume.size > as it is in createVolume > ---------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-2957 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2957 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.2.0 > Reporter: Nitin Mehta > Assignee: Nitin Mehta > Fix For: 4.2.0 > > > size atribute when used with custom disk offering should be limited by > storage.max.volume.size global config (default 2000 gb) as it is in > createVolume but from the code seems like its not. The number is used to > avoid abuse by the end user. -- 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