DMTF / Redfish-Service-Validator

The Redfish Service Validator is a Python3 tool for checking conformance of any "device" with a Redfish service interface against Redfish CSDL schema
Other
40 stars 34 forks source link

Default Oem Property Response Not Shown in Redfish-Service-Validator #558

Closed Saravanans2001 closed 4 months ago

Saravanans2001 commented 1 year ago

Hi, I am using Redfish-Service-Validator tool (https://github.com/DMTF/Redfish-Service-Validator/issues/new) for checking the Schema compilance,

Screenshot from 2023-07-14 18-08-07 For managers/Bmc URI , I could see the above response as ,which "/redfish/v1/Managers/bmc/Truststore/Certificates" can navigate to the Tructstore/Certificate Screenshot from 2023-07-14 18-09-42 1.But I can't navigate to the "/redfish/v1/Managers/bmc#/Oem/OpenBmc", Screenshot from 2023-07-14 18-50-20 2.I coud'nt get response for Certificate like the above image "/redfish/v1/Managers/bmc/Truststore/Certificates"

  1. redfish/v1/Oem/openBmc/Certificate is a default property,But it is not displayed like the above image in the Redfish-Service-Validator
  2. It is under the Oem property whether it will show the response like the above image or not ?
mraineri commented 1 year ago

Can you please try again with --debugging and provide the txt log file?

Saravanans2001 commented 1 year ago

Hi @mraineri

Here is my txt log file

ConformanceLog_07_17_2023_124655.txt

I have added one property under Oem.OpenBmc.ButtonPress Screenshot from 2023-07-17 14-23-30 Screenshot from 2023-07-17 15-23-27

Wheather Oem.OpenBmc.Buttonpress will show the above response like redfish/v1/cable or not ?

mraineri commented 1 year ago

The txt file doesn't contain all of the debugging traces. The file shows debugging: False. Can you please try again and add --debugging to the CLI when running the tool?

Looking at your earlier questions... I think there's some confusion for what dictates a resource... The URI /redfish/v1/Managers/bmc#/Oem/OpenBmc contains a #, which gives a browser a reference into a resource. For JSON payloads, this follows the RFC6901 syntax, so when you use a URI like "/redfish/v1/Managers/bmc#/Oem/OpenBmc", this equates to "the OpenBmc property inside the Oem object inside the /redfish/v1/Managers/bmc resource". So, this will appear as an object in the test report inside the /redfish/v1/Managers/bmc section. From your most recent screenshot, I do see this in the output.

mraineri commented 4 months ago

Closing; debug files shown so far indicate the tool is behaving properly. OEM definitions in this case require refinement in the implementation.