PEL: Skip purging PEL if it has associated hw isolation entry
When PELs reaches to certain limits, either in total size or
total number of them, the code starts removing older pels
based on certain criteria. During this process make sure
no pel is removed that has an associated hardware isolation
entry record or error_log event record.
Signed-off-by: Sumit Kumar <sumit_kumar@in.ibm.com>
Change-Id: Ia7c9af6911bcf2ac8f8ec046d4c7a7a12d9b2bbd
diff --git a/extensions/openpower-pels/manager.cpp b/extensions/openpower-pels/manager.cpp
index 6bbdf11..419d087 100644
--- a/extensions/openpower-pels/manager.cpp
+++ b/extensions/openpower-pels/manager.cpp
@@ -526,7 +526,9 @@
void Manager::pruneRepo(sdeventplus::source::EventBase& /*source*/)
{
- auto idsToDelete = _repo.prune();
+ auto idsWithHwIsoEntry = _dataIface->getLogIDWithHwIsolation();
+
+ auto idsToDelete = _repo.prune(idsWithHwIsoEntry);
// Remove the OpenBMC event logs for the PELs that were just removed.
std::for_each(idsToDelete.begin(), idsToDelete.end(),