Red Hat Bugzilla – Bug 1275918
[userinterface_public_525]Available number is not matched with used number in pod metrics chart when choose different "Time Range"
Last modified: 2015-11-23 16:15:43 EST
Description of problem:
Check pod's metrics on web console, the available number is not matched with used number when choose different Time Range. The sum of available number and used number is not equal to the total number. It confused user how many resources are used.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Setup metrics. Create pod with cpu/memory requests/limits.
1.1 oc run cpuhog --image=busybox --requests=cpu=100m --limits=cpu=500m -- md5sum /dev/urandom
1.2 $oc create -f origin/examples/project-quota/application-template-with-resources.json -n pro1
$oc new-app ruby-helloworld-sample-with-resources
2.Login on web console, check pod cpuhog's metrics, switch "Time Range" in list: "Last 30 minutes, Last hour, Last 4 hours, Last day, Last week"
3.Check app's pod metrics such as frontend/database , switch "Time Range" in list: "Last 30 minutes, Last hour, Last 4 hours, Last day, Last week"
2,3.The available number is not matched with used number for some Time Range. The sum of available number and used number is not equal to the total number. Refer to the attachment.
2,3.Should have right number for any Time Range, and make it clear for users.
Created attachment 1087148 [details]
Created attachment 1087149 [details]
Created attachment 1087150 [details]
I suspect this is an angular-patternfly utilization chart bug since we don't calculate the available value, we only give them used and total. It looks like they're not watching changes to those values to update available.
We should be able to set the available value ourselves to workaround the problem, although I'd like to open an upstream issue as well.
Opened an upstream angular-patternfly pull request to fix:
origin pull request:
Tested on latest origin code.
Login on web console, check pod's metrics, switch "Time Range" in list: "Last 30 minutes, Last hour, Last 4 hours, Last day, Last week". Now the available number is matched with used number for all Time Range, and the sum of available number and used number is equal to the total number.
The bug has been fixed, so move it to verified.