[ https://issues.apache.org/jira/browse/CLOUDSTACK-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
prashant kumar mishra updated CLOUDSTACK-1622: ---------------------------------------------- Attachment: (was: apilog.log) > Global parameter "cluster.memory.allocated.capacity.disablethreshold" is not > disabling cluster after threshold value > --------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-1622 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1622 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Affects Versions: 4.2.0 > Reporter: prashant kumar mishra > Fix For: 4.2.0 > > Attachments: logs.rar > > > Cluster should get disable after alocated memory crosses threshold of global > parameter cluster.memory.allocated.capacity.disablethreshold . > ->-->when i set "cluster.memory.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.memory.allocated.capacity.disablethreshold" stop working. > Steps to repo > ------------------- > 1-Set Global parameter cluster.memory.allocated.capacity.disablethreshold to > some value say 0.3 > 2-set cluster level parameter > cluster.memory.allocated.capacity.disablethreshold to blank space > 3-Deploy vms > Expected > ---------------- > After threshold value (0.3) cluster should get disable > Actual > --------- > Cluster is not getting disable -- 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