Disk/memory space on Node edit page have no units
Bug #1281406 reported by
Jeroen T. Vermeulen
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Low
|
Raphaël Badin |
Bug Description
On the Node edit form, disk space and memory space are just numbers. The labels ought to say whether these megabytes, gigabytes, or something else (petabytes, kibibytes...). It may seem clear from the numbers themselves, but let's take extreme machine sizes, accidental editing, and external distractions into account.
Related branches
lp:~rvb/maas/bug-1281406
- Gavin Panella (community): Approve
-
Diff: 15 lines (+2/-2)1 file modifiedsrc/maasserver/forms.py (+2/-2)
Changed in maas: | |
milestone: | none → 14.10 |
Changed in maas: | |
milestone: | 1.6.0 → none |
Changed in maas: | |
assignee: | nobody → Raphaël Badin (rvb) |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | none → 1.7.0 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've run into confusion over this issue when dealing with nodes on a SeaMicro box which had been (mis)configured without real hard disks; MAAS detects the disk size as "1408" (from memory), which seems to refer to a small floppy-disk-sized default disk. (I didn't investigate too deeply.)