Inventory dbus to redfish mapping and debug

[i.kononenko]

Patrick, 

I have same problem with the Processor redfish node. In our system we using entity-manager and dbus-sensors as mainline of managing physical system components.
At research  I was found some problem of business-logic in dbus-sensors and bmcweb:

* Bmcweb:redfish:cpudimm.hpp[1] - retrieving CPU info from dbus depend of CPU-core object which was not been created anyone service. 
  This is originate the premise to adjust "TotalCoresEnable" to zero and Status->State to "absent"
* The main problem which raising the exception is lack of "present" and "functional" DBus-properties [2].

But, I was noticed, that at last revision of bmcweb this was be fixed. If problems is remained let me known -
I have number of patches which fixed this another context for our system implementation and I'm ready suggest it at gerrit changes.
Thanks.


[1] https://github.com/openbmc/bmcweb/blob/50626f4f1aaa02daae058617ce0c603874277322/redfish-core/lib/cpudimm.hpp#L197
[2] https://github.com/openbmc/bmcweb/blob/80789c8e769b7439d72787bd620f28ebd5b14235/redfish-core/lib/cpudimm.hpp#L169 

On 26.09.2020 02:42, Patrick Voelker wrote:
> I'm trying to view my processor information that originates from SMBIOS.  I can see readable info on the dbus with this command:
> busctl introspect xyz.openbmc_project.Smbios.MDR_V1 /xyz/openbmc_project/inventory/system/chassis/motherboard/cpu0
> 
> But if I ask redfish, I get an error (below.)  Can someone give me a pointer on how to debug this?  I'm having trouble finding what maps the redfish query to the dbus and what log file I can check to see more information about the error.
> 
> https://<host>/redfish/v1/Systems/system/Processors/cpu0
> 
> {
>     "@odata.id": "/redfish/v1/Systems/system/Processors/cpu0",
>     "@odata.type": "#Processor.v1_7_0.Processor",
>     "error": {
>         "@Message.ExtendedInfo": [
>             {
>                 "@odata.type": "#Message.v1_0_0.Message",
>                 "Message": "The request failed due to an internal service error.  The service is still operational.",
>                 "MessageArgs": [],
>                 "MessageId": "Base.1.4.0.InternalError",
>                 "Resolution": "Resubmit the request.  If the problem persists, consider resetting the service.",
>                 "Severity": "Critical"
>             }
>         ],
>         "code": "Base.1.4.0.InternalError",
>         "message": "The request failed due to an internal service error.  The service is still operational."
>     }
> }
> 

-- 
Best regards,

Igor Kononenko