MAAS reports incorrect memory amount
Bug #1878685 reported by
Lee Trager
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Lee Trager | ||
| 2.7 |
Fix Released
|
Undecided
|
Unassigned | ||
| lxd |
Fix Released
|
Unknown
|
|||
Bug Description
MAAS 2.8 gathers memory information from LXD. LXD is under reporting the amount of memory available in the system.
Related branches
~ltrager/maas:lp1878923_lp1878685_2.7
- Lee Trager (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 108 lines (+51/-12)3 files modifiedsrc/machine-resources/src/machine-resources/Gopkg.lock (+7/-2)
src/metadataserver/builtin_scripts/hooks.py (+8/-10)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+36/-0)
~ltrager/maas:lp1878923_lp1878685
- Dougal Matthews (community): Approve
- MAAS Lander: Approve
-
Diff: 101 lines (+46/-10)3 files modifiedsrc/machine-resources/src/machine-resources/Gopkg.lock (+2/-1)
src/metadataserver/builtin_scripts/hooks.py (+8/-9)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+36/-0)
Revision history for this message
| Lee Trager (ltrager) wrote | #1 |
| Changed in maas: | |
| milestone: | none → 2.8.0rc1 |
| Changed in lxd: | |
| status: | Unknown → New |
| Changed in lxd: | |
| status: | New → Fix Released |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Stéphane is working on a fix. Once the patch is added to LXD all we have to do is update the LXD source we build machine-resources from.
If this doesn't happen in time we can bring back the old code which gathers memory information from lshw.