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

Remove errorlog association on PEL deletion #119

Open
wants to merge 1 commit into
base: 1050
Choose a base branch
from

Conversation

deepakala-k
Copy link
Contributor

If a system guard's associated PEL is removed, the guard was skipped to be displayed in the GUI as the association is lost. The following error was displayed.

Skipping to restore a given isolated hardware [23 01 00 02 00 03 00 ] : Due to failure to get BMC error log path by isolated hardware EID (aka PEL ID) [1342178283]

As the guard still exists, it is better to display the guard without the errorlog association. The gui could show a system guard (predictive/ fatal) without the errorlog.

Currently the PEL associated with the guard cannot be removed. This is an extra check on top of it.

@deepakala-k deepakala-k force-pushed the 1050_PEL_deleted branch 2 times, most recently from 67285d5 to 15207be Compare January 24, 2025 06:45
If a system guard's associated PEL is removed, the guard was skipped to
be displayed in the GUI as the association is lost. The following error
was displayed.

```Skipping to restore a given isolated hardware [23 01 00 02 00 03 00 ] :
Due to failure to get BMC error log path by isolated hardware EID (aka
PEL ID) [1342178283]```

As the guard still exists, it is better to display the guard without the
errorlog association. The gui could show a system guard (predictive/
fatal) without the errorlog.

Cherry picked the change from 1110.

Tested and found it working as expected

Signed-off-by: deepakalak <[email protected]>
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.

1 participant