MAAS UI reports storage size in Gibibytes (base 2) but is labeled GB - Gigabytes (base 10).
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Jason Hobbs | ||
1.7 |
Fix Released
|
Undecided
|
Jason Hobbs |
Bug Description
My node is reported in the UI's node listing page as having 119 GB of storage. However, the lshw output shows 128035676160 bytes, which is 128.03567616 GB (Gigabytes).
<lshw:node id="disk" claimed="true" class="disk" handle=
<lshw:size units="
</lshw:node>
Version: 1.7.1+bzr3373-
Related branches
- Blake Rouse (community): Approve
-
Diff: 515 lines (+402/-14)5 files modifiedsrc/maasserver/migrations/0121_recompute_storage_size.py (+383/-0)
src/maasserver/models/node.py (+10/-5)
src/maasserver/models/tests/test_node.py (+4/-4)
src/metadataserver/models/commissioningscript.py (+1/-1)
src/metadataserver/models/tests/test_noderesults.py (+4/-4)
description: | updated |
Changed in maas: | |
milestone: | none → 1.7.1 |
tags: | added: server-hwe |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
importance: | High → Critical |
Changed in maas: | |
assignee: | nobody → Jason Hobbs (jason-hobbs) |
tl;dr Use GiB everywhere because GB is the ambiguous term.
<allenap> rvba: I think we might be at the point where enough people are
aware of GB and GiB that we ought to clarify which one we mean, or
show both (which would be my preference).
<rvba> allenap: this field is also something users can edit so we need
to pick one (even if we can show both in the view page).
<rvba> allenap: also, I don't think we want to display both on the
listing page.
<allenap> rvba: Right, good point. GB is the ambiguous term, so I
propose GiB everywhere with GB in tooltips or brackets.