boot-block: don't power on if blocking err present
If the user has enabled the setting to block the boot if an error with a
CALLOUT is logged and such an error is logged, ensure the chassis-poweron
target does not complete.
See the following design for more details:
https://github.com/openbmc/docs/blob/master/designs/fail-boot-on-hw-error.md
Tested:
With the following series of commits:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-logging/+/32155/
- Verified that obmc-chassis-poweron@0.target did not complete when an
unresolved error was present.
- Verified that target did complete once the log was resolved
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If07993eeaf0d468d12f7872c2ef469f08c90ff70
diff --git a/target_files/obmc-chassis-poweron@.target b/target_files/obmc-chassis-poweron@.target
index e1aa7cf..2fae676 100644
--- a/target_files/obmc-chassis-poweron@.target
+++ b/target_files/obmc-chassis-poweron@.target
@@ -5,6 +5,8 @@
After=mapper-wait@-xyz-openbmc_project-state-chassis%i.service
Wants=mapper-subtree-remove@-xyz-openbmc\x5fproject-software\x3Axyz.openbmc_project.Software.ActivationBlocksTransition.service
After=mapper-subtree-remove@-xyz-openbmc\x5fproject-software\x3Axyz.openbmc_project.Software.ActivationBlocksTransition.service
+Wants=mapper-subtree-remove@-xyz-openbmc\x5fproject-logging\x3Axyz.openbmc_project.Logging.ErrorBlocksTransition.service
+After=mapper-subtree-remove@-xyz-openbmc\x5fproject-logging\x3Axyz.openbmc_project.Logging.ErrorBlocksTransition.service
Conflicts=obmc-chassis-poweroff@%i.target
RefuseManualStop=yes
OnFailure=obmc-chassis-poweroff@%i.target