[2.5, UI] Pod core counts are inconsistent
Bug #1811662 reported by
Björn Tillenius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Steve Rydz | ||
| 2.5 |
Fix Released
|
High
|
Unassigned | ||
Bug Description
This is with MAAS 2.5.1-7489-
I register a pod on a machine that has 4 physical cores. I set the CPU
overcommit ratio to 4.7.
Now I see different core counts all over the place:
* pod listing says '-9 free of 4'
* pod overview page says '13 used, 5.8 available'
* pod compose page says '4 available'
Related branches
~steverydz/maas:backport-pod-core-ram-bugfix
- Steve Rydz: Approve
-
Diff: 96 lines (+23/-17)5 files modifiedsrc/maasserver/static/js/angular/controllers/pod_details.js (+1/-11)
src/maasserver/static/js/angular/controllers/pods_list.js (+3/-0)
src/maasserver/static/js/angular/factories/pods.js (+13/-0)
src/maasserver/static/partials/pod-details.html (+2/-2)
src/maasserver/static/partials/pods-list.html (+4/-4)
~steverydz/maas:pod-core-and-ram-amounts
- Lilyana Videnova (community): Approve
- MAAS Lander: Approve
- Blake Rouse (community): Approve
-
Diff: 96 lines (+23/-17)5 files modifiedsrc/maasserver/static/js/angular/controllers/pod_details.js (+1/-11)
src/maasserver/static/js/angular/controllers/pods_list.js (+3/-0)
src/maasserver/static/js/angular/factories/pods.js (+13/-0)
src/maasserver/static/partials/pod-details.html (+2/-2)
src/maasserver/static/partials/pods-list.html (+4/-4)
| tags: | added: ui |
| Changed in maas: | |
| status: | New → Incomplete |
| status: | Incomplete → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.5.1 |
| Changed in maas: | |
| milestone: | 2.5.1 → 2.5.2 |
Revision history for this message
| Lilyana Videnova (lilyanavidenova) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Steve Rydz (steverydz) |
| Changed in maas: | |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | 2.5.2 → 2.6.0 |
| Changed in maas: | |
| milestone: | 2.6.0 → 2.6.0alpha1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Similarly the RAM amounts differ between the three places.
The correct number of used, available and total cores and RAM are displayed on the overview page as they take into account the overcommit ratios applied to them.
The other two places should use the same information:
- on the listing page the used and total number of cores/amount of RAM after the overcommit is applied should be shown with a tooltip telling the user what the "real" number of cores/amount of RAM is and what overcommit ratio is applied. For the example above the row in the listing page would read "5.8 free of 18.8", with a tooltip reading "4 cores x 4.7 CPU overcommit".
- the compose page should say 5.8 available; as the user would have first seen both the listing and the individual pod overview page, the detail of what the overcommit ratio is can be omitted, in order not to make the sublabel of the field too long.