[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Attachment: (was: screenshot-2.jpg) > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: cloud-backup.dmp, log.rar > > > --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character > 4-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Attachment: (was: screenshot-1.jpg) > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: cloud-backup.dmp, log.rar > > > --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character > 4-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Attachment: (was: setupManagement.log) > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: cloud-backup.dmp, log.rar > > > --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character > 4-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Attachment: (was: cloud-backup1.dmp) > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: cloud-backup.dmp, log.rar, management-server.log, > screenshot-1.jpg, screenshot-2.jpg, setupManagement.log > > > --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character > 4-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Attachment: (was: management-server.log) > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: cloud-backup.dmp, log.rar, screenshot-1.jpg, > screenshot-2.jpg, setupManagement.log > > > --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character > 4-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Attachment: cloud-backup.dmp log.rar uploading new logs and db dump > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: cloud-backup.dmp, log.rar, management-server.log, > screenshot-1.jpg, screenshot-2.jpg, setupManagement.log > > > --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character > 4-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Attachment: (was: apilog.log) > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: cloud-backup.dmp, log.rar, management-server.log, > screenshot-1.jpg, screenshot-2.jpg, setupManagement.log > > > --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character > 4-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Description: --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value between 0 and 1) of cpu utilization above which allocators will disable using the cluster for low cpu available. -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank character at cluster level , Global parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. Steps to reproduce 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , 2-Restart MS 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character 4-Deploy some vms , so that cpu utilizatio should be >0.5 Expected - Cluster should be disabled after threshold value Actual --- cluster is not getting disabled after threshold value was: "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value between 0 and 1) of cpu utilization above which allocators will disable using the cluster for low cpu available. Steps to reproduce 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , 2-Restart MS 3-Deploy some vms , so that cpu utilizatio should be >0.5 Expected - Cluster should be disabled after threshold value Actual --- cluster is not getting disabled after threshold value > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: apilog.log, cloud-backup1.dmp, management-server.log, > screenshot-1.jpg, screenshot-2.jpg, setupManagement.log > > > --> "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > -->when i set "cluster.cpu.allocated.capacity.disablethreshold" to blank > character at cluster level , Global > parameter"cluster.cpu.allocated.capacity.disablethreshold" stop working. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Set cluster.cpu.allocated.capacity.desablethreshold to "blank" character > 4-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Assignee: (was: Bharat Kumar) > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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: apilog.log, cloud-backup1.dmp, management-server.log, > screenshot-1.jpg, screenshot-2.jpg, setupManagement.log > > > "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
[jira] [Updated] (CLOUDSTACK-1704) cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] prashant kumar mishra updated CLOUDSTACK-1704: -- Summary: cluster is not getting disabled after threshold value set to global parameter "cluster.cpu.allocated.capacity.disablethreshold" (was: cluster is not getting disabled after threshold value set in global parameter "cluster.cpu.allocated.capacity.disablethreshold") > cluster is not getting disabled after threshold value set to global parameter > "cluster.cpu.allocated.capacity.disablethreshold" > --- > > Key: CLOUDSTACK-1704 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1704 > 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 >Assignee: Bharat Kumar > Fix For: 4.2.0 > > Attachments: apilog.log, cloud-backup1.dmp, management-server.log, > screenshot-1.jpg, screenshot-2.jpg, setupManagement.log > > > "cluster.cpu.allocated.capacity.disablethreshold "Percentage (as a value > between 0 and 1) of cpu utilization above which allocators will disable using > the cluster for low cpu available. > Steps to reproduce > > 1-Set cluster.cpu.allocated.capacity.disablethreshold to 0.5 , > 2-Restart MS > 3-Deploy some vms , so that cpu utilizatio should be >0.5 > Expected > - > Cluster should be disabled after threshold value > Actual > --- > cluster is not getting disabled after threshold value -- 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
