Skip to content

Conversation

Alpana07
Copy link
Contributor

This commit is to move yaml/com/ibm/VPD.errors.yaml into yaml/com/ibm/VPD directory

Test:
Tested the patch on Rainier system.
Reached successfully standby - runtime - standby

Change-Id: I4e04a865164f7e1a4548ffd7a80b4f035a31573d

@jenkins-openbmc-ibm
Copy link

Can one of the admins verify this patch?

errors:
- xyz.openbmc_project.Common.Error.InvalidArgument

- name: deleteFRUVPD
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why were these removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay , will check, how this happened.

- xyz.openbmc_project.Common.Error.InvalidArgument
- com.ibm.VPD.Error.LocationNotFound
- com.ibm.VPD.Error.NodeNotFound
- com.ibm.VPD.VPD.Error.LocationNotFound
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets see if we can rename the file from VPD.errors.yaml.
These repeated VPD.VPD is not looking good and create confusions later on.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something like Parser.errors.yaml

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, yeah.
but then it will be different from current upstream commit.

This commit is to move yaml/com/ibm/VPD.errors.yaml into
yaml/com/ibm/VPD directory

Test:
Tested the patch on Rainier system.
Reached successfully standby - runtime - standby

Change-Id: I4e04a865164f7e1a4548ffd7a80b4f035a31573d
Signed-off-by: Alpana Kumari <[email protected]>
Copy link
Contributor

@SunnySrivastava1984 SunnySrivastava1984 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is not so straight forward.
This will have impact on message registry and the way we create PELs from parser code.
Will need to discuss this in detail.

@Alpana07
Copy link
Contributor Author

Alpana07 commented Dec 4, 2023

As we discussed, I am closing this PR, as this change is causing lots of other files/components change. We can come back later on it.

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 this pull request may close these issues.

3 participants