Redfish power configuration vanishes after commissioning
Bug #1862102 reported by
Adam Beeman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Alberto Donato | ||
2.7 |
Fix Released
|
Medium
|
Alberto Donato |
Bug Description
I added a new Dell C6420 to MAAS with power type = Redfish. The system commissioned successfully, then immediately went to power state = Error. Revisiting the Configuration tab for the system, it no longer has any power control information.
I tried repeating this with the checkbox to not try to create a new power control user during commissioning, and got the same result from that as well.
Related branches
~ack/maas:1862102-redfish-credentials-fix
Merged
into
maas:master
- MAAS Lander: Needs Fixing
- Björn Tillenius: Approve
-
Diff: 101 lines (+43/-16)2 files modifiedsrc/maasserver/api/nodes.py (+14/-12)
src/maasserver/api/tests/test_api.py (+29/-4)
summary: |
- [2.7.0~rc3] Redfish power configuration vanishes after commissioning + Redfish power configuration vanishes after commissioning |
tags: | added: ui |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.8.0b1 |
tags: | removed: ui |
Changed in maas: | |
assignee: | nobody → Alberto Donato (ack) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It seems the issue is the call to store_node_ power_parameter s() in src/metadataser ver/api. py which ends up being called for a request which doesn't contain power parameters.