Redfish controller iDRAC returns 406 error

[Chris Newcomer]

When using the MAAS GUI to control an iDRAC BMC (version 3.30.30.30) via the Redfish protocol, it dumps a stack trace in the rackd.log and returns a 406 error. This is believed to be due to an issue with the version of iDRAC that doesn't conform to the RFC:
If no Accept header field is present, then it is assumed that the client accepts all media types.

Q: Does MAAS explicitly set the 'Accept: application/json' header?

A similar issue reported in Ansible that was fixed by setting the header:
https://github.com/ansible/ansible/issues/55078

[Chris Newcomer (cnewcomer)]

After reviewing the code in [2], it would appear that the proper headers are not being sent to the Redfish API, according to [1]:

GET_HEADERS = {'accept': 'application/json', 'OData-Version': '4.0'}
POST_HEADERS = {'content-type': 'application/json', 'accept': 'application/json', 'OData-Version': '4.0'}
PATCH_HEADERS = {'content-type': 'application/json', 'accept': 'application/json', 'OData-Version': '4.0'}
DELETE_HEADERS = {'accept': 'application/json', 'OData-Version': '4.0'}

Not sure the OData ones are needed, those are mostly for compliance, but others are definitely needed or it will fail in some hardware.

[1] https://github.com/ansible/ansible/pull/55193
[2] https://git.launchpad.net/maas/tree/src/provisioningserver/drivers/power/redfish.py#n57

[Jerzy Husakowski (jhusakowski)]

Is this still reproducible on newer MAAS versions? LP:1845032 looks similar and the fix landed in MAAS 2.7

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]