Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About the error respond "not match object IDs of resource chain" #531

Closed
FelixD999 opened this issue Feb 7, 2023 · 2 comments · Fixed by #536
Closed

About the error respond "not match object IDs of resource chain" #531

FelixD999 opened this issue Feb 7, 2023 · 2 comments · Fixed by #536
Assignees

Comments

@FelixD999
Copy link

Hi,

Some errors indicate "URI {} does not match object IDs of resource chain".
As far as I know, the value of the property "ID" must be the same as the word after the last slash in the link of "@odata.id", what other specifications must be met to avoid such errors from happening?
Take a screenshot as an example:
1
2

In the URI of the upper layer, the "Members" also lists the correct link.
3

Thanks,
Felix

@tomasg2012
Copy link
Contributor

tomasg2012 commented Feb 7, 2023

The Ids are only checked in the Resource itself, so the bottom screenshot will pass.

However, not sure about the top image. It checks every resource Id in the path. Does your /redfish/v1/Systems/Self pass as well?

After looking into the Schema for USBController, the issue seems to be how the tool interprets the Schema. The schema is written with {ControllerId} instead of {USBControllerId}, and the tool uses this to determine type accuracy (Controller is not a valid type).

This is a tool issue, so your implementation should already be correct.

@mraineri
Copy link
Contributor

mraineri commented Feb 7, 2023

@tomasg2012 let's check two things with this:

  1. Ensure there's no dependency with parent resources; so, even if "/redfish/v1/Systems/Self" is not correct, that should not impact child resources like with this USB controller resource.
  2. Don't rely on the names of the tokens inside of the curly braces or perform matching with the resource name since the token names aren't required to match the resource name; simply the presence of the curly braces is sufficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants