Redfish Service Validator

[justin0309]

Currently I am testing with v3.0-stable version. I tested it in docker.

I know that the problem regarding branch_name in the dmtf test item has been corrected in the master version. For the following two test items, I can't find any relevant information for my reference. 1.The first test (Test BMC Redfish Using Redfish Service Validator) fails. I don't know which direction to pursue. How should the member ID match to pass? Is it odata.id": "/redfish/v1/Chassis/chassis/Power#/Voltages/0 and "MemberId": "ADC_12" The number at the end must match? 2.The second test (Run Redfish Service Validator With Additional Roles) seems to be that it cannot be created once Get User Role is started.

I tried setting device_name to 0 and this one is pass.

So if the path is /xyz/openbmc_project/sensors/temperature/Sensor_Temp_2, the following Sensor_Temp_2 must be named according to 0, 1, 2, 3, 4 and so on. Is there any relevant information that I can refer to?

[justin0309]

@gkeishin can anyone assist me?

[justin0309]

err.OemSession.v1_0_0.Session This error cannot tell where the actual error is.

[mdmillerii]

The validator is complaining about the third session. It appears two were formatted to json and the third likely is trying to generate an error response that (1) didn't create an error response and (2) didn't offer the client any details why.

[gkeishin]

1.The first test (Test BMC Redfish Using Redfish Service Validator) fails. I don't know which direction to pursue. How should the member ID match to pass? Is it odata.id": "/redfish/v1/Chassis/chassis/Power#/Voltages/0 and "MemberId": "ADC_12" The number at the end must match?

This is probably a schema vs implementation error which Redfish validator is complaining about.. Reach out to the OpenBMC community on discord https://discord.gg/GYqshvV8

2.The second test (Run Redfish Service Validator With Additional Roles) seems to be that it cannot be created once Get User Role is started.

This one, I can check on it..

[gkeishin]

@justin0309 it looks like with 0penBmc default password it doesn't seem to work for the additional roles while creating.. So probably I can update the test case like this to make it default for Operator and Read-only users

    #username      password             role        enabled
    operator_user  0penBmc123           Operator    ${True}
    readonly_user  0penBmc123           ReadOnly    ${True}

can you try with this changes if it works clean in your setup.. if all works I ll push up the changes..

[gkeishin]

Never mind. I have pushed up the patch fix for the additional role to work https://gerrit.openbmc.org/c/openbmc/openbmc-test-automation/+/67609 @justin0309