meta-ibm: Disable redfish-oem-manager-fan-data
The bmcweb bummp adding this meson option merged so this can go.
IBM does not use phosphor-pid-control instead using phosphor-fan-presence
and such.
This Redfish OEM fan data includes PATCHing. Turn this PATCHing off and
the whole Manager OEM Fan data. This has been done downstream already.
We have also observed 500 errors with getting the thermalMode.
"Jan 24 16:34:57 rain534 bmcweb[435]: (2022-01-24 16:34:57) [ERROR
"managers.hpp":1196] GetPIDValues: Can't get thermalModeIface
/xyz/openbmc_project/control/thermal/0"
Tested: No longer see this InternalErrors. Been running with this
downstream.
Tested on a Tacoma.
Before on a PATCH:
curl -k -X PATCH https://$bmc/redfish/v1/Managers/bmc -d '{"Oem":{"OpenBmc":{"Fan":{"Profile":"Acoustic"}}}}'
{
"error": {
"@Message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_1_1.Message",
"Message": "The request failed due to an internal service...
With this change and the bmcweb change (instead see a PropertyUnknown)
curl -k -X PATCH https://$bmc/redfish/v1/Managers/bmc -d '{"Oem":{"OpenBmc":{"Fan":{"Profile" : "Acoustic"} }}}'
{
"error": {
"@Message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_1_1.Message",
"Message": "The property %1 is not in the list of valid properties for the resource.",
"MessageArgs": [
"Oem"
],
"MessageId": "Base.1.13.0.PropertyUnknown",
...
Change-Id: Ic988e2949ad65b31eb0b9bc6ecbdceb997d8cdda
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
diff --git a/meta-ibm/recipes-phosphor/interfaces/bmcweb_%.bbappend b/meta-ibm/recipes-phosphor/interfaces/bmcweb_%.bbappend
index 1c1ebfb..840469b 100644
--- a/meta-ibm/recipes-phosphor/interfaces/bmcweb_%.bbappend
+++ b/meta-ibm/recipes-phosphor/interfaces/bmcweb_%.bbappend
@@ -3,6 +3,7 @@
-Dibm-management-console=enabled \
-Dredfish-new-powersubsystem-thermalsubsystem=enabled \
-Dredfish-dump-log=enabled \
+ -Dredfish-oem-manager-fan-data=disabled \
"
EXTRA_OEMESON:append:p10bmc += " \