msinhore opened a new issue #3542: The # of CPU_CORE capacity has been shown wrongly URL: https://github.com/apache/cloudstack/issues/3542 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ capacity calculation ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11 ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> ##### SUMMARY <!-- Explain the problem/feature briefly --> The # of CPU_CORE capacity has been shown wrongly when, even considering the operprovisioning factor, the value presented should be for maximum capacity = 100% and no more than this. Example in CloudMonkey command: cloudmonkey list capacity filter=name,percentused, | grep CPU_CORE CPU_CORE,195.72 In the UI, the CPU_CORE value, shown out of margin in "Infrastructure > Zones > select zone > Resources"  
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
