Failed to set one-time boot via Redfish
Bug #1925298 reported by
renxulei
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Paul Jonason | ||
Bug Description
I am trying to use MAAS (MAAS version: 2.9.2) to manage Lenovo servers. When I add one server and used "Redfish" as power management type for this server (Lenovo ThinkSystem SR635), I found the commission failed. I tracked the Redfish requests to the server, found that when MAAS sent PATCH request to set one-time boot, 'etag' property is not specified in request body which caused BMC side returned error code 428, but per industry Redfish standard spec, 'etag' is recommended. Is it possible that MAAS can fix this? Thanks.
Related branches
~pjonason/maas:add-redfish-etag-bug-1925298
- MAAS Lander: Approve
- Björn Tillenius: Approve
-
Diff: 206 lines (+154/-1)2 files modifiedsrc/provisioningserver/drivers/power/redfish.py (+18/-0)
src/provisioningserver/drivers/power/tests/test_redfish.py (+136/-1)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 3.0.1 |
Revision history for this message
| Paul Jonason (pjonason) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Paul Jonason (pjonason) |
| milestone: | 3.0.1 → 3.1.0 |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | 3.1.0 → 3.1.0-beta5 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I am directed to a web link for the log containing the test failures, but I am unable to connect because of redirect errors. Clearing and disabling cookies does not help. Is there any other way to view the failure log and see what the problem is? The tests work fine locally.