Auto-enlistment not reporting power parameters
Bug #1363850 reported by
Jeroen T. Vermeulen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Graham Binns | ||
Bug Description
I just auto-enlisted a NUC after upgrading to a package freshly built from trunk. The node registered itself, but failed to register any power parameters. (Nor did it register number of CPUs, memory size, or storage capacity — but maybe that's only supposed to happen during commissioning).
Power parameters were discovered correctly just a few days ago, even though auto-enlistment ended up failing (see bug 1363836).
Architecture and MAC address were registered correctly. After I registered power type and power parameters manually, the node seemed to work normally.
Related branches
lp://qastaging/~gmb/maas/prob-mscm-power-params-testcase
- Raphaël Badin (community): Approve
-
Diff: 70 lines (+30/-1)2 files modifiedsrc/maasserver/rpc/nodes.py (+5/-0)
src/maasserver/rpc/tests/test_nodes.py (+25/-1)
| description: | updated |
| summary: |
- Auto-enlistment not reporting power parameters, memory, CPUs, or storage + Auto-enlistment not reporting power parameters |
| description: | updated |
| description: | updated |
| description: | updated |
| Changed in maas: | |
| milestone: | none → 1.7.0 |
Revision history for this message
| Graham Binns (gmb) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| assignee: | nobody → Graham Binns (gmb) |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This should be fixed now (as of r3047)… Can you double-check for me (I have nothing available to test auto-enlistment with right now).