Hypervisor summary shows incorrect total storage (Ceph)

Bug #1387812 reported by Sergey Nikitin on 2014-10-30
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Medium
Unassigned

Bug Description

On Horizon UI in Admin/Hypervisors, Disk Usage shows incorrect value.

Since using Ceph for ephemeral storage it adds up the ceph storage seen in each storage node rather than just using the real amount of ceph storage.
When we use Ceph we should divide sum of storage sizes by the replication factor of ceph storage. (Replication factor is a number which tells how much times information into the Ceph storage would be duplicated).
For example we have 3 nodes and each node has 60 Gb storage.
Replication factor is 2. So total storage is 60 * 3 / 2 = 90.
But now size of a total storage is calculating as 60 + 60 + 60 = 180. See the screenshot (the real size of storage is 207 Tb.)
So if type storage is Ceph, we should ask information about size of storage directly from Ceph.

Sergey Nikitin (snikitin) wrote :
Changed in nova:
assignee: nobody → Sergey Nikitin (snikitin)

Fix proposed to branch: master
Review: https://review.openstack.org/132084

Changed in nova:
status: New → In Progress
Changed in nova:
importance: Undecided → Low
summary: - Hypervisor summary shows incorrect total storage
+ Hypervisor summary shows incorrect total storage (Ceph)

Change abandoned by Sergey Nikitin (<email address hidden>) on branch: master
Review: https://review.openstack.org/132084

Changed in nova:
assignee: Sergey Nikitin (snikitin) → nobody
status: In Progress → Confirmed
Vikram Hosakote (vhosakot) wrote :

Is this bug fixed ? I see it in kilo.

In kilo, "Local Disk Usage" in "Hypervisor Summary" is wrong.

melanie witt (melwitt) on 2016-07-01
tags: added: ceph

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
importance: Low → Undecided
status: Confirmed → Expired
Dr. Jens Harbott (j-harbott) wrote :

CONFIRMED FOR: MITAKA

Changed in nova:
status: Expired → New
John Garbutt (johngarbutt) wrote :

So the work on the scheduler for resource providers is looking to address this problem.

tags: added: resource-tracker
Changed in nova:
status: New → Triaged
importance: Undecided → Medium
Shabna Shaik (shabna942) on 2017-03-05
Changed in nova:
assignee: nobody → Shabna Shaik (shabna942)
Sean Dague (sdague) on 2017-06-23
Changed in nova:
assignee: Shabna Shaik (shabna942) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers