Hypervisor summary shows incorrect RAM usage

[Sergey Nikitin]

Fuel 5.1
Openstack deployment Centos, Multi-node with HA, three nodes (one controller, two compute nodes) with Ceph OSD, ceph for ephemeral, images, block and object.

If size of RAM in each compute node will be a little less 1 Gb (996 Mb in this case) total memory usage will be incorrect (see the screenshot). If we have two nodes with 996 Mb RAM, total we have 1,95 Gb RAM. But screenshot shows "Used 1Gb (its true) of 1 Gb (its not true)". But a diagram of RAM usage is correct (half of the circus is colored). So we should see "Used 1Gb of 1,95Gb" or at least "Used 1 Gb of 2 Gb".

[Paul Karikh (pkarikh)]

Works for me. Maybe, this bug was already fixed in some patch? Fuel version - "5.0.2".

[Paul Karikh (pkarikh)]

Full Fuel version:
{"build_id": "2014-10-28_00-01-06", "ostf_sha": "2969c1ad443b632e815bb1f01149c3800cd7aa3a", "build_number": "17", "api": "1.0", "nailgun_sha": "c18a21381843dffe807b254a4ff96eec259953cb", "production": "docker", "fuelmain_sha": "2db390c01df7836f90a5d8dc9f79a92077b69a90", "astute_sha": "6db5f5031b74e67b92fcac1f7998eaa296d68025", "feature_groups": ["mirantis"], "release": "5.0.2", "fuellib_sha": "a6737e68030cd92ef13bb74f176b74294139cb50"}

[Timur Sufiev (tsufiev-x)]

Sergey, could you please verify whether it's still an issue for you on latest Fuel 5.x?

[Sergey Nikitin (snikitin)]

Ok, I checked two versions of fuel 5.X.
1. Release version from here https://mirantis.jira.com/wiki/display/PRD/5.1+release (first ISO image)
2. The last bild of 5.1.1 from here http://jenkins-product.srt.mirantis.net:8080/view/5.1.1/job/5.1.1.iso/17/

Bug was reproduced in both cases.

Full fuel version of the second ISO:

{"build_id": "2014-11-04_21-17-27", "ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346", "build_number": "17", "auth_required": true, "api": "1.0", "nailgun_sha": "4aa4fb5f89c02aaee5bec1aa4677b48598ffe482", "production": "docker", "fuelmain_sha": "16e6cfd1b4775cccfd9a6f0d66d3826d41d3214e", "astute_sha": "f5fbd89d1e0e1f22ef9ab2af26da5ffbfbf24b13", "feature_groups": ["mirantis"], "release": "5.1.1", "release_versions": {"2014.1.1-5.1.1": {"VERSION": {"build_id": "2014-11-04_21-17-27", "ostf_sha": "64cb59c681658a7a55cc2c09d079072a41beb346", "build_number": "17", "api": "1.0", "nailgun_sha": "4aa4fb5f89c02aaee5bec1aa4677b48598ffe482", "production": "docker", "fuelmain_sha": "16e6cfd1b4775cccfd9a6f0d66d3826d41d3214e", "astute_sha": "f5fbd89d1e0e1f22ef9ab2af26da5ffbfbf24b13", "feature_groups": ["mirantis"], "release": "5.1.1", "fuellib_sha": "42c25fc764dd931615ae767a3b91574ed1c95f16"}}}, "fuellib_sha": "42c25fc764dd931615ae767a3b91574ed1c95f16"}

[Sergey Nikitin (snikitin)]

Screenshot for second fuel iso.

[Vlad Okhrimenko (vokhrimenko)]

I reproduced this bug for MOS 5.1. But not reproduced for (MOS 6.0):

{"build_id": "2014-11-23_10-54-46", "ostf_sha": "a35f516f1606b0d03d51ff63bfe3fbe23de4b622", "build_number": "130", "auth_required": true, "api": "1.0", "nailgun_sha": "7196c478bfe0b5cff97077c1829009b9dbc3ee92", "production": "docker", "fuelmain_sha": "0dd338b6280843b4c45b46635528a6c43939c772", "astute_sha": "c15623d05ccdf7ac10873e7a90df954de8726280", "feature_groups": ["mirantis"], "release": "6.0", "release_versions": {"2014.2-6.0": {"VERSION": {"build_id": "2014-11-23_10-54-46", "ostf_sha": "a35f516f1606b0d03d51ff63bfe3fbe23de4b622", "build_number": "130", "api": "1.0", "nailgun_sha": "7196c478bfe0b5cff97077c1829009b9dbc3ee92", "production": "docker", "fuelmain_sha": "0dd338b6280843b4c45b46635528a6c43939c772", "astute_sha": "c15623d05ccdf7ac10873e7a90df954de8726280", "feature_groups": ["mirantis"], "release": "6.0", "fuellib_sha": "2bfa9431a4839efae9c75d6b133df24c0f11c868"}}}, "fuellib_sha": "2bfa9431a4839efae9c75d6b133df24c0f11c868"}

and not reproduced for "build_number": "111" too.
Maybe, this bug was already fixed in some patch ?

[Timur Sufiev (tsufiev-x)]

Setting to 'Invalid' due to inability to reproduce. Please feel free to reopen if it persists for you.