Don't block boot on debug or info level event logs
Event logs with a severity of Debug or Informational do not need to
block boots, when that functionality is enabled, even if they contain a
callout. If a boot block was desired, the creating application can just
make the error a different severity.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I79f052a8159342ed6d9ccd11e057482bd2272114
diff --git a/README.md b/README.md
index 1a393db..f55412b 100644
--- a/README.md
+++ b/README.md
@@ -573,7 +573,8 @@
phosphor-logging supports a setting, which when set, will result in the
software looking at new phosphor-logging entries being created, and if a
CALLOUT* is found within the entry, ensuring the system will not power
-on.
+on. Entries with severities of Informational or Debug will not block boots,
+even if they have callouts.
The full design for this can be found
[here](https://github.com/openbmc/docs/blob/master/designs/fail-boot-on-hw-error.md)
diff --git a/log_manager.cpp b/log_manager.cpp
index d12630a..c2a9b86 100644
--- a/log_manager.cpp
+++ b/log_manager.cpp
@@ -242,7 +242,8 @@
serialize(*e);
- if (isQuiesceOnErrorEnabled() && isCalloutPresent(*e))
+ if (isQuiesceOnErrorEnabled() && (errLvl < Entry::sevLowerLimit) &&
+ isCalloutPresent(*e))
{
quiesceOnError(entryId);
}